en:develop:guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:develop:guidelines [2023/09/26 13:20] – prokusheven:develop:guidelines [2023/11/07 05:52] (current) – prokushev
Line 27: Line 27:
  
 <code> <code>
- +git clone https://github.com/osfree-project/osfree.git 
-    git clone https://github.com/osfree-project/osfree.git +git submodule update --init --recursive 
- +git submodule update --remote --recursive
-    git submodule update --init --recursive +
- +
-    git submodule update --remote --recursive +
 </code> </code>
  
Line 49: Line 45:
  
 For more information about build system read [[en:develop:bldenv|Build system]] document. For more information about build system read [[en:develop:bldenv|Build system]] document.
- 
-==== The Directory Tree ==== 
- 
-Please look at the source code tree to understand how files are to be placed. Please understand that the osFree source tree contains the code for an operating system and some toolkit tools. Please, DO NOT place unrelated tools or applications in this tree. The Toolkit is a set of helper utilities, which are built for development system (under which the OS is built). They are necessary for OS files building. 
- 
-==== Global/Shared/Private Headers ==== 
- 
-Each level of the source tree contains two standard directories: <code>FIX THIS! Now it's slightly different!</code> 
- 
-|//shared//  |Contains code shared among all source at this level and deeper levels | 
-|//include//  |Contains header files for the above | 
- 
-Each levels/part of the OS should have a specific prefix that allows a developer to easily find what part of the OS a header/library file belongs to. For example code shared by the whole tree should be included with: 
- 
-<code c>#include <all_shared.h></code> 
- 
-and code shared by all commandline tools should include: 
- 
-<code c>#include <cmd_shared.h></code> 
- 
-Try to create as few shared code headers as possible. Each “shared” directory should contain one (1) library (.lib) file (xxx_shared.lib) with all shared code and each “include” directory should contain one main header file including all other (xxx_shared.h). 
- 
-Example of use of common files: 
- 
-<code c> 
-// Use the normal OS/2 INCL_ since our toolkit is the OS/2 toolkit 
-#define INCL_DOSERROR 
- 
-// Include os2.h 
-#include <os2.h> 
- 
-// Include any needed normal C library 
-#include <malloc.h> 
-#include <string.h> 
- 
-// Include all shared code and shared code for command line tools 
-#include <all_shared.h> 
-#include <cmd_shared.h> 
-</code> 
  
 ==== Documentation ==== ==== Documentation ====