Oh, so do you mean that I would need to link the executable with libharfbuzz.a to use libicu-le-hb.a to replace libicule.a?
Or that I need to have HarfBuzz on my system in order to build libicu-le-hb.a, which I can then use as a replacement for libicule.a without having to link the executable with libharfbuzz.a? ________________________________________ From: Behdad Esfahbod <[email protected]> on behalf of Behdad Esfahbod <[email protected]> Sent: Wednesday, July 16, 2014 2:12 PM To: Anita Hui; [email protected] Subject: Re: [HarfBuzz] Cross-compiling HarfBuzz for ios On 14-07-16 02:11 PM, Anita Hui wrote: > Just so I'm sure I understand, does this mean that libicu-le-hb.a is > standalone and can directly replace libicule.a without anything extra? Yes, as long as by "standalone" you mean "only needs harfbuzz". :) > Also thanks for responding so quickly :D > > ________________________________________ > From: Behdad Esfahbod <[email protected]> on behalf of Behdad > Esfahbod <[email protected]> > Sent: Wednesday, July 16, 2014 12:47 PM > To: Anita Hui; [email protected] > Subject: Re: [HarfBuzz] Cross-compiling HarfBuzz for ios > > On 14-07-16 12:42 PM, Anita Hui wrote: >> Hi Behdad, >> >> Thanks for your response! I have a general question about building static >> HarfBuzz libraries for replacing icu-LE. I noticed in the configure process >> when checking for tools, it checks for ICU. Does this mean that I need to >> have ICU in order to build libharfbuzz-icu.a? Please correct me if I'm wrong >> but I'm guessing that I need libharfbuzz-icu.a with libicu-le-hb.a in order >> to replace libicule.a. > > You don't need libharfbuzz-icu to use icu-le-hb. Same way that ICU Layout > doesn't actually depend on the rest of ICU. :) > > behdad > >> Again, thank you for replying! It's much appreciated :) >> >> Anita >> >> ________________________________________ >> From: Behdad Esfahbod <[email protected]> on behalf of Behdad >> Esfahbod <[email protected]> >> Sent: Monday, July 14, 2014 4:46 PM >> To: Anita Hui; [email protected] >> Subject: Re: [HarfBuzz] Cross-compiling HarfBuzz for ios >> >> On 14-07-14 04:27 PM, Anita Hui wrote: >>> Hi! >> >> Hi, >> >> >>> I'm trying to cross compile HarfBuzz for iOS (ARMv7, ARMv7s, i386), and I >>> was >>> wondering if I also needed to compile FreeType, Cairo, and GLib for the >>> iOS architectures as well. I am working on an osx machine, and what led me >>> to >> >> No. >> >> >>> the idea that I may need to cross compile the aforementioned libraries is a >>> warning that I receive when I try to build: >>> >>> >>> ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was >>> built for x86_64 which is not the architecture being linked (armv7): >>> /opt/local/lib/libfreetype.dylib >> >> configure --without-freetype --without-glib --without-cairo >> >> Or better yet, set PKG_CONFIG_LIBDIR correctly. >> >> behdad >> >> >>> This warning was followed by a bunch of errors regarding undefined symbols >>> for >>> the architecture. I get the above warning for libglib.dylib and >>> libintl.dylib >>> as well. >>> >>> >>> Ultimately my goal is to create static libraries for HarfBuzz and icu-le-hb. >>> >>> >>> Thanks! >>> >>> >>> Anita Hui >>> [email protected] >>> >>> >>> _______________________________________________ >>> HarfBuzz mailing list >>> [email protected] >>> http://lists.freedesktop.org/mailman/listinfo/harfbuzz >>> >> >> -- >> behdad >> http://behdad.org/ >> > > -- > behdad > http://behdad.org/ > -- behdad http://behdad.org/ _______________________________________________ HarfBuzz mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/harfbuzz
