Wiki source code of Embedding WOFrameworks
Version 43.1 by Ulrich Köster on 2006/09/08 05:53
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
19.1 | 1 | Example for embedding WOFrameworks. |
2 | |||
![]() |
39.1 | 3 | It's an good idea is create your own targets in the build.xml or even create your own build.xml (with a different name). This leaves the door open for an update of the default build.xml. |
![]() |
19.1 | 4 | |
5 | Assume two projects: One named Foo( a framework) and the other named Uli (an application). The parent folder has another folder named packandgo. | ||
6 | |||
7 | The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml: | ||
![]() |
43.1 | 8 | (Applied to the compile and application target.) |
![]() |
19.1 | 9 | |
10 | {{code}} | ||
11 | |||
![]() |
37.1 | 12 | <!-- package and go example--> |
![]() |
19.1 | 13 | <frameworks root="../packageandgo/frameworks" embed="true"> |
14 | <include name="*.framework"/> | ||
15 | </frameworks> | ||
16 | |||
17 | {{/code}} | ||
18 | |||
![]() |
43.1 | 19 | |
![]() |
19.1 | 20 | |
21 | The [[^build.xml]] from the packageandgo folder: | ||
22 | |||
![]() |
43.1 | 23 | Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder |