Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-11 Thread Geir Magnusson Jr
Tim Ellison wrote: > Geir Magnusson Jr wrote: >> 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 >> a

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-11 Thread Tim Ellison
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 modules it contains. The

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-11 Thread Tim Ellison
Geir Magnusson Jr wrote: > 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 yep (probably

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-09 Thread Oliver Deakin
Geir Magnusson Jr wrote: 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 modul

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-09 Thread Denis Sharypov
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: ...

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-09 Thread Geir Magnusson Jr
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 a

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-09 Thread Denis Sharypov
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 modules it contains. The intent was to propose it later as

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Mark Hindess
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 correctl

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Geir Magnusson Jr
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)

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Vladimir Gorr
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? A

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Geir Magnusson Jr
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 harmon

Re: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Geir Magnusson Jr
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 harmony/enhanced/drlvm/trunk

RE: [drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-08 Thread Denis Sharypov
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: comment

[drlvm] build -unhook the classlib build and point to the existing in-tree one

2006-06-07 Thread Geir Magnusson Jr
Can I get some help from someone w/ the build? First thing, I want to stop using the auto-download classlib and harmony JIRA fetches, and just point the build at the existing classlib that's in the svn tree. IOW, I have w/ /harmony/enhanced/ as my root : drlvm/trunk/ classlib/trunk/ and I want