Likely that you will have to link with a static library. You shouldn't
place log4cxx.dll in system32 since we have not reached the point of
promising binary compatibility between versions. Since a .msi is
likely a DLL itself (though I haven't checked that), the path is
controlled by the calli
On May 9, 2005, at 8:07 PM, Chris Williams wrote:
Here are my results compiling on solaris 10 with gcc.
The build line I used was: ant -Dapr.dir=/usr/local/apr
-Dcppunit.dir=/export/disk10/cppProjects/cppunit-1.10.2 -Dlogchar=utf8
-Dhas.wchar_t=0
I only got one error which was the following. I thi
Here are my results compiling on solaris 10 with gcc.
The build line I used was: ant -Dapr.dir=/usr/local/apr
-Dcppunit.dir=/export/disk10/cppProjects/cppunit-1.10.2 -Dlogchar=utf8
-Dhas.wchar_t=0
I only got one error which was the following. I think it might fail because
I am not using wchar_t
The only way I have gotten it to work is by copying log4cxxd.dll to
system32.
"Owen Corpening" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> 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 j
Nope, still no logfile, but thanks! I had forgotten to even suspect the
logging code, I had assumed it was my mistake.
changed to:
log4j.rootLogger=debug, stdout, R
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
# Pattern to outpu
RollingFileAppender is stubbed out in log4cxx at the moment in
anticipation of porting over the log4j 1.3 new Rolling File framework.
Try using a FileAppender. Should have RFA's on-line within the week.
pulling hair out
tried everything, this stuff is just copied out of the docs. I am expecting
to get a file "example.log", console output is not possible in this
situation. If I change the path to the property file it fails, as expected.
So at least I believe that is getting read in. I have tried sp
I did a little research on the Ant list and there are plans for an Ant
1.6.4 since 1.6.3 (released 28 April) broke javah and Clover and
apparently cpptasks. The traceback is a little strange in that it says
that the Cpptasks (loaded by Ant) can't find the o.a.t.ant.Task class
which is provided
On 09/05/2005 at 10:25 Curt Arnold wrote:
>On May 9, 2005, at 10:04 AM, Javier wrote:
>> C:\temp\log4cxx\logging-log4cxx>ant -v build-projects-vc6
>>
>> But I received the following error message:
>>
>>
>> Apache Ant version 1.6.3 compiled on April 28 2005
>>
>
>This sounds very similar to a probl
On May 9, 2005, at 10:04 AM, Javier wrote:
C:\temp\log4cxx\logging-log4cxx>ant -v build-projects-vc6
But I received the following error message:
Apache Ant version 1.6.3 compiled on April 28 2005
This sounds very similar to a problem reported by Paul Nader last week
(http://marc.theaimsgroup.com/?
Hi
I've downloaded source code from cvs and now I'm trying to build it.
I followed installation instructions as follows:
1 - I've placed cpptasks.jar and ant-contrib.jar in class-path
2 - The following files placed in the lib directory:
apr-1.1.0.tar.gz
apr-util-1.1.0.tar.gz
apr-ico
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:
e
I have hit a similar problem on Linux. The workaround that I found was to
manually call the configure script in the apr and apr-util projects that
are downloaded to the lib logging-log4cxx/lib directory.
Hope this helps.
Jim
|-+>
| | Chris
Curt, I would like to try and help the project with
Solaris 10 since I have it at home running on a Ultra
60. I did get a bit further and I plan on emailing my
steps and where I am later today.
One question about the build.xml. Is there a way to
add additional -L paths without having to modify t
14 matches
Mail list logo
