harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-5359) [drlvm][build] normalized ant build system
Date Sat, 29 Dec 2007 11:10:43 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alexey Varlamov updated HARMONY-5359:

    Attachment: build.zip

Unpack the archive to root dir of drlvm workspace (typically working_vm), use as usual ant

ant -Dhy.cfg=release build test ehwa.test reg.test

For a clean workspace, you'll need to run "build.bat update" as per paragraph 3.3.2 of the
old README.txt.

> [drlvm][build] normalized ant build system
> ------------------------------------------
>                 Key: HARMONY-5359
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5359
>             Project: Harmony
>          Issue Type: New Feature
>          Components: DRLVM
>            Reporter: Alexey Varlamov
>         Attachments: build.zip
> Need to refactor DRLVM build system was stated since early ages of Harmony, due to its
awkwardness and bad augmentability (one can find a lot of discussons in dev-list archives).
> Here is this long-expected feature, "normalized" ant build system, featuring:
> - improved portability, as it drops "build.bat/build.sh" wrappers and provides traditional
ant interface for users and external scripts;
> - better maintainability and robustness, as it does not use XSL preprocessing and ant-contrib
(except tests which really need "for" task);
> - much faster rebuild time even with cpptasks: void build takes only 7-8 sec (and can
be improved a bit more). Also, it is possible to build standalone component w/o rebuilding
dependencies which is also handy.
> - enhanced modularity and plugability: any component or test script can be used independently
(modulo 2-3 shared ant files), simplifying component reusing or redeployment.
> For now, the system lacks facilities for managing external dependencies, it just relies
on presence and layout of artifacts as retrieved via old build.
> The dependency management is to be refactored cross Harmony components, including classlib,
drlvm and jdktools.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message