I'm required to use the compiler from visualstudio and I use cygwin for
launching ant only. I have modified build.xml to call cl.exe to build
and link. What I can't figure out is how to modify build.xml so that I
can control what gets passed to the compiler and to see the ouput from
the compiler when I give it the wrong thing; you know a log file.
I hope that is more clear.
thanks for the response.
john
Curt Arnold wrote:
On May 12, 2006, at 5:18 PM, john ware wrote:
Hi,
I got sources using:
svn co http://svn.apache.org/repos/asf/logging/log4cxx/trunk
logging-log4cxx
I'm using cygwin bash on a windoz server 2003,sp1. I call ant in
logging-log4cxx and I get the errors below. It can't find the
standard ms compiler
headers.
Two questions: does the cc task generate an output file of the
compilation process and how does one pass an include flag to the c+ +
compiler.
thanks,
john ware
Running under the cygwin shell doesn't really affect the build
process other than putting the Cygwin gcc on the path. As it stands,
the build process assumes that you want to build a Win32 DLL using a
MinGW gcc (which would have a windows.h in its default include
directory). If you want to build a more Unixy log4cxx running under
a Cygwin compatibility layer, you have to override the assumed Win32
target platform, by specifying:
ant -Dos.family=cygwin
However, I haven't tested the cygwin or MinGW builds for a long time
and can't say that will get you much further. The autoconf style
builds might be a more natural way to create a Cygwin log4cxx, since
they always assume that you are targeting a Unix-like platform.
