Enrico Forestieri a écrit :
On Fri, Apr 14, 2006 at 05:07:47PM +0200, Abdelrazak Younes wrote:
I am no m4 expert, but could see what I can do. Anyway, this is not
strictly necessary as that define can be set through CPPFLAGS.
I would prefer something that is ready to compile out of the box so
let's try to improve the wannabe windows developer ;-)
I am checking in my change right now and we work from there.
Ok, I'll have a look at it, then.
Great!
[...]
Actually, it is quite simple. You should set CC, CPP, CXX, and CXXPP
when invoking configure, like this:
cd build
../configure CC='gcc -mno-cygwin' CPP='gcc -mno-cygwin -E' \
CXX='g++ -mno-cygwin' CXXCPP='g++ -mno-cygwin -E' ...
Are the CPP and CXXCPP used in the build process? What does the '-E' option?
At autogen.sh time, we have to configure between for two potential
platforms:
- CYGWIN
- MSYS
At configure time, we have four different platforms:
- CYGWIN-cygwin-X11
-> no special flags
- CYGWIN-cygwin-WIN32
-> -DQ_CYGWIN_WIN for compilation
- CYGWIN-mingw
-> -mno-cygwin for compilation (and linking?)
-> maybe -L<mingw directory>/lib for linking?
- MSYS-mingw
-> Nothing that I remember for now.
I am not sure anymore we need cygwin.m4 for what we want to do... But
then I know nothing about autoconf :-(
Abdel.
