Skip to Content

Changes for page Embedding WOFrameworks

Last modified by Gavin Eadie on 2011/07/29 18:09
From version 44.1
edited by Ulrich Köster
on 2006/09/08 05:53
Change comment: There is no comment for this version
To version 45.1
edited by Ulrich Köster
on 2006/09/08 05:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,23 +1,11 @@
1 -Example for embedding WOFrameworks.
1 +A good idea is to create your own targets in the build.xml or even create your own build.xml (with a different name).
2 2  
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.
3 +This leaves the door open for an update of the default build.xml.
4 4  
5 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 6  
7 -The [[^packageandgobuild.xml]] from the application. Two minor changes to the default build.xml:
8 -(Applied to the compile and application target.)
7 +The [[^packageandgobuild.xml]] from the application. One minor change to the default build.xml:
9 9  
10 -{{code}}
11 -
12 -<!-- package and go example-->
13 -<frameworks root="../packageandgo/frameworks" embed="true">
14 - <include name="*.framework"/>
15 -</frameworks>
16 -
17 -{{/code}}
18 -
19 -
20 -
21 21  The [[^build.xml]] from the packageandgo folder:
22 22  
23 23  Just invoke ant in the packageandgo folder and grap the App from applications folder within the packageandgo folder