logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen Corpening" <ocorpen...@acornsys.com>
Subject Re: __stdcall ?
Date Tue, 10 May 2005 00:27:27 GMT
The only way I have gotten it to work is by copying log4cxxd.dll to
system32.

"Owen Corpening" <ocorpening@acornsys.com> wrote in message
news:d5nqph$e2f$1@sea.gmane.org...
> I am writing some installation code, and wanted to include logging in it.
Do
> I have to install lib4cxxd.dll before I can use it?
>
> Do I just add it to the PATH? or LIBPATH?
>
> The code used in a .msi must be __stdcall, does that have an effect? I
> haven't crossed this bridge before. Here is my code:
>
> extern "C" UINT __stdcall ValidateActuateiServerSettings(MSIHANDLE
hInstall)
> {
> char ServerPort[MAX_PATH];
> DWORD ServerPortLen = MAX_PATH;
> BasicConfigurator::configure();
> LoggerPtr rootLogger = Logger::getRootLogger();
>
> LOG4CXX_INFO(rootLogger, "Entering ValidateActuateiServerSettings");
> MsiGetProperty (hInstall, "ISERVERPORT", ServerPort, &ServerPortLen);
> MsiSetProperty (hInstall, "PORTBUSY", ServerPort[0] == '1' ? "1" : "0");
> LOG4CXX_INFO(rootLogger, "Exiting ValidateActuateiServerSettings");
>
> return ERROR_SUCCESS;
> }
>
>
>
>




Mime
View raw message