Difference between revisions of "Developer's Corner"
Cholmondely (talk | contribs) m (Retagged as major page in "Oolite Development") |
|||
| (8 intermediate revisions by one other user not shown) | |||
| Line 9: | Line 9: | ||
* [[Cross Platform IDEs]] | * [[Cross Platform IDEs]] | ||
* [[Compiling with Clang instead of gcc]] (Windows/Linux) | * [[Compiling with Clang instead of gcc]] (Windows/Linux) | ||
| + | * [[Oolite build system]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== OS Specific parts == | == OS Specific parts == | ||
| Line 39: | Line 30: | ||
|} | |} | ||
| − | ==Releasing the code== | + | == Releasing the code == |
Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'. | Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'. | ||
If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]]. | If you are convinced the current status should be published as 'stable' or 'release', follow the [[Oolite Release Process]]. | ||
| − | |||
| − | |||
== Hints == | == Hints == | ||
| Line 54: | Line 43: | ||
To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules | To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules | ||
| + | |||
| + | |||
| + | |||
| + | [[Category:Oolite Development| ]] | ||
Latest revision as of 16:31, 14 July 2026
Here you will find information that helps understanding the Oolite source code, build and test the project.
- Contributing to the project
- Release Process
- Branding, Branding History
- Oolite API documentation
- Doxygen Documentation
- Code Coverage Report
- Cross Platform IDEs
- Compiling with Clang instead of gcc (Windows/Linux)
- Oolite build system
OS Specific parts
| Procedure | Apple Mac | Linux | Windows |
|---|---|---|---|
| Setting up a development environment | Development on Apple Mac, Cross Platform IDEs | Development on Linux, Cross Platform IDEs | Development on Windows, Cross Platform IDEs |
| Compiling | Compiling on Apple Mac | Compiling on Linux | Compiling on Windows |
| Testing | Testing on Apple Mac, Common Testing | Testing on Linux, Common Testing | Testing on Windows, Common Testing |
| Packaging into Installer | Installer on Apple Mac | Installer on Linux | Installer on Windows |
| Running | Running Oolite-Mac |
Releasing the code
Once you developed a while you might no longer be happy that all you have created is called 'nightly' or 'prerelease' or 'unstable'.
If you are convinced the current status should be published as 'stable' or 'release', follow the Oolite Release Process.
Hints
The code is organized across several git repositories. The main one refers to the others as submodules - but always to a concise commit.
If you need to update submodules you also need to tell people to update the reference in the main repository. Here you can see that handling submodules can lead to strange effects: https://bb.oolite.space/viewtopic.php?f=3&t=21470
To learn mode about submodules read the fine manual at https://git-scm.com/book/en/v2/Git-Tools-Submodules
