Like the title says.
It will always create a build in a sub dir of the current working dir.
Running the OSX version by the way on mountain lion.
Like the title says.
It will always create a build in a sub dir of the current working dir.
Running the OSX version by the way on mountain lion.
We will be removing them as they are not used at all.
Instead, why not implement it so it can be used ? :D
It seems usefull to me
You can change this in the .sencha/app/build-impl.xml
I'm used it :(
I'm using phonegap, and so, I want two separate builds for android and iOS.
So I have this in app.json:
"buildPaths": {
"testing": "build/testing",
"production": "build/production",
"package-ios": "build/ios/www",
"package-android": "build/android/assets/www",
"native": "build/native"
},
And, so, I can build my app like this:
sencha app build package-ios
or
sencha app build package-android
Now it's impossible. Is there a more correct way to do such thing?
like I said ^^Quote:
Originally Posted by mitchellsimoens
Hehe, it's not so obvious :)
I found this in build-impl.xml:
<target name="production">
<property name="args.environment" value="production"/>
</target>
<target name="testing">
<property name="args.environment" value="testing"/>
</target>
<target name="native">
<property name="args.environment" value="native"/>
</target>
<target name="package">
<property name="args.environment" value="package"/>
</target>
Adding another target don't add target to valid targets list.
Also, there is no any references to "path" or something like this in that file.
All "path" mentions are about .jar file paths which is obviously not what I need.
Sorry, my english is not very good )
We REALLY need better documentation on this Sencha Cmd stuff. It changes all the time, and it's very unclear how we're supposed to use it.
For you guys, who deal with the same problem here the solution:
As told above, buildPaths in app.json is no more used, so you can safely remove it.
But now we have build.xml in the root of the project, which is regular ant-tasks file.
So we can add our custom tasks:
I added this between <project> tags:
<target name="-after-build">
<copy todir="build/ios/www">
<fileset dir="build/PM/package"/>
</copy>
<copy todir="build/android/assets/www">
<fileset dir="build/PM/package"/>
</copy>
</target>
If you want file in other location, I think you can just add "move" files task. which will be move them to needed location.
Here is the list of available ant-tasks: http://ant.apache.org/manual/tasklist.html