Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

mobile app "build" folder

i couldn't find anything about this issue here:
what is the correct structure of the "build" folder inside a Titanium mobile application?
there's "src" but it seems to be auto-generated, and so are the XML files, and the "bin" folder.

can you please elaborate on what happens there when i launch my app in an Emulator? for example, Android 1.6?

— asked April 11th 2010 by Tomer Sole'
  • android
  • build
  • files
  • folders
  • windows

2 Answers

  • There are many steps in the process so I'm not sure what level of information you're after.

    The src folder contains classes that extend the core Titanium classes to give your Titanium Android application a unique package and name. That name is taken from the appid and title as entered during creation. The bin folder is a temporary workplace where the intermediary and final .apk are generated. The XML files are configuration and source files required by an Android application.

    When you launch your app in the emulator a build is done that generates/updates the AppInfo.java file from the contents of your tiapp.xml, copies the Resources, compiles your code with Titanium code, packages up the resources and class files, signs it with a key, installs or re-installs it on the emulator and then launches it.

    — answered April 11th 2010 by Don Thorp
  • thanks.

    can you also please explain to me, if it's not too hard, what is the "assets" and "sim" folders directly under build/[platform] , as well as how can i use the "res" folder and its xml config file to my advantage, if i'm planning different user interfaces for different clients, for example? i couldn't find anything useful about the res folder in http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=res+folder+site:http://appcelerator.com

    — answered April 11th 2010 by Tomer Sole'
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.