On Nov 28, 2007, at 8:03 PM, Vic Simkus wrote:
Hello
Thanks for the help. It sort of works... it logs to the "Application
Log" if I use a pre-existing source (? not sure of the win32
terminology. It's all ass-backwards in my mind). It logs to a custom
source to a custom log. But it refus
Hello
Thanks for the help. It sort of works... it logs to the "Application
Log" if I use a pre-existing source (? not sure of the win32
terminology. It's all ass-backwards in my mind). It logs to a custom
source to a custom log. But it refuses to log to a custom source in
an existing log.
E
On Nov 28, 2007, at 8:37 AM, Eborn, Eric D wrote:
I had figured as much, that I wouldn’t need to use that directive if
using shared libs, but it cleaned up a few errors of the following
form:
class 'std::vector<_Ty>' needs to have dll-interface to be used by
clients of class
However, t
On Nov 28, 2007, at 2:07 PM, Unnikrishnan Udinoor wrote:
Hi,
I am using log4cxx 0.9.7 version. On dynamically linking to the
log4cxx library my C++ application works fine with the logging.
On changing the linking to static log4cxx , I get errors stating
that unable to instantiate the cla
Hi,
I am using log4cxx 0.9.7 version. On dynamically linking to the log4cxx
library my C++ application works fine with the logging.
On changing the linking to static log4cxx , I get errors stating that
unable to instantiate the class.
Can someone help me to fix this issue ? Thanks a lot in Advanc
One thing I noticed also is that each of the errors (with static libs) is
associated with the following lines of code within my code:
LoggerPtr logger(Logger::getLogger("MyApp"));
LOG4CXX_INFO(logger, "Entering application.");
These lines were pulled out directly from the working app however, I
I had figured as much, that I wouldn’t need to use that directive if using
shared libs, but it cleaned up a few errors of the following form:
class 'std::vector<_Ty>' needs to have dll-interface to be used by clients of
class
However, the 3 remaining errors remain the same without that preproce
