[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mingw compiler on cygwin, and path issues
From: |
Jan Engelhardt |
Subject: |
Re: mingw compiler on cygwin, and path issues |
Date: |
Fri, 10 Apr 2009 22:23:53 +0200 (CEST) |
User-agent: |
Alpine 2.00 (LSU 1167 2008-08-23) |
On Friday 2009-04-10 22:19, Jan Engelhardt wrote:
>
>AM_CFLAGS = -I${abs_top_builddir}/subproject
>AM_LDFLAGS = -L${abs_top_builddir}/subproject
>
>This gets expanded into -I/home/User/project/subproject, but the mingw
>compiler of course tries to search in C:\home\user\project\subproject
>instead of c:\cygwin\home\user\project. [...]
Secondly, the use of libtool suffocates the potential success of cygpath
-m.
Given:
AM_LDFLAGS = -L../subproject
foo_LDADD = -lsub
automake will call libtool as usual, and libtool will expand it to
a cygwin path only:
/bin/sh ../libtool --tag=CC --mode=link gcc -I../subproject -O2 -g
-L../subproject -o foo.exe foo.o -lsub libtool: link: gcc
-I../subproject -O2 -g -o .libs/foo.exe foo.o -L../subproject
/home/User/project/subproject/.libs/libsub.a
gcc.exe: [longpath]/libsub.a: No such file or directory
How would one go about addressing this?