Thanks for this. I'm figuring it out. It's pretty logical once you
start to figure it out in that you can start to guess where things might
be. There seem to be multiple places that would be valid w/
parent-child relationships, but that's no different than make. I don't
like what I'm guessing
Currently two VM subcomponents - vmi and kernel_classes - explicitly depend
on classlibs.
It's needed to get rid of this and then bootstrap prebuilt harmony classlib
while building vm subcomponents.
Here're the extracts from the correponding xml descriptors describing
dependency:
project
Geir Magnusson Jr wrote:
snip
Denis Sharypov wrote:
I would like to give the background on how the build system is designed and
then
give answers for the specific questions.
The build system provided with the VM is designed to be able to build the
whole harmony codebase
no matter how many
To stop using the auto-download classlib and harmony JIRA fetches,
and point the build at the existing classlib that's stored locally
you should do the following:
edit harmony/enhanced/drlvm/trunk/build/make/win.properties or
harmony/enhanced/drlvm/trunk/build/make/linux.properties file:
Ok - perfect - and this assumes the standard location for jars/dlls?
Denis Sharypov wrote:
To stop using the auto-download classlib and harmony JIRA fetches,
and point the build at the existing classlib that's stored locally
you should do the following:
edit
Maybe I wasn't clear.
I dont' want DRLVM to then try and build that classlib, I just want it
to use it, as is...
geir
Geir Magnusson Jr wrote:
Ok - perfect - and this assumes the standard location for jars/dlls?
Denis Sharypov wrote:
To stop using the auto-download classlib and harmony
Geir,
unfortunately the DRLVM build system doesn't allow to make you wish.
Obviously it should be modified to build the recent version of class library
from SVN
using the original build system. Whether do I correctly understand you are
interested
to have only one build system for class library?
oh.
Well, I'll try that - it's a step forward. I do think we need to
rapidly come to a conclusion on what to do. I think we want to have the
drlvm build :
1) point anywhere to a hdk/classlib that's prebuilt and just use the
artifacts in it
2) be invokable from 'above' (as described below)
3)
On 8 June 2006 at 22:42, Vladimir Gorr [EMAIL PROTECTED] wrote:
Geir,
unfortunately the DRLVM build system doesn't allow to make you wish.
Obviously it should be modified to build the recent version of class library
from SVN
using the original build system. Whether do I correctly
