[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mingw compiler on cygwin, and path issues
From: |
Jan Engelhardt |
Subject: |
mingw compiler on cygwin, and path issues |
Date: |
Fri, 10 Apr 2009 22:19:05 +0200 (CEST) |
User-agent: |
Alpine 2.00 (LSU 1167 2008-08-23) |
Hi,
I am currently using automake in a Windows-related project; there is a
(pure) mingw compiler in c:\mingw, and cygwin is installed in c:\cygwin.
Now I noticed that Makefile.in, as generated by automake, has a
CYGPATH_W variable which is `echo` on Unices, and `cygpath -w` on
Cygwin. The problem is with a Makefile.am as simple as:
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. Using -L`${CYGPATH_W}
${abs_top_builddir}` also makes for a whacky command line later on where
it tries to use something like
C:\cygwin\home\user\project/subproject/libfoo.la.
In the end I settled with -L`cygpath -m ${abs_top_builddir}` but that
does not quite thrill me. Is there a better way - from a technical
point? (I could use ${top_builddir} but having to relativize everything.)
- mingw compiler on cygwin, and path issues,
Jan Engelhardt <=