Re: [ft] Question: linker errors when building freetype for iOS in Xcode

[Wojciech Mamrak]

Have you excluded ftgzip from the build?

2014-06-13 11:42 GMT+02:00 Jeffrey Sheen <address@hidden>:
> Hi all,
>
> I have successfully built a full version of freetype2, using the
> freetype-ios project's Xcode project file. However, I am still unable to
> build a minimal version of freetype2 using the 'configure' command line
> method. Ideally, I would like to just build support for TrueType and
> OpenType font formats.
>
> Please find attached my 'ftoption.h' and 'modules.cfg' files, and the batch
> script used to cross compile for iOS architectures (including the i386
> simulator).
>
> I get linker errors when trying to use the static library built with this
> configuration. Specifically:
>
>> Undefined symbols for architecture i386:
>>   "_FT_Gzip_Uncompress", referenced from:
>>       _sfnt_init_face in libfreetype-ios+simulator.a(sfnt.o)
>>
>> ld: symbol(s) not found for architecture i386
>
>
> I can see that 'sfnt_init_face' calls 'FT_Gzip_Uncompress' in the source
> code.
>
> Although there is no dependency mentioned in the documentation, is it the
> case that the TrueType or OpenType modules require Gzip support to be
> enabled? I have disabled it in my build options, as I interpreted it as
> being optional.
>
> Any help is much appreciated.
>
> Cheers,
>
> Jeff.
>
>
> On 23 May 2014 12:03, Jeffrey Sheen <address@hidden> wrote:
>>
>> Dear Werner and the wider freetype mailing list,
>>
>> I just wanted to say that I fixed my OSX build environment by reinstalling
>> the latest distribution of the Xcode command line tools.
>>
>> I have updated my StackOverflow question with this solution, so that
>> others with the same issue can resolve it without resorting to the mailing
>> list.
>>
>> Thank you for your patience,
>>
>> Jeff.
>>
>>
>> On 15 May 2014 17:09, Jeffrey Sheen <address@hidden> wrote:
>>>
>>> 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 <address@hidden> 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 <address@hidden> 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
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/freetype
>