Nathan, thank you for creation of the trunk/working_jdktools.
Geir, Please look at comment and scripts attached to the HARMONY-2180. I tried to make them trivial so that reviewing doesn't take much time. Proposed build system has two levels of enrties: - working_jdktools/build.xml which can be used for processing all or selected modules. To be used in federated build; - working_jdktools/modules/$M/build.xml used for processing the $M module. These module-level build.xml files can be used while working with single module. The working_jdktools/make/ dir contains definitions imported by modules' build.xml files so few simple buildfiles are required in each module directory. I'm going to complete the HARMONY-2180 sub-task in few days to provide final script set. Thank you -Ilya On 11/13/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Can you please give us an idea of what you have right now? There's no way we can participate with you if we don't have an idea of current status... geir Ilya Neverov wrote: > On 10/31/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > [skip] >> > Assumptions which look reasonable for jdktool's build subsystem: >> > >> > 1) it works in presence of built classlib (as HDK binaries or as a >> > result of classlib phase of overall build); >> >> yes - think of the same trick we do w/ DRLVM to "reach over" to find it. >> I'd imagine the federated build to then have : >> >> trunk/ >> working_classlib/ >> working_vm/ >> working_jdktools/ >> > > Commiters, > > Could you please create empty directory "trunk/working_jdktools". > > I need it to check building jdktools as part of the federated build. > Without having the "working_jdktools/" in the repository the moving > sources and patching buiild files would require additional manual > steps. > > Thank you. > -Ilya >
