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-744) [classlib] Move vmi, zip, zlib and luni natives to their relevant modules
Date Tue, 04 Jul 2006 12:37:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-744?page=all ]

Oliver Deakin updated HARMONY-744:

    Attachment: modularise.zip.zlib.luni.vmi.natives.sh

Here are my proposed patches.

modularise.zip.zlib.luni.vmi.natives.sh moves the native code for zip and zlib into the archive
module, and luni and vmi into the luni module. It also moves 2 headers from fdlibm into the
shared set of header files at modules/luni/src/main/native/include/shared.

modularise.zip.zlib.luni.vmi.natives.diff updates the build system to recognise the new code

Please apply modularise.zip.zlib.luni.vmi.natives.sh before modularise.zip.zlib.luni.vmi.natives.diff.
They should both be applied to the root directory of a classlib/trunk checkout.

Once they are applied, the following svn:ignore properties will need to be set:
*.dll, *.map, *.pdb and *.so added to svn:ignore for modules/luni/src/main/native/luni and

> [classlib] Move vmi, zip, zlib and luni natives to their relevant modules
> -------------------------------------------------------------------------
>          Key: HARMONY-744
>          URL: http://issues.apache.org/jira/browse/HARMONY-744
>      Project: Harmony
>         Type: Improvement

>   Components: Classlib
>     Reporter: Oliver Deakin
>  Attachments: modularise.zip.zlib.luni.vmi.natives.diff, modularise.zip.zlib.luni.vmi.natives.sh
> The penultimate step in native modularisation. This JIRA will:
>  - Move the native code for luni and vmi into the luni module, and for zip and zlib into
the archive module.
>  - Patch the build system to understand the new code locations.
> I will attach a patch to carry these steps out.

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