Re: [gimpwin-users] libtool crach in gimp compiling

Cyrille Grange <[email protected]>
Newsgroups gmane.comp.video.gimp.windows.devel
Message-ID <[email protected]>

Tor Lillqvist wrote:
> (This really is more suited for gimpwin-dev, Cc:ing there.)
> 
> Cyrille Grange writes:
>  >        .libs/impgen ../../libgimp/.libs/libgimpui-1-2-0.dll > 
>  > .libs/libgimpui-1-2-0.dll-def
>  > generating import library for `libgimpui-1-2-0.dll'
> 
> works, while:
> 
>  >        .libs/impgen 
>  > /usr/local/src/gimp-1.2.3/libgimp/.libs/libgimp-1-2-0.dll > 
>  > .libs/libgimp-1-2-0.dll-def
>  > make[1]: *** [script-fu.exe] Error 1
> 
> fails.
> 
>  > What i don't anderstand, is that everything goes well with 
>  > libgimpui-1-2-0.dll but impgen seems to fail on libgimp-1-2-0.dll
> 
> One possible explanation is that the first time impgen gets run, the
> argument is a relative path to ../../libgimp/....  This relative path
> means the same both in Cygwin and Windows.
> 
> However, the second impgen (for some reason I don't understand right
> now) is invoked on /usr/local/src/... This is a absolute Cygwin
> path. Presumably it is not a valid Windows path, i.e. /usr/local/src
> in Cygwin is not current_drive:\usr\local\src in Windows? The
> impgen.exe that libtool produces presumably is a non-Cygwin program
> (if you have the mingw gcc first in your PATH, as you should), and
> doesn't understand Cygwin paths.
> 
> Because of problems like this, I always make sure that the same paths
> to source files are valid both in Cygwin and pure Windows when working
> with auto* and libtool. I have GLib, GTK+, GIMP etc sources in I:\src,
> which is mounted in Cygwin as /src. Thus, if my current directory is
> for instance I:\src\gimp\plug-ins\common, the path /src/gimp/libgimp
> is valid both in Cygwin and Windows, and refers to the same location.
> 
> Ditto for the installation target (prefix), it's also best if that is
> the same both from Cygwin's and Windows' point of view.
> 
> --tml

Thank's a lot Tor, it really help in plug-ins compilations. A lot of 
errors came from that.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.