You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/02/21 12:29:06 UTC

[jira] Updated: (HARMONY-3196) [drlvm][winx64][build] enabling of drlvm build on windows/em64t

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

Gregory Shimansky updated HARMONY-3196:
---------------------------------------

    Summary: [drlvm][winx64][build] enabling of drlvm build on windows/em64t  (was: [drlvm][build] enabling of drlvm build on windows/em64t)

> [drlvm][winx64][build] enabling of drlvm build on windows/em64t
> ---------------------------------------------------------------
>
>                 Key: HARMONY-3196
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3196
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: windows/em64t
>            Reporter: Ivan Zvolsky
>         Assigned To: Gregory Shimansky
>         Attachments: drlvm_build_system.patch, drlvm_cosmetic_changes.patch, drlvm_need_impl.patch, HARMONY-3196.patch, HARMONY-3196.patch, zlib-x86_64-dll.zip
>
>
> This is a set of patches for enabling building of drlvm on windows/em64t. This issue is linked with harmony-3188, because classlib has to be built in order to start drlvm building.
> Short descriptions of attached files:
> 1) zlib-x86_64-dll.zip - zlib library windows/em64t binaries and headers, to be placed "as is" to some public server, and that location should be specified in win.properties file (see drlvm_build_system.patch, line 211)
> 2) drlvm_build_system.patch - changes to the build system of drlvm
> 3) drlvm_cosmetic_changes.patch - small changes in sources to make them buildable with msvc 2005
> 4) drlvm_need_impl.patch - changes to sources, some of which need further investigation and fixing. I've added //TODO comment for each such issue, and also a subtask of current jira will be created to reflect all such places.
> Some tips on running patched build:
> a) you will need msvc 2005
> b) execute like set COMPILER_CFG_SCRIPT=EM64T (so build.bat knows which environment to execute)
> c) execute build.bat update and then build.bat

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