On 6/24/06, Andrey Chernyshev [EMAIL PROTECTED] wrote:
I wanted to add that patching ant with cpptasks as it is done today should
not
be allowed since system wide installations are usually write protected.
:)
Note that when we're finished, DRLVM shouldn't do anything to the
filesystem
I now have drlvm working w/ independent classlib and configure/make
building of APR on linux.
This is great, thanks! One more suggestion - what if we try using the
precompiled binaries for APR, Log4cxx? Their compilation takes the
significant time and may be extra cause of various building
Andrey Chernyshev wrote:
I now have drlvm working w/ independent classlib and configure/make
building of APR on linux.
This is great, thanks! One more suggestion - what if we try using the
precompiled binaries for APR, Log4cxx?
What I want to do is remove the dependency builds completely
On Friday 23 June 2006 00:44 Geir Magnusson Jr wrote:
Does something prevent us from keeping these binaries under SVN
similarly how the icu libraries are kept? Is there any licensing
issues given that APR/Log are Apache projects?
These binaries will have to be prepared stored for each
Gregory Shimansky wrote:
On Friday 23 June 2006 02:18 Geir Magnusson Jr wrote:
We would be able to do it if really necessary, but I'd rather avoid if
we can. I do think that the current DRLVM shows that it can be avoided
(so we have a way for people to get started) as well as the
I now have drlvm working w/ independent classlib and configure/make
building of APR on linux.
I had a lot of fun working through a lot of the gcc issues that others
have. It was a good refresher course for me. It's working on Ubuntu
6.whatever using gcc/g++ version 3.4 and Sun's java 5.
I can
