Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

Hi Behdad, I wrote this hb.cc file. Drop it in the root of harfbuzz source tree to try it out. You will need to add both Freetype and 'hb-ucdn' to the include path though. It will *not* compile; there are a bunch of symbol redefinition problems and other seemingly (?) trivial things to fix (82

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

Thanks Daniel. I'm not opposed to the idea if it doesn't introduce too many hacks. Might take a look at it myself even. On 15-12-28 11:00 PM, Daniel Ribeiro Maciel wrote: > I can write a '.cc' file which includes all other '.cc' files and defines a > bunch of stuff if you guys are willing to

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

I can write a '.cc' file which includes all other '.cc' files and defines a bunch of stuff if you guys are willing to add such file to your source tree. On Tue, Dec 15, 2015 at 11:14 AM, Jonathan Blow wrote: > Sure, it would be fine to add this; there is also a for-loop in

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

On 15-12-16 12:06 AM, Jamie Dale wrote: > The way I handled this was to create a define called HAVE_STUB_GETENV (which > is a really weird name in hindsight) in my config.h file. I then just set that > define, along with HAVE_INTEL_ATOMIC_PRIMITIVES, when building for PS4. > > I'm not sure if

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

Is Makefile format really that hard to understand? It took 15 minutes for me to port the build rules fin Makefile to my build tool. That's definitely less than I spent reading this thread, BTW ;) Konstantin 2015-12-15 20:23 GMT+03:00 Jonathan Blow : > A porting guide

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

On 15-12-13 09:33 PM, Jamie Dale wrote: > You'll need a define to stub out getenv for a PS4 build I'll take a patch to hb-private.hh to do that. ___ HarfBuzz mailing list HarfBuzz@lists.freedesktop.org

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

On Tue, Dec 15, 2015 at 9:14 PM, Jonathan Blow wrote: > Sure, it would be fine to add this; there is also a for-loop in one spot > that doesn't compile in Visual Studio because it declares an enum inline, so > one has to move the enum. > > But these things don't matter, they

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

> It seems to me that the best way to do this is just to provide one > .cpp file that just includes everything else. [...] Cf. https://github.com/vinniefalco/FreeTypeAmalgam https://github.com/vinniefalco/Amalgams/ Werner ___ HarfBuzz

[HarfBuzz] A plea to make HarfBuzz easier to build.

Hi, I just got through hooking HarfBuzz into a project that runs on Windows (and Monday we get to make sure it runs on the PS4 as well). Even with the help of Daniel Maciel here, who had done a similar thing already, it still took me a couple of hours all together. The thing is there's no reason

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

Hmm... Good luck with that ;P Konstantin 2015-12-13 10:40 GMT+04:00 Jonathan Blow : > Hi, > > I just got through hooking HarfBuzz into a project that runs on Windows > (and Monday we get to make sure it runs on the PS4 as well). Even with the > help of Daniel Maciel here,