Hi,
The project configuration is different between debug and release. In debug
you certainly added log4cxx.lib in the field "Linker/Input/Additional
dependencies" but you have a drop-down which select the configuration, if
you switch to release, I think you don't have log4cxx.lib in "Additional
de
Thanks for answering. I wish the solution was that simple. I apologize for not
explicitly mentioning it, but my project is - I think - set up correctly.
That is:
- both the Debug and Release configurations mention log4cxx.lib in its
Linker>Input>Additional Dependencies
- both the Debug and Rele
Mh, maybe those symbols are in the DLL but not in the lib. To be in the lib,
it must have __declspec(dllexport) when compiling.
log4cxx use this define to do this:
#if defined(LOG4CXX_STATIC)
#define LOG4CXX_EXPORT
// definitions used when building DLL
#elif defined(LOG4CXX)
#define LOG4CXX_EXPOR
When setting the linker verbose, it indeed reports that it is searching
log4cxx.lib.
When setting fully verbose, it even reports *finding* symbols in log4cxx.lib
with the file that references them.
So indeed, the linker finds log4cxx.lib AND manages to find some of the symbols
I use.
Also, it se
Why my boss don't want I develop for MacOS X ? :-)
The class déclaration must be __declspec(export) when you compile the dll
and must be __declspec(import) when you include .h from this dll. So it's
correct in your error message.
It's possible that the missing symbols declarations didn't have
__
I downloaded the source code from the links at
http://logging.apache.org/log4cxx/download.html
I simply compiled it following the instructions at
http://logging.apache.org/log4cxx/building/vstudio.html
I had no error doing so.
I tried to track down one of those missing symbols, namely "getLogge
Have you tried to recompile all from clean?
Maybe the release lib is corrupted...
On Fri, May 7, 2010 at 15:47, Jean-Denis Muys wrote:
> I downloaded the source code from the links at
> http://logging.apache.org/log4cxx/download.html
> I simply compiled it following the instructions at
> http:/
yep. no change.
On May 7, 2010, at 15:57 , Fabian Jacquet wrote:
> Have you tried to recompile all from clean?
> Maybe the release lib is corrupted...
>
>
> On Fri, May 7, 2010 at 15:47, Jean-Denis Muys wrote:
> I downloaded the source code from the links at
> http://logging.apache.org/log4cx
I use the ant build system from the VS shell.
In the source directory run ant for a release build or ant -Ddebug=true for a
debug build
From: Jean-Denis Muys [mailto:jdm...@mac.com]
Sent: 07 May 2010 16:11
To: Log4CXX User
Subject: Re: link error in release mode
John,
Thanks for chiming in.
Unfortunately, I think I don't understand your suggestion.
Are you suggesting that I build log4cxx [Debug|Release] using ant?
Or are you suggesting that I build my client program with ant?
Or both?
In either case, why do you think ant could help with the issue I hav
I suggest building the log4cxx.dll via ant as you only have do it once ( twice
if you want a release and debug version ) and you can set the correct paths to
the dll and header files in the VS project setting for your client project
build configuration. Personally I very rarely use application V
That should be a static lib only results in a lib, duh!
From: Reynolds, John [mailto:john.reyno...@flightman.com]
Sent: 07 May 2010 17:16
To: Log4CXX User
Subject: RE: link error in release mode with Visual Studio 2008
I suggest building the log4cxx.dll via ant a
I suspect something about the VC release mode linker settings in the client
project.
But for the library build, make sure the LOG4CXX_EXPORT stuff (preprocessor
symbol) is setup the same in debug and release mode.
I agree I don't see how ant would be relevant.
When you figure it out,
13 matches
Mail list logo
