Re: Compiler option changes (and other patches)

Josh Clark wrote: > The current version from littletux.net has the PDB > change in it twice. This first time is too early (the lib.dir directory > isn't set yet. > > see line 339 of build.xml. > > > > > Thanks, I will fix it. > Also, apr now has 1.2.2. I don't need the

Re: Compiler option changes (and other patches)

The current version from littletux.net has the PDB change in it twice.  This first time is too early (the lib.dir directory isn't set yet. see line 339 of build.xml.               Also, apr now has 1.2.2.  I don't need the patch file but I do error out the first time

Re: Compiler option changes (and other patches)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Clark wrote: > Andreas, > > I was trying to use your daily build, but had some issues... > > 1. The websites for apr do not have apr 1.1.0 anymore. I had to use the > ones I had downloaded previously. They seem to have released 1.2.1 recently.

Re: Compiler option changes (and other patches)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Clark wrote: > For the PDB changes to the build files... > > For aprutil-build.xml, the following line > > > > needs to be changed to > > True. Changed in the patchfile, should be in the next daily build. Thanks & Best Regar

Re: Compiler option changes (and other patches)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Clark wrote: > > Sorry. One more thing... > > You are missing outputdebugstringappender.cpp in the src directory for > your daily build. Thanks. It was missing from Makefile.am (since its Windows specific) and was therefore not part of the dist

Re: Compiler option changes (and other patches)

g, so let me know if there's a better way to do this...First, thanks for the patches. I have integrated the Compiler option changes and the ODBC stuff in my daily build at http://www.littletux.net/log4cxxIt would be good if you could use the .tar.gz file provided there,because it already co

Re: Compiler option changes (and other patches)

s/patch> thing, so let me know if there's a better way to do this...First, thanks for the patches. I have integrated the Compiler option changes and the ODBC stuff in my daily build at http://www.littletux.net/log4cxxIt would be good if you could use the .tar.gz file provided there,because it

Re: Compiler option changes (and other patches)

the cvs/patch> thing, so let me know if there's a better way to do this...First, thanks for the patches. I have integrated the Compiler option changes and the ODBC stuff in my daily build at http://www.littletux.net/log4cxxIt would be good if you could use the .tar.gz file provided th

Re: Compiler option changes (and other patches)

On Sep 14, 2005, at 10:22 AM, Josh Clark wrote: Maybe I'm just dense, but when I try to submit a bug report, the only project available is Cocoon 2. Am I missing something? Try navigating in from http://issues.apache.org/jira. Also, are you saying I should submit all three changes? As s

Re: Compiler option changes (and other patches)

Maybe I'm just dense, but when I try to submit a bug report, the only project available is Cocoon 2.  Am I missing something? Also, are you saying I should submit all three changes? As separate bugs/enhancements? I realize the MySql appender is windows only right now.  I just don't have access to

Re: Compiler option changes (and other patches)

Hi Josh, Josh Clark wrote: Hopefully this is the correct forum to post this. I'm new to the cvs/patch thing, so let me know if there's a better way to do this... First, thanks for the patches. I have integrated the Compiler option changes and the ODBC stuff in my daily bui

Compiler option changes...

Hopefully this is the correct forum to post this.  I'm new to the cvs/patch thing, so let me know if there's a better way to do this... I build log4cxx as a static library that I link into my own logging dll.  In debug builds (on Windows using VC 2003) of my dll, I would get warnings complaining t