Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Directory layout of Symbian projects

From Wiki
Jump to: navigation, search
Article Metadata
Article
Created: tote_b5 (22 Mar 2007)
Last edited: hamishwillee (20 Jul 2012)

Before you write a line of code, it will help to understand the directory structure under which your source and project files should be stored. If you look at the example code accompanying your SDK, or use project wizards from an IDE to create a UI application, you’ll see examples of the typical layout used to organise a project.

A good directory layout is invaluable for keeping track of your code as the project grows. It’s usual to separate the project files, which will be described shortly, from the source code, which is itself split further into header files, such as .h and .hrh, and implementation files, such as .cpp. Resources, such as .bmp or .wav files used by the application, usually go into yet another separate directory. Test code should also be stored apart from production code.

Thus, a typical UI application would have the following directory structure and files.

data Resource specification files (.rss)
gfx Application resources such as bitmaps or audio files
group Project files (e.g. MMP file and bld.inf)
inc Header files (typically .h, .hrh and .inl)
src Short for 'source', contains the implementation code in .cpp files
test Test code
This page was last modified on 20 July 2012, at 07:21.
65 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×