forked from I2P_Developers/i2p.i2p
Realised a better way to handle the build process of both the
Browser Bundle i2p launcher, as well as the upcoming Mac OS X i2p launcher. They share some few properties and how code has to be managed for both system's update managers and so on. More details will be documentated in README.md files as well as in those commit messages I now write :)
This commit is contained in:
22
build.xml
22
build.xml
@@ -297,6 +297,28 @@
|
||||
</script>
|
||||
</target>
|
||||
|
||||
<target name="bbLauncher" depends="build">
|
||||
<sequential>
|
||||
<exec executable="sbt" dir="launcher" failonerror="true">
|
||||
<arg value="browserbundle:clean" />
|
||||
</exec>
|
||||
<exec executable="sbt" dir="launcher" failonerror="true">
|
||||
<arg value="browserbundle:assembly" />
|
||||
</exec>
|
||||
</sequential>
|
||||
</target>
|
||||
|
||||
<target name="osxLauncher" depends="build">
|
||||
<sequential>
|
||||
<exec executable="sbt" dir="launcher" failonerror="true">
|
||||
<arg value="macosx:clean" />
|
||||
</exec>
|
||||
<exec executable="sbt" dir="launcher" failonerror="true">
|
||||
<arg value="macosx:assembly" />
|
||||
</exec>
|
||||
</sequential>
|
||||
</target>
|
||||
|
||||
<target name="buildBOB" depends="buildStreaming" >
|
||||
<ant dir="apps/BOB/" target="jar" />
|
||||
<copy file="apps/BOB/dist/BOB.jar" todir="build/" />
|
||||
|
||||
Reference in New Issue
Block a user