#55 0.3.4b VC7 Build under XP

[Anonymous]

Log4cpp project build problem.

First I get custom build error. I can fix it with the
replacement of the existing custom build commands
with the following (in the dsp):

"$(OutDir)\NTEventLogAppender.dll" :
$(SOURCE) "$(INTDIR)" "$(OUTDIR)"
if not exist $(OutDir) md $(OutDir)
"$(MSDEVDIR)\..\Tools\Bin\mc.exe" -h
$(OutDir) -r $(OutDir) $(projdir)\..\$(InputName).mc
"$(MSDEVDIR)\..\Tools\Bin\Bin\RC.exe" -r -
fo $(OutDir)\$(InputName).res $(OutDir)\$(InputName).rc
"$(MSDEVDIR)
\..\..\V\Bin\link.exe" /MACHINE:IX86 -dll -noentry -
out:$(OutDir)\NTEventLogAppender.dll $(OutDir)
\$(InputName).res

Now I get some warning:
..\..\include\log4cpp\Configurator.hh(21) : warning
C4275: non dll-interface class 'std::runtime_error' used
as base for dll-interface class 'log4cpp::ConfigureFailure'
C:\Program Files\Microsoft Visual Studio .NET\Vc7
\include\stdexcept(137) : see declaration
of 'std::runtime_error'
..\..\include\log4cpp\Configurator.hh(21) : see
declaration of 'log4cpp::ConfigureFailure'

which repeted 6 times both in debug and release mode.
Now I can build only Debug, because the Release stop
after calling the lib.exe.

Could anybody help me to build the Release version?

Lorinc

[Keith McCreery]

Logged In: YES
user_id=317870

I am able to get both DEBUG and RELEASE to build, but with
the same warnings. I am investigating the issue...

FYI... I am using .NET 2003 and I replaced both 'custom build'
entries for the NTEventLogCategories.mc file with...

if not exist "$(OutDir)" md "$(OutDir)"
"$(DevEnvDir)..\tools\bin\mc.exe" -h $(OutDir) -r $(OutDir)
$(ProjectDir)..\$(InputName).mc
"$(DevEnvDir)..\tools\bin\RC.exe" -r -fo $(OutDir)
\$(InputName).res $(OutDir)\$(InputName).rc
"$(DevEnvDir)..\..\vc7\bin\link.exe" /MACHINE:IX86 -dll -
noentry -out:$(OutDir)\NTEventLogAppender.dll $(OutDir)
\$(InputName).res

... which has slightly different build paths. Also, I only build
the DLL.

Keith