log4cplus-devel — Mailing list for log4cplus developers

Re: [Log4cplus-devel] *SPAM* Log4cplus_help

[Vaclav H. <wi...@us...>]

On Mon, 10 May 2010 02:12:45 -0700 (PDT), Done Gogov <> wrote:
> I have start log4cplus 1.0.4 rc-7 in visual studio 2008, and when start
> This application has failed to start because log4cplusUD.dll was not
> found.
Are you trying to execute some of the testcases? You need to copy the
log4cplusUD.dll into the testcase binary's directory.

--
VH

[Log4cplus-devel] log4cplus under VC++ 2010 Express

[Harald P. <har...@do...>]

Hallo!

I try to build log4cplus (1.1/trunk) with ms vc++ 2010 Express. There are a
view bitfalls in this case.

So i like to share my experiance:

 
 converting the msvc8 projects fails
 The 2010 Express doesn't provide x64 so I opened the project files in an
editor and removed all X64 Configurations
 
building the dll is successfull
 
a simple test-Project with linked against the dll brings link error 2019
 the reason therefor: importing the project the char-set ist multibyte - the
default charset in a new project is unicode by changing the charset every
thing work


I hope some of you can save time with this informations.

best regards 

Harry

 

Re: [Log4cplus-devel] Help needed by building log4cplus on windows and MinGW&MSYS

[Vaclav H. <wi...@us...>]

On Wed, 21 Apr 2010 13:42:50 +0200, Harald Pollak wrote:
> Hy!!!
Hi.

> 
> I'm trieing to build log4cplus ( branch 1.1 ) on Windows with MinGW and
> MSYS
> on Windows. 
I have recently moved the non-stable development to the trunk, please use
it instead of the 1.1 branch.

> 
> It seems like the buildtool allways tries to build the sockt-unix,...
and
> all other unix-specific files.
> 
> I tried following commands but none had make success, can anybody tell
me
> whats wrong?
> 
> ./configure
> 
> ./configure CXXFLAGS=LOG4CPLUS_BUILD_DLL
> 
> ./configure CXXFLAGS="-DLOG4CPLUS_BUILD_DLL -DLOG4CPLUS_USE_WINSOCK
> -DWIN32"
> 
> ...
I do not remember exactly what state is 1.1 branch in but trunk does
compile socket-unix.cxx too. However it is effectively empty file because
its contents is protected by #if defined (LOG4CPLUS_USE_BSD_SOCKETS)/#endif
which is undefined for MinGW. Unless of course there is a bug, I have not
tested MinGW builds recently.

--
VH

[Log4cplus-devel] Help needed by building log4cplus on windows and MinGW&MSYS

[Harald P. <har...@do...>]

Hy!!!

I'm trieing to build log4cplus ( branch 1.1 ) on Windows with MinGW and MSYS
on Windows. 

It seems like the buildtool allways tries to build the sockt-unix,... and
all other unix-specific files.

I tried following commands but none had make success, can anybody tell me
whats wrong?

./configure

./configure CXXFLAGS=LOG4CPLUS_BUILD_DLL

./configure CXXFLAGS="-DLOG4CPLUS_BUILD_DLL -DLOG4CPLUS_USE_WINSOCK -DWIN32"

...

 

best regards 

Harry

Re: [Log4cplus-devel] Error -: No appenders could be found

[Václav H. <v.h...@sh...>]

On Mon, 12 Apr 2010 19:06:46 +0530, Dileep Nayak <> wrote:
> Hi ,
> When this error occurred?
> 
> 
> *log4cplus:ERROR No appenders could be found for logger (error).
> log4cplus:ERROR P
> Please initialize the log4cplus system properly.”*
The warning is produced by LoggerImpl::callAppenders(). It is triggered
when you try to log something and there are not any appenders attached in
the hierarchy on the way from the particular logger to the rootLogger. Not
even your rootLogger has any appenders attached to it. IOW there is nowhere
to log the message to, it is lost.

--
VH

[Log4cplus-devel] Error -: No appenders could be found

[Dileep N. <nay...@gm...>]

Hi ,
When this error occurred?


*log4cplus:ERROR No appenders could be found for logger (error).
log4cplus:ERROR P
Please initialize the log4cplus system properly.”*

Thanks & Regards
Dileep

[Log4cplus-devel] *SPAM* log4cplus 1.0.4-RC7 released

[Václav H. <wi...@us...>]

log4cplus 1.0.4-RC7 has been released. I hope this could be the last RC for
1.0.4. Please, test it if you can.

--
VH



Version 1.0.4-RC7

  - Fixed thread safety issues with gethostbyname() by using
    getaddrinfo() instead, where available.
  - Fixed bug #2965390 - Minor internal debugging output issue.
  - Added --enable-warnings (--disable-warnings) switches to the
    configure script.
  - Added ReopenDelay property to FileAppender, allowing the appender
    to reopen output stream after write failure. (Patch #2971315)

Version 1.0.4-RC6

  - Fixed bug #2945335 - MinGW/MSYS build problems. For Windows builds
    the source now defaults to static librar/empty LOG4CPLUS_EXPORT
    macro.
  - Fixed a security problem in SyslogAppender.
  - Fixed bug #2955058 - Looping over properties during variables
    expansion.
  - Added missing dependency on log4cplus_dll project to filter_test
    project.
  - Added a constructor with Properties parameter to DenyAllFilter.
  - Reworked Layout, Appender and Filter factories registration.

Version 1.0.4-RC5

  - Implemented feature request #2927416 "Add a native Win32 Console
    Appender".
  - Loggingserver now exits with value 2 when it cannot open
    listening socket.
  - Improved Doxygen documentation.
  - Added PropertyConfigurator::getProperties() and
    PropertyConfigurator::getPropertyFilename() functions.
  - Removed LOG4CPLUS_EXPORT on SharedObjectPtr<>.
  - Turned on linker optimizations for MSVC8 builds to make resulting
    binaries slightly smaller.
  - Added --enable-runtime-pseudo-reloc linker option for Cygwin and
    Mingw. Enable --enable-auto-import linker flag also for Mingw.

Version 1.0.4-RC4

  - Fixed bug #2875993 - Implement connector thread for
    SocketAppender.
  - Improved documentation of Appenders' properties.
  - Improved behaviour of DailyRollingFileAppender.
  - Added x64 (AMD64) build configuration to MSVC8 project files.
  - Reworked MSVC8 project files to use .vsprops files to share
    project settings.
  - Moved all tests into Tests project folder.
  - Improved behaviour of ConfigurationWatchDogThread.
  - Fixed bug #2890819 - Handle empty input in towstring_internal()
    and tostring_internal().
  - Corrected VERSION and SOVERSION in CMakeLists.txt.
  - Fixed thread_test compilation on AIX.
  - Added missing syncprims.cxx file in log4cplus_static.vcproj.

Version 1.0.4-RC3

  IMPORTANT: Majority of log4cplus' source code is now licensed using
  the Apache Software License 2.0. The rest is covered by two clause
  BSD license.

  - Fixed bug #2747435. Implement handling of log4cplus.configDebug
    configuration property.
  - Fixed variables shadowing.
  - Doxygen documentation improvements and fixes.
  - Add %i PatternLayout format. It expands to process ID.
  - Fix logging macros compilation for LOG4CPLUS_SINGLE_THREADED case.
  - Fix Logger log level configuration and root Logger handling log
    level handling.

Version 1.0.4-RC2

  - Fixed bug #2834811. Accessing index 0 of empty strings.
  - Fixed bug #2834808. Memory leak in thread local storage code.
  - Removed MSVC6 directory and project files.
  - Update to libtool-2.2.6.

Version 1.0.4-RC1

  - Fixed compilation with Borland C++ Builder compiler.
  - Improved CMake build system to also build tests.
  - Fixed compilation and improved support for Windows CE.
  - Fixed compilation and improved support for Sun Studio 11 compiler.
  - Fixed use after free and improved shutdown handling in
    ConfigurationWatchDogThread.
  - Implement %H (FQDN) and %h (host name) PatternLayout format
    specifiers.
  - Fixed bug #2829604. Environment variables substitution.

[Log4cplus-devel] solved: [Fwd: Re: Patch 2971315]

[Harald P. <har...@do...>]

-------- Ursprüngliche Nachricht --------
Betreff: Re: [Log4cplus-devel] Patch 2971315
Von: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= <v.h...@sh...>
Datum: Die, 16.03.2010, 22:03
An: log...@li...

Ricardo Andrade wrote, On 16.3.2010 17:43:
> VH,
>
> A new patch was created following the your orientations.
> I really appreciate if it could be part of the next release of the
> log4cplus.
I have committed it in revision 1119 to the PRODUCTION_1_0_x
branch with only minor tweaks. Thanks.

--
VH

Now I have reinstalled cygwin. I have build and installed g++ 4.4.3.
Recompiled my code, now it works.

thanks
Harry

Re: [Log4cplus-devel] Patch 2971315

[Václav H. <v.h...@sh...>]

Ricardo Andrade wrote, On 16.3.2010 17:43:
> VH,
> 
> A new patch was created following the your orientations.
> I really appreciate if it could be part of the next release of the
> log4cplus.
I have committed it in revision 1119 to the PRODUCTION_1_0_x
branch with only minor tweaks. Thanks.

--
VH

[Log4cplus-devel] Patch 2971315

[Ricardo A. <ric...@so...>]

VH,

A new patch was created following the your orientations.
I really appreciate if it could be part of the next release of the
log4cplus.

Thank you,
Ricardo Andrade

Re: [Log4cplus-devel] problems with log4cplus and cygwin (exitcode 127)

[Václav H. <v.h...@sh...>]

Harald Pollak wrote, On 4.3.2010 13:57:
> I have changed my cygwin to 1.7.1 and took the latest log4cplus dist
> (1.0.4-rc6).
>
> I run configure, and make ( like befor on cygwin 1.5.x ) with no error
> message.
>
> I compile my testprogram ( with no errors ) and start it:
>
> $./test.exe
>
> no output comes.
>
> $ echo $?
> 127
>
> gcc  i use is
4.3.4 20090804 (release) 1 (GCC), right?

>
> log...@li...
>
> does any one have a hint for me or have the same problems?
This is AFAIK Cygwin problem. There is some sort of a problem with how the
newer GCC exports some DLL symbols and how it imports them from the DLL. It
is possible to make it work but you will have to install newer/recent
Binutils (ld) from sources. Alternatively, things might work if you disable
generation of cyglog4cplus-1.0.dll, try adding --disable-shared to the
./configure command line.

--
VH

[Log4cplus-devel] problems with log4cplus and cygwin (exitcode 127)

[Harald P. <har...@do...>]

I have changed my cygwin to 1.7.1 and took the latest log4cplus dist
(1.0.4-rc6).

I run configure, and make ( like befor on cygwin 1.5.x ) with no error
message.

I compile my testprogram ( with no errors ) and start it:

$./test.exe

no output comes.

$ echo $?
127

gcc  i use is

log...@li...

does any one have a hint for me or have the same problems?

best regards
harry

Re: [Log4cplus-devel] How do I get log4cplus to print the "header" every time?

[Václav H. <wi...@us...>]

Jim wrote, On 24.2.2010 23:16:
> I'm obviously doing something wrong.  My output looks like:
> 
> 2010-02-24 17:08:22.138 DEBUG 3055020960  main loggerbase.cpp:3944 
> Starting diagloop with 120
> -timing 118
> -timing 119
> Running procs are 0
> -Input stage activity 1
> patrol detaching
> timing 0
> 
> but the only output I'm doing is via calls like:
>         Thread::sleep (50000);
>         outString << "timing "<<timing << endl;
>         LOG4CPLUS_DEBUG (root, outString.str ());
> inside of a forever loop.  Obviously there are some other calls in the 
> loop, but this is the bit of code that generates the "timing" output.
If I understand you correctly, you are asking why are you not getting
"2010-02-24 17:08:22.138 DEBUG 3055020960  main loggerbase.cpp:3944" header
for every line? If that is the question then the answer is because the header
is only being printed for each instance of InternalLoggingEvent object that
is created internally by the LOG4CPLUS_DEBUG() macro. It is not printed for
each textual line of output.

> 
> outString is
> ostringstream outString;
> Defined earlier in the function.
> 
> I'm making a wild guess that the time isn't changing from call to call?
> 
> root is defined as:
> Logger root;
> and assigned as
>     root = Logger::getInstance ("main");
> 
> It was preceded by:
>         PropertyConfigurator::doConfigure ("/etc/VA/log4cplus.properties");
>  And that file looks like:
> log4cplus.rootLogger=DEBUG, R
> log4cplus.logger.filelogger=DEBUG, R
Your filelogger is using the same appender as rootLogger. Are you not getting
duplicate log entries if you log anything using the filelogger?

> log4cplus.appender.R=log4cplus::RollingFileAppender
> log4cplus.appender.R.File=/var/log/VA/logger.log
> log4cplus.appender.R.MaxFileSize=15MB
> log4cplus.appender.R.MaxBackupIndex=10
> log4cplus.appender.R.layout=log4cplus::PatternLayout
> log4cplus.appender.R.layout.ConversionPattern=%D{%Y-%m-%d %H:%M:%S.%q} 
> %-5p %t  %c %l %m%n
> 
> Thanks for any guidance.

--
VH

[Log4cplus-devel] How do I get log4cplus to print the "header" every time?

[Jim <ji...@fa...>]

I'm obviously doing something wrong.  My output looks like:

2010-02-24 17:08:22.138 DEBUG 3055020960  main loggerbase.cpp:3944 
Starting diagloop with 120
-timing 118
-timing 119
Running procs are 0
-Input stage activity 1
patrol detaching
timing 0

but the only output I'm doing is via calls like:
        Thread::sleep (50000);
        outString << "timing "<<timing << endl;
        LOG4CPLUS_DEBUG (root, outString.str ());
inside of a forever loop.  Obviously there are some other calls in the 
loop, but this is the bit of code that generates the "timing" output.

outString is
ostringstream outString;
Defined earlier in the function.

I'm making a wild guess that the time isn't changing from call to call?

root is defined as:
Logger root;
and assigned as
    root = Logger::getInstance ("main");

It was preceded by:
        PropertyConfigurator::doConfigure ("/etc/VA/log4cplus.properties");
 And that file looks like:
log4cplus.rootLogger=DEBUG, R
log4cplus.logger.filelogger=DEBUG, R
log4cplus.appender.R=log4cplus::RollingFileAppender
log4cplus.appender.R.File=/var/log/VA/logger.log
log4cplus.appender.R.MaxFileSize=15MB
log4cplus.appender.R.MaxBackupIndex=10
log4cplus.appender.R.layout=log4cplus::PatternLayout
log4cplus.appender.R.layout.ConversionPattern=%D{%Y-%m-%d %H:%M:%S.%q} 
%-5p %t  %c %l %m%n

Thanks for any guidance.

Jim.

Re: [Log4cplus-devel] thread safety

[Václav H. <wi...@us...>]

Reza Razavipour wrote, On 19.1.2010 23:27:
> All,
> 
> totall newbie to this topic... Is the package thread safe. Have experience
> with log4j and we saw, in very rare occasion, log messages stepping on
> each other.
Calls to Appender::doAppend() are synchronized. Unless you have created more
than one appender for the same physical destination, the messages should
never overlap.

--
VH

[Log4cplus-devel] thread safety

[Reza R. <rra...@st...>]

All,

totall newbie to this topic... Is the package thread safe. Have experience with log4j and we saw, in very rare occasion, log messages stepping on each other.

Thanks
Reza

Re: [Log4cplus-devel] license

[Václav H. <v.h...@sh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 14.12.2009 11:07, Attila Odry wrote:
> Hi Vaclav,
Hi.

> 
>  
> 
> We are going to release our new product and we are using some open
> source libraries. I am just about to finalize the about box with all the
> proper license text.
> 
> All the library we used has it’s own online page with the license or a
> link to the proper one.  Our about box has the list of libraries we use
> with the link to the license file. Log4cplus has no such a page – or I
> can not find it.
> 
> In the license file (next to the source) you have two licenses, one for
> apache 1.1, and one for log4cplus.
> 
>  
> 
> Is there any online page where this license file exist, so  I could make
> a link to that?
There is no such page.

> 
> If not, is it enough to link to apache license page?
> (http://www.apache.org/licenses/LICENSE-1.1)
IANAL but I think that all that your documentation and/or about box
needs to say is in the item 3 in the log4j license: "This product
includes software developed by the Apache Software Foundation
(http://www.apache.org/)."

Just FYI, the licensing for 1.0.4 is changing to Apache Software License
2.0, for most parts.

- --
VH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAksmPEYACgkQjksRtmO2spf12wCfTNmFbgQB04Oy2DGtxDPfWLHY
6cwAoJAc4Ra9r+d3EyxzmEh4UI+3NhCy
=5hbN
-----END PGP SIGNATURE-----

[Log4cplus-devel] license

[Attila O. <Att...@xs...>]

Hi Vaclav,

We are going to release our new product and we are using some open source libraries. I am just about to finalize the about box with all the proper license text.
All the library we used has it's own online page with the license or a link to the proper one.  Our about box has the list of libraries we use with the link to the license file. Log4cplus has no such a page - or I can not find it.
In the license file (next to the source) you have two licenses, one for apache 1.1, and one for log4cplus.

Is there any online page where this license file exist, so  I could make a link to that?
If not, is it enough to link to apache license page? (http://www.apache.org/licenses/LICENSE-1.1)

Thanks,
Attila

Re: [Log4cplus-devel] NTEventLogAppender

[Václav H. <v.h...@sh...>]

Attila Odry wrote, On 7.12.2009 14:53:
> Hi
> 
> 
> 
> I would like to set up a logger to send message into system log, using the
> NTEventLogAppender.
> 
> 
> 
> NTEventLogAppender(const log4cplus::tstring& server,
> 
> const log4cplus::tstring& log,
> 
> const log4cplus::tstring& source);
> 
> 
> 
> I can’t found any documentation (or test) for this one. Could someone 
> explain to me what those paramters for in ctor?
> 
> Regarding to log4, the source should be the source showed in event log, 
> but what about the rest?
As far as I can tell, server and source are used for first
RegisterEventSource() parameter. Log parameter is the log like "Application",
"Security", "System". Log and source parameters are used to set up some
registry keys under "SYSTEM\\CurrentControlSet\\Services\\EventLog". I do not
know much about Windows event log myself either, I am afraid I cannot help
you with this much.

--
VH

[Log4cplus-devel] NTEventLogAppender

[Attila O. <Att...@xs...>]

Hi

I would like to set up a logger to send message into system log, using  the NTEventLogAppender.

        NTEventLogAppender(const log4cplus::tstring& server,
                           const log4cplus::tstring& log,
                           const log4cplus::tstring& source);

I can't found any documentation (or test) for this one. Could someone explain to me what those paramters for in ctor?
Regarding to log4, the source should be the source showed in event log, but what about the rest?

Thanks,
Attila

Re: [Log4cplus-devel] Problems linking log4cplus 1.0.3 in VisualStudio 2005 project

[Vaclav H. <wi...@us...>]

heapifyman wrote:
> Václav Haisman schrieb:
>> heapifyman wrote, On 3.11.2009 17:49:
>>> Hello all,
>>>
>>> I managed to successfully build log4cplus in Visual Studio 2005 and now
>>> am trying to use it in my C++ project.
>>>
>>> In my project settings, I added the log4cplus include dir to Additional
>>> Includedirectories and also the msvc8\log4cplus_dll.Debug directory to
                                          ^^^^^^^^^^^^^^^^^^^

You are using the DLL that is built without the UNICODE symbol defined,
the "Character Set" option. You need match the log4cplus DLL with the
settings of your project in this respect, too. If your project's
"Character Set" option is set to "Use Unicode Character Set" then you
will need to use log4cplus DLL from one of
log4cplus_dll.{Release,Debug}_Unicode directories.

>>> Additional Librarydirectories. Further, I added log4cplusD.lib to my
>>> Linker-->Input-->Additional Dependencies (sorry if the setting's names
>>> are not correct, I only have the German version here.
>>>
>>> However, when building the project I get the following error in the
>>> Linking step:
>>> error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
>>> ""__declspec(dllimport) public: void __thiscall
>>> log4cplus::Logger::forcedLog(int,class std::basic_string<unsigned
>>> short,struct std::char_traits<unsigned short>,class
>>                                 ^^^^^^^^^^^^^^
>>
>> Your project appears to be compiling without the "Treats wchar_t as built-in
>> type" option /Zc:wchar_t. The log4cplus MSVC projects are set up with the
>> option set so that wchar_t is a distinct type instead of alias for unsigned
>> short. You could try turning the option off in log4cplus project or (which I
>> would recommend) turning the option on in your application/project.
> 
> Thanks for the quick answer, unfortunately it didn't help.
> If I recompile log4clus with "/Zc:wchar_t-" (which my project uses, as
> it is an extension of another project that uses that setting...) I get
> linking errors, the first one being:
> error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
> ""__declspec(dllimport) public: void __thiscall
> log4cplus::Logger::forcedLog(int,class std::basic_string<unsigned
> short,struct std::char_traits<unsigned short>,class
> std::allocator<unsigned short> > const &,char const *,int)"
> (__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@PBDH@Z)"
> in Funktion ""public: __thiscall
> Plateau::MyPlugin_impl::MyPlugin_impl(void)"
> (??0MyPlugin_impl@Plateau@@QAE@XZ)".
> 
> which seems to be the same as in my first posting.
> 
> If I use log4cplus in standard settings "/Zc:wchar_t" and change my
> project to that same setting, I get the following linking error:
> error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
> ""__declspec(dllimport) public: void __thiscall
> log4cplus::Logger::forcedLog(int,class std::basic_string<wchar_t,struct
> std::char_traits<wchar_t>,class std::allocator<wchar_t> > const &,char
> const *,int)"
> (__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@PBDH@Z)"
> in Funktion ""public: __thiscall
> Plateau::MyPlugin_impl::MyPlugin_impl(void)"
> (??0MyPlugin_impl@Plateau@@QAE@XZ)".
> 
> I'm really new to this whole C++ logging stuff (and c++ in general) so
> I'm really a little confused what's going on here.
> 
> I'd appreciate it if you had any more ideas.

--
VH

Re: [Log4cplus-devel] is it may unsubscribe me from the group please

[Vaclav H. <wi...@us...>]

Somayeh Bakhshaei wrote:
> Hello,
>  As no more i am working on log4cplus and beside receiving lots of mail
> from lots of mailing lists! i want to ask unsubscribe me from this group
> please.
> _______________________________________________
> Log4cplus-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cplus-devel
You can do that yourself using the mailing list at
<https://lists.sourceforge.net/lists/listinfo/log4cplus-devel>.

--
VH

[Log4cplus-devel] is it may unsubscribe me from the group please

[Somayeh B. <s.b...@ya...>]

Hello,
 As no more i am working on log4cplus and beside receiving lots of mail from lots of mailing lists! i want to ask unsubscribe me from this group please.

best regards,
Somayeh Bakhshaei



      

Re: [Log4cplus-devel] Problems linking log4cplus 1.0.3 in VisualStudio 2005 project

[heapifyman <hea...@gm...>]

Václav Haisman schrieb:
> heapifyman wrote, On 3.11.2009 17:49:
>> Hello all,
>>
>> I managed to successfully build log4cplus in Visual Studio 2005 and now
>> am trying to use it in my C++ project.
>>
>> In my project settings, I added the log4cplus include dir to Additional
>> Includedirectories and also the msvc8\log4cplus_dll.Debug directory to
>> Additional Librarydirectories. Further, I added log4cplusD.lib to my
>> Linker-->Input-->Additional Dependencies (sorry if the setting's names
>> are not correct, I only have the German version here.
>>
>> However, when building the project I get the following error in the
>> Linking step:
>> error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
>> ""__declspec(dllimport) public: void __thiscall
>> log4cplus::Logger::forcedLog(int,class std::basic_string<unsigned
>> short,struct std::char_traits<unsigned short>,class
>                                 ^^^^^^^^^^^^^^
> 
> Your project appears to be compiling without the "Treats wchar_t as built-in
> type" option /Zc:wchar_t. The log4cplus MSVC projects are set up with the
> option set so that wchar_t is a distinct type instead of alias for unsigned
> short. You could try turning the option off in log4cplus project or (which I
> would recommend) turning the option on in your application/project.

Thanks for the quick answer, unfortunately it didn't help.
If I recompile log4clus with "/Zc:wchar_t-" (which my project uses, as
it is an extension of another project that uses that setting...) I get
linking errors, the first one being:
error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
""__declspec(dllimport) public: void __thiscall
log4cplus::Logger::forcedLog(int,class std::basic_string<unsigned
short,struct std::char_traits<unsigned short>,class
std::allocator<unsigned short> > const &,char const *,int)"
(__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@PBDH@Z)"
in Funktion ""public: __thiscall
Plateau::MyPlugin_impl::MyPlugin_impl(void)"
(??0MyPlugin_impl@Plateau@@QAE@XZ)".

which seems to be the same as in my first posting.

If I use log4cplus in standard settings "/Zc:wchar_t" and change my
project to that same setting, I get the following linking error:
error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
""__declspec(dllimport) public: void __thiscall
log4cplus::Logger::forcedLog(int,class std::basic_string<wchar_t,struct
std::char_traits<wchar_t>,class std::allocator<wchar_t> > const &,char
const *,int)"
(__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@PBDH@Z)"
in Funktion ""public: __thiscall
Plateau::MyPlugin_impl::MyPlugin_impl(void)"
(??0MyPlugin_impl@Plateau@@QAE@XZ)".

I'm really new to this whole C++ logging stuff (and c++ in general) so
I'm really a little confused what's going on here.

I'd appreciate it if you had any more ideas.


> 
>> std::allocator<unsigned short> > const &,char const *,int)"
>> (__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@PBDH@Z)"
>> in Funktion ""public: __thiscall
>> Plateau::MyPlugin_impl::MyPlugin_impl(void)"
>> (??0MyPlugin_impl@Plateau@@QAE@XZ)".
>>
>> Am I missing anything in my includes or library dependencies?
>>
>> Is there some documentation available on how to setup a VS 2005 project
>> with log4cplus support?
>>
>> I'd appreciate any help.
> 
> --
> wilx
> 

Re: [Log4cplus-devel] Problems linking log4cplus 1.0.3 in VisualStudio 2005 project

[Václav H. <wi...@us...>]

heapifyman wrote, On 3.11.2009 17:49:
> Hello all,
> 
> I managed to successfully build log4cplus in Visual Studio 2005 and now
> am trying to use it in my C++ project.
> 
> In my project settings, I added the log4cplus include dir to Additional
> Includedirectories and also the msvc8\log4cplus_dll.Debug directory to
> Additional Librarydirectories. Further, I added log4cplusD.lib to my
> Linker-->Input-->Additional Dependencies (sorry if the setting's names
> are not correct, I only have the German version here.
> 
> However, when building the project I get the following error in the
> Linking step:
> error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
> ""__declspec(dllimport) public: void __thiscall
> log4cplus::Logger::forcedLog(int,class std::basic_string<unsigned
> short,struct std::char_traits<unsigned short>,class
                                ^^^^^^^^^^^^^^

Your project appears to be compiling without the "Treats wchar_t as built-in
type" option /Zc:wchar_t. The log4cplus MSVC projects are set up with the
option set so that wchar_t is a distinct type instead of alias for unsigned
short. You could try turning the option off in log4cplus project or (which I
would recommend) turning the option on in your application/project.

> std::allocator<unsigned short> > const &,char const *,int)"
> (__imp_?forcedLog@Logger@log4cplus@@QAEXHABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@PBDH@Z)"
> in Funktion ""public: __thiscall
> Plateau::MyPlugin_impl::MyPlugin_impl(void)"
> (??0MyPlugin_impl@Plateau@@QAE@XZ)".
> 
> Am I missing anything in my includes or library dependencies?
> 
> Is there some documentation available on how to setup a VS 2005 project
> with log4cplus support?
> 
> I'd appreciate any help.

--
wilx