I got around to looking at the release process earlier tonight, and I ran
into a few problems. As part of the release procedure, Maven goes and
attempts to re-build the code, which is using Ant to re-build APR and
APR-util before building log4cxx. Because of that, I can't (easily) run
through the
I can look more into the release process this week. It will probably take
a few days though, although I am traveling later this week so I should have
some free time then.
As for the PGP signing, it may be that somebody else would have to sign it
then. While I do have a PGP key, it's not associat
Guten Tag Robert Middleton,
am Samstag, 23. Juli 2016 um 22:15 schrieben Sie:
> Given my quick test, it seems like using CMake for Windows is a
> valid solution for building log4cxx, especially since the only
> dependencies for log4cxx also use CMake. Thoughts?
Sounds good to me. How to build wa
I took a bit of time to create a Visual Studio project to use the log4cxx
dll that I had created using CMake, and I was able to compile and link
cleanly. My only test was to create a project which came up and logged a
single statement, so it's not extensively tested(the logging did work
properly).
I did try to add the APR folder for 'encoding' to the apr-build.xml,
however it was not able to build it because apr_escape.c requires a
(generated) header file that the log4cxx build process does not account for.
Ultimately, it doesn't seem like a good idea to essentially duplicate the
APR build
Guten Tag Robert Middleton,
am Samstag, 16. Juli 2016 um 21:47 schrieben Sie:
> The functions that are missing are apr_generate_random_bytes and apr_
> escape_hex.
apr-build.xml:
>
>includes="**/${arch}/*.c"
>
I tried to get log4cxx to build on Windows without much luck. I think that
I have narrowed down what is going on though. First, here's what I did to
try and get it to compile.
1. Download Netbeans to have an easy Maven environment setup on Windows.
2. Open up the log4cxx project in netbea
