3 A typical project architecture would be :
20 │ │ │ │ └── autobuild.in
22 │ │ │ │ └── autobuild.in
24 │ │ │ └── autobuild.in
26 │ │ │ ├── config.cmake.sample
28 │ │ │ └── macros.cmake
30 │ │ │ └── config.deb.in
32 │ │ │ └── config.spec.in
35 │ │ ├── config.xml.in.sample
36 │ │ ├── icon-default.png
37 │ │ ├── icon-html5.png
38 │ │ ├── icon-native.png
40 │ │ └── icon-service.png
57 | # | Parent | Description |
58 | - | -------| ----------- |
59 | \<root-path\> | - | Path to your project. Hold master CMakeLists.txt and general files of your projects. |
60 | conf.d | \<root-path\> | Holds needed files to build, install, debug, package an AGL app project |
61 | app-templates | conf.d | Git submodule to app-templates AGL repository which provides CMake helpers macros library, and build scripts. config.cmake is a copy of config.cmake.sample configured for the projects. SHOULD NOT BE MODIFIED MANUALLY !|
62 | autobuild | conf.d | Scripts generated from app-templates to build packages the same way for differents platforms.|
63 | cmake | conf.d | Contains at least config.cmake file modified from the sample provided in app-templates submodule. |
64 | wgt | conf.d | Contains at least config.xml.in template file modified from the sample provided in app-templates submodule for the needs of project (See config.xml.in.sample file for more details). |
65 | packaging | conf.d | Contains output files used to build packages. |
66 | \<libs\> | \<root-path\> | External dependencies libraries. This isn't to be used to include header file but build and link statically specifics libraries. | Library sources files. Can be a decompressed library archive file or project fork. |
67 | \<target\> | \<root-path\> | A target to build, typically library, executable, etc. |
69 ## Manage app-templates submodule
73 You may have some news bug fixes or features available from app-templates
74 repository that you want. To update your submodule proceed like the following:
77 git submodule update --remote
78 git commit -s conf.d/app-templates
81 This will update the submodule to the HEAD of master branch repository. Save
82 the modification by commiting it in your master git project.
84 ### Checkout submodule to a git tag
86 You could just want to update at a specified repository tag or branch or commit
87 , here are the method to do so:
90 cd conf.d/app-templates
91 # Choose one of the following depending what you want
92 git checkout <tag_name>
93 git checkout --detach <branch_name>
94 git checkout --detach <commit_id>
97 git commit -s conf.d/app-templates