Re: [Fontforge-devel] fontforge and cygwin

[Heiko J. <hei...@gm...>]

Am 16.02.2014 21:02, schrieb Jose Da Silva:
> I'm not running cygwin, but you are in an interesting position to see if
> this resolves it. Would you mind seeing if this works? It is "before"
> bootstrap and still uses autogen.sh
>
> https://github.com/fontforge/fontforge/releases  (use ver 20140101).
> This version still uses:
> sh autogen.sh
> ./configure
> make
> sudo make install

Result:

Also not finding libspiro etc. because also only searching
at /lib and /usr/lib ...

libiconv:  a lot of compiling warnings, but linking seems to work
with warning?:
   CCLD     libgunicode.la
libtool: link: warning: undefined symbols not allowed in
                         x86_64-unknown-cygwin shared libraries

fontforgeexe:
   CCLD     libfontforgeexe.la
now "working" with warnings like this:
*** Warning: This system can not link to static lib archive ../Unicode/libgunicode.la.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.

but two steps further:
   CC       fontforge-main.o
   CCLD     fontforge.exe
./.libs/libfontforgeexe.a(libfontforgeexe_la-prefs.o): In function `encmatch':
/home/Jacobs/fontforge-2.0.20140101/fontforgeexe/prefs.c:966: undefined reference to `libiconv_open'
/home/Jacobs/fontforge-2.0.20140101/fontforgeexe/prefs.c:966:(.text+0x13cc): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `libiconv_open'
/home/Jacobs/fontforge-2.0.20140101/fontforgeexe/prefs.c:980: undefined reference to `libiconv_close'
/home/Jacobs/fontforge-2.0.20140101/fontforgeexe/prefs.c:980:(.text+0x143c): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `libiconv_close'
... and so on ... long list again ...

>> There make produces a loooooong list of errors. It seems that make
>> found NOTHING of things compiled before ...
>
> apt-get automake and also dev-libtools (I think).
> ...as it currently stands at this time, the make system still doesn't check
> for libtools (I think).

cygwin seems not to use apt ... not found ...
but automake and libtools are installed. That they were missing I saw
at the early steps of trying to compile fontforge ;)