Re: Problems building log4cxx 0.9.7 on Windows/CYGWIN

Thanks very MUCH for your reply Jwahar !

Your tip seems pretty helpful, but the fact is that I don't get to build the 
libraries under CYGWIN, so I can't aplly what you suggest :-(

I keep having problems with tchar.h (the compiler doesn't know the "int64_t" 
type). It happens when I compile with MinGW (under CYGWIN), and with Borland, so I'm googling around to see if I learn something new about this type, it's header, and it's headaches ;-).

The fact is that my project can´t wait any more to have this log library 
running, so in the meantime it would be great if you could zip and email me just the 
binaries... I mean:

the dynamic library:      log4cxx.dll
& it's "import library":  liblog4cxx.a

I think if you built these two binaries on any Windows/x86 platform, with MinGW 
or CYGWIN GCC, then I could successfully link them to my project with MinGW. 
I'll let the resolution of Borland compilation to the future, cause Curt Arnold 
told me there would be an ant script for Borland in future releases.

Thanks in advance for your kind help.
My email is: dsusa@xxxxxxxxx

Receive best regards,
Diego

Jwahar Bammi wrote:

> Diego,
> I have been building log4cxx on CYGWIN for a while now. I have a pretty much
> a stock full install of cygwin, also doxygen. I guess the best way to
> describe my environment is to include my file "config.log", it will give you
> all the details.
>
> As I have described here before, after building the libraries and doing a
> make install, I build dynamic libraries using the following procedure
> (hack): -- see attached "doit" file, I am sure email will mangle the long
> line that follows:
>
> g++ -shared -o log4cxx.dll -Wl,--out-implib=liblog4cxx.dll.a
> -Wl,--export-all-symbols -Wl,--enable-auto-import -Wl,--whole-archive
> liblog4cxx.a -Wl,--o-whole-archive '-L/usr/lib -lxml2 -lz -lpthread -liconv
> -lm' -lxml2 -lz -pthread -liconv -lm
>
> Not sure how I can help: if you like I can zip up my whole directory and
> send it to you (or anyone else).
>
> Jwahar Bammi
> Memento, Inc.
> bammi@xxxxxxxxxxxxxxx