Wiki source code of Usage for Windows
Version 29.1 by Quinton Dolan on 2008/04/11 02:07
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | {{warning}} | ||
2 | Work in progress | ||
3 | {{/warning}} | ||
4 | |||
5 | {{toc/}} | ||
6 | |||
7 | = Moving the WebObjects frameworks from a Mac to a Windows machine = | ||
8 | |||
9 | The WebObjects frameworks are part of the Xcode tools distribution (available on the Mac OS X DVD, or as a download from Apple, see below) which cannot be installed on a Windows (or any Linux/UNIX variant) machine directly. So, before developing on Windows, you will need to get access on a Mac, make a archive of the frameworks and move this archive to your Windows machine. You can extract the frameworks from XCode without having to install them on the intermediate Mac. | ||
10 | |||
11 | * Obtain Xcode 2.5 (if you want to work with WebObjects 5.3), or Xcode 3.0 (if you want to work with WebObjects 5.4) at [[ADC>>url:http://developer.apple.com/tools/download/||shape="rect"]] – these are in the form of large (about 1 GB) disk images. Note that you will need to sign up for an ADC membership, but the "online" membership is free. | ||
12 | |||
13 | * Mount, on a Mac, the DMG file. Then, for XCode 2.5 / Mac OS X Tiger: | ||
14 | |||
15 | {{code}} | ||
16 | |||
17 | cp /Volumes/Xcode\ Tools/Packages/Packages/WebObjectsRuntime.pkg/Contents/Archive.pax.gz /tmp | ||
18 | cd /tmp | ||
19 | unzip Archive.pax.gz | ||
20 | pax -r -f Archive.pax | ||
21 | tar cf WebObjectsRuntime.tar Library System | ||
22 | cp WebObjectsRuntime.tar -> Windows | ||
23 | |||
24 | {{/code}} | ||
25 | |||
26 | ... and for XCode 3.0 / Mac OS X Leopard (since Installer packages are created differently in Leopard): | ||
27 | |||
28 | {{code}} | ||
29 | |||
30 | mkdir -p /tmp/wo ; cd /tmp/wo | ||
31 | xar -vxf "/Volumes/Xcode Tools/Packages/WebObjectsRuntime.pkg" ; pax -rzf Payload | ||
32 | tar cf WebObjectsRuntime.tar Library System | ||
33 | cp WebObjectsRuntime.tar -> Windows | ||
34 | |||
35 | {{/code}} | ||
36 | |||
37 | = Create the file structure on your Windows machine = | ||
38 | |||
39 | 1) Create the structure: | ||
40 | C:\Apple | ||
41 | C:\Apple\Local\Library\Frameworks (equivalent to /Library/Frameworks on the Mac) | ||
42 | C:\Apple\Library\Frameworks (equivalent to /System/Library/Frameworks on the Mac) | ||
43 | |||
44 | 2) Copy all the frameworks from /System/Library/Frameworks on a Mac that are named Java* except for JavaScriptCore and JavaVM to C:\Apple\Library\Frameworks | ||
45 | |||
46 | {{code}} | ||
47 | |||
48 | mv WebObjectsRuntime.tar/Library/* C:\Apple\Local\Library\Frameworks | ||
49 | mv WebObjectsRuntime.tar/System/Library/* C:\Apple\Library\Frameworks | ||
50 | |||
51 | {{/code}} | ||
52 | |||
53 | {{warning}} | ||
54 | 3) If you copied a 5.2, you will need to put a Windows License.key in JavaWebObjects.framework/Resources. If you copied a 5.3, I think it's a universal license key. | ||
55 | {{/warning}} | ||
56 | |||
57 | 4) Create a wobuild.properties file in C:\Documents and Settings\<your user>\Library with the contents: | ||
58 | wo.woroot=C:/Apple | ||
59 | wo.wolocalroot=C:/Apple/Local | ||
60 | wo.wosystemroot=C:/Apple | ||
61 | wo.homeroot=C:/Temp | ||
62 | eclipse.home=C:/Programs Files/eclipse | ||
63 | wo.dir.library.frameworks=C:/Apple/Library/Frameworks | ||
64 | |||
65 | = Install Eclipse and WOLips = | ||
66 | |||
67 | Install [[Eclipse and WOLips>>url:http://wiki.objectstyle.org/confluence/display/WOL/Install+WOLips+with+Eclipse+Update+Manager||shape="rect"]] | ||
68 | |||
69 | = Notes = | ||
70 | |||
71 | That should be it, I think? The things that are problematic right now on Windows: | ||
72 | 1) The {{code language="none"}}woproject/*.patternset{{/code}} don't work quite right on Windows with older versions of WOLips. If you don't have subfolders in your Resources/Components/etc, you can work around it by converting {{code language="none"}}Components/**/*/etc/**{{/code}} to {{code language="none"}}Components/*{{/code}}, same w/ Resources and WebServerResources. Alternatively you can use a recent nightly build of WOLips where this bug has been fixed. | ||
73 | 2) Couple images have backgrounds that should not | ||
74 | 3) Outline view in component editor is not right | ||
75 | 4) AutoOpenInBrowser doesn't work unless you override Application._isSupportedDevelopmentPlatform to return true | ||
76 | |||
77 | I THINK that was it, but there might have been a couple other misc items .. I'll have to go back through and doublecheck. |