harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Deakin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-561) Modularise native include directories
Date Mon, 05 Jun 2006 16:26:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-561?page=all ]

Oliver Deakin updated HARMONY-561:

    Attachment: modularise.includes.sh

To apply these patches, please first run modularise.includes.sh in the root directory of your
classlib/trunk checkout. Then apply the modularise.includes.diff patch.

modularise.includes.sh creates modules/<modulename>/src/main/native/include directories
in luni and archive, and then moves header files from native-src/<platform>/include
into their appropriate location.
Some files that are not actually being used by more than one native component are moved into
their relevant component instead of being shared.

modularise.includes.diff patches up the build system to understand the new include locations,
and to share the necessary includes at build time.

> Modularise native include directories
> -------------------------------------
>          Key: HARMONY-561
>          URL: http://issues.apache.org/jira/browse/HARMONY-561
>      Project: Harmony
>         Type: Improvement

>   Components: Classlib
>     Reporter: Oliver Deakin
>  Attachments: modularise.includes.diff, modularise.includes.sh
> There has been discussion on harmony-dev about moving the natives into the modules directory
> One of the first steps towards achieving this goal is to move the contents of the native-src/<platform>/include
directories into their relevant modules, and alter the build.xml's of those modules to move
them into a shared place at build time (i.e. <hdk>/include [2]).
> I will attach a proposed patch to make these changes.
> [1] http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/200605.mbox/%3c4463654A.3080105@googlemail.com%3e
> [2] http://incubator.apache.org/harmony/subcomponents/classlibrary/hdk.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message