Fulltext results:
- compiling_and_running_1.15_or_earlier_qmake
- iles are deployed under **distrib\products**. The directory structure mirrors the one that is created by the distributi... ad'' - Set **distrib\products** as the working directory. ==== Mac OS X ==== - Set **%{buildDir}/cli... '' - Set **%{buildDir}/client** as the working directory. ==== Unix ==== - Modify the Run configurat... f how to use it: you will need to create an empty directory where the generated binaries and other build file
- file_system
- . It also contains semantic information about the structure and content of the tree, allowing others to know ... objects attached to the folders. For instance, a DirectoryFeed will generate the appropriate File and Folder instances for a directory in the native file system. The file system can b... for instance when native files get deleted in the directory a folder is feeding on. The feeds are responsible
- quick_guide_to_amethyst
- rest of the CMake projects. - Create a build directory. This should be outside the Doomsday source tree.... rectory called //inst// under the Amethyst source directory. ===== Generating documents ===== To genera... on Unix, run this command in the Amethyst //doc// directory: <code> # amethyst -dHTML guide.ame > guide.htm... uide on Windows, run this command in the //inst// directory: <code> # amethyst -dTXT -i../lib -oguide.txt .
- directory_structure
- {{update}} This article describes the standard directory structures used in the project: source code directories, runt... me directories on various platforms. ⇒ //"Source Directory Structure Proposal" by skyjake on April 14, 2006 at 13:56 o... ringing some consistency into the Doomsday source directory structure. I think the following new principles should form the basis of a new directory structure. * All file and directory names should be in