Issue Details (XML | Word | Printable)

Key: LOGCXX-53
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Michaël CATANZARITI
Reporter: Ivo Gaydajiev
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Log4cxx

Problems compiling with MsDev 6.0 (space in paths)

Created: 10/Jan/05 08:04 PM   Updated: 11/Feb/05 01:29 PM
Return to search
Component/s: Build
Affects Version/s: 0.9.7
Fix Version/s: 0.10.0

Time Tracking:
Not Specified

Environment: Windows 2000

Resolution Date: 11/Feb/05 01:29 PM


 Description  « Hide
trying to build the log4cxx with (static library) MicrosoftVisual C++ 6.0 using
\log4cxx-0.9.7\msvclog4cxx.dsw
leads to
-----------------------------------------------------
Performing Custom Build Step on ..\..\include\log4cxx\nt\EventLogCategories.mc
MC: Compiling ..\..\include\log4cxx\nt\EventLogCategories.mc
Microsoft (R) Incremental Linker Version 6.00.8447
Copyright (C) Microsoft Corp 1992-1998. All rights reserved.
LINK : fatal error LNK1181: cannot open input file "log4xxx\cpp\log4cxx-0.9.7\msvc\Lib\Unicode_R\NTEventLogAppender.dll"
Error executing c:\winnt\system32\cmd.exe.

log4cxxs.lib - 1 error(s), 0 warning(s)

--------------------------------------------------------

This happens only if in the path where the log4cxx is extracted has space ' ' fo example
"C:\Downloads\software\Logger\Apache log4xxx\cpp\log4cxx-0.9.7\msvc"

if you cut the space from "\Apache log4xxx" for example :
"C:\Downloads\software\Logger\Apachelog4xxx\cpp\log4cxx-0.9.7\msvc " you can build the project successfully

The problem occures also and for \log4cxx-0.9.7\msvc\dll\dll.dsp

I guess the problesm is in the .dsp files because the path are not quted. I have tested it only with MsDev 6.0 but it is possible to occure also and with .Net.




 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Curt Arnold added a comment - 11/Feb/05 01:29 PM
The current CVS HEAD no longer provided prebuilt MSVC projects but instead uses an Ant build script to build log4cxx which can also generate MSVC projects. I was able to successfully build log4cxx and pass the unit tests on a path with embedded spaces and the generated MSVC project files seemed to work fine. I did have to make some minor modifications to a few unit tests so the filename substition would occur before other replacements.