After contacting the owner of the freetype2-iphone git project, it seems that he has the same problems building the library with Xcode. I have decided to put that approach to one side for now, and to follow the procedures detailed in INSTALL.UNIX and INSTALL.CROSS.
My execution of the `configure` script is currently not working with the parameterisation suggested on StackOverflow, resulting in errors to do with the `limits.h` and `assert.h` header files. However, this is specific to my build environment, and not a general freetype2 question. I have addressed the StackOverflow community to try to resolve this: https://stackoverflow.com/questions/23683331/error-compiling-freetype2-library-for-arm7-with-osx-gcc-limits-h-no-such-file Cheers, Jeff. On 14 May 2014 23:58, Jeffrey Sheen <[email protected]> wrote: > Many thanks for your quick response Werner. > > This being my first foray with freetype2, I had indeed overlooked the > customisation of `ftmodule.h`. > > After commenting out the modules corresponding to those `.c` files that I > had omitted from the compilation step, I rebuilt the product. I ended up > with a library of 3.2MB, as opposed to the previous build of 2.6Mb. I then > re-added it to my other, dependent Xcode project. > > The first clean and build cycle of the dependent Xcode project yielded the > same linker errors, so there is still something awry. I will give it > another go in the morning. > > Perhaps I will jettison my plan to build the freetype2 library with Xcode > altogether. There are some suggestions for a command line process that I > can attempt instead. > > > On 14 May 2014 19:38, Werner LEMBERG <[email protected]> wrote: > >> > However, when trying to build the dependent Xcode project, I get the >> > following linker errors: >> > >> > "_bdf_driver_class", referenced from: >> > [...] >> > >> > I notice that these errors contain the names of modules that I have >> > disabled, by removing their respective ".c" files from compilation >> > in the original "freetype2-ios" Xcode project. >> > >> > Was there some other configuration required in that Xcode project, >> > in order to remove references to these disabled modules? >> >> I guess that you've missed to update `ftmodule.h' to hold only the >> modules you are going to use. Cf. `docs/CUSTOMIZE'. >> >> >> Werner >> > >
_______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
