Development/Tutorials/Necessitas/Assets: Difference between revisions
Bog dan ro (talk | contribs) |
Bog dan ro (talk | contribs) |
||
| Line 2: | Line 2: | ||
Android assets are read-only arbitrary files bundled in their raw form into your package.Necessitas project provides seamless integration with android assets, meaning that you can access any asset files as you access any ordinary files. | Android assets are read-only arbitrary files bundled in their raw form into your package.Necessitas project provides seamless integration with android assets, meaning that you can access any asset files as you access any ordinary files. | ||
=== | === Deploy assets === | ||
<syntaxhighlight lang="make"> | |||
# assuming we want to deploy qml/foo/main.qml file | |||
delployment.files=qml/foo/main.qml | |||
android { #define an android block | |||
delployment.path=/assets | |||
} else : symbian { | |||
delployment.path=/opt/$${TARGET} | |||
} | |||
INSTALLS += delployment | |||
</syntaxhighlight> | |||
=== Access assets === | === Access assets === | ||
Revision as of 11:47, 30 October 2011
Android assets
Android assets are read-only arbitrary files bundled in their raw form into your package.Necessitas project provides seamless integration with android assets, meaning that you can access any asset files as you access any ordinary files.
Deploy assets
# assuming we want to deploy qml/foo/main.qml file
delployment.files=qml/foo/main.qml
android { #define an android block
delployment.path=/assets
} else : symbian {
delployment.path=/opt/$${TARGET}
}
INSTALLS += delployment