In this article we describe the framefork core and Standard Package directory structure. You may take it as example when creating your own packages. The following are the names relative to the directory where you have the framework installed.
In the integration mode the structure is the same as described below except for the removed in such a case some folders and both binaries and intermediary files are placed in the application data folder(usually C:\ProgramData) inside Nitisa\VERSION subfolder, where VERSION is the installed extension version(for example the directory will be C:\ProgramData\Nitisa\9.0.0 if you install 9.0.0 release). There will be bin and obj subdirectories inside with the same structure as corresponding ones described below. The source code is also installed in one of Visual Studio extensions folder. Anyway, when using extension to create projects you don't have to worry about it as all include and library directories are set automatically to the correct ones and needed static libraries are built automatically as well.
The Nitisa framework standalone installation has the following directory structure. This is a complete directory structure after building all configurations for all available platforms. Some folders are created automatically and do not exist after unpacking.
Important note about Packages directory. We recommend install a source code of packages here but it is not mandatory. Packages may also be installed in their own directories. In this case you will need to add those directories to your project include pathes or to include them by absolute path(which is a bad idea).
The Android part of the project depends on several third-party libraries which are placed inside Dependencies directory. They are
The Linux part of the project depends on several third-party libraries which should be installed on the Linux machine you use for building. They are
The names can be different on different linuxes. Please use search if there are no available for your Linux packages with the names above.