[prev in list] [next in list] [prev in thread] [next in thread]
List: freetype
Subject: Re: [ft] Question: linker errors when building freetype for iOS in Xcode
From: Jeffrey Sheen <jeff () stargazystudios ! com>
Date: 2014-05-23 11:03:43
Message-ID: CAPYQ83no3ig48144=bk8nOn7fhcUmHyE+0j=pEKfPoEebbZOvg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <jeff@stargazystudios.com> 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 <jeff@stargazystudios.com> 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 <wl@gnu.org> 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
> > >
> >
> >
>
[Attachment #5 (text/html)]
<div dir="ltr">Dear Werner and the wider freetype mailing list,<div><br></div><div>I \
just wanted to say that I fixed my OSX build environment by reinstalling the latest \
distribution of the Xcode command line tools.</div><div>
<br></div><div>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.</div><div> <br></div><div>Thank you for your \
patience,</div><div><br></div><div>Jeff.</div></div><div \
class="gmail_extra"><br><br><div class="gmail_quote">On 15 May 2014 17:09, Jeffrey \
Sheen <span dir="ltr"><<a href="mailto:jeff@stargazystudios.com" \
target="_blank">jeff@stargazystudios.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">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.<div>
<br></div><div>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.</div>
<div><br></div><div>I have addressed the StackOverflow community to try to resolve \
this:</div><div><br></div><div><a \
href="https://stackoverflow.com/questions/23683331/error-compiling-freetype2-library-for-arm7-with-osx-gcc-limits-h-no-such-file" \
target="_blank">https://stackoverflow.com/questions/23683331/error-compiling-freetype2-library-for-arm7-with-osx-gcc-limits-h-no-such-file</a></div>
<div><br></div><div>Cheers,</div><div><br></div><div>Jeff.<div><div \
class="h5"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 May \
2014 23:58, Jeffrey Sheen <span dir="ltr"><<a \
href="mailto:jeff@stargazystudios.com" \
target="_blank">jeff@stargazystudios.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr">Many thanks for your quick response Werner.<div>
<br></div><div>This being my first foray with freetype2, I had indeed overlooked the \
customisation of `ftmodule.h`.<div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>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.</div>
</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 \
May 2014 19:38, Werner LEMBERG <span dir="ltr"><<a href="mailto:wl@gnu.org" \
target="_blank">wl@gnu.org</a>></span> wrote:<br> <blockquote class="gmail_quote" \
style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>> However, when trying to build the dependent Xcode project, I get the<br>
> following linker errors:<br>
><br>
</div>> "_bdf_driver_class", referenced from:<br>
> [...]<br>
<div>><br>
> I notice that these errors contain the names of modules that I have<br>
> disabled, by removing their respective ".c" files from compilation<br>
> in the original "freetype2-ios" Xcode project.<br>
><br>
> Was there some other configuration required in that Xcode project,<br>
> in order to remove references to these disabled modules?<br>
<br>
</div>I guess that you've missed to update `ftmodule.h' to hold only the<br>
modules you are going to use. Cf. `docs/CUSTOMIZE'.<br>
<span><font color="#888888"><br>
<br>
Werner<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div>
_______________________________________________
Freetype mailing list
Freetype@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic