BlueM.Sim Development: Difference between revisions
Jump to navigation
Jump to search
(remove SVN references, link to GitHub) |
(→Source code: Folder structure) |
||
| Line 11: | Line 11: | ||
All source code and issues are managed on GitHub: https://github.com/bluemodel | All source code and issues are managed on GitHub: https://github.com/bluemodel | ||
Most individual BlueM components are configured to build to a common parent output folder <code>..\bin\<Platform>\<Configuration></code>. The recommended folder structure is thus to have all individual components in one single parent folder as follows: | |||
<pre> | |||
BlueM | |||
- BlueM.DLLAdapter | |||
- BlueM.LaPipe | |||
- BlueM.Sim | |||
- BlueM.Wave | |||
- BlueM.Win | |||
</pre> | |||
This also ensures that references between projects work out of the box. | |||
==Compilation== | ==Compilation== | ||
Revision as of 02:24, 23 December 2021
BlueM.Sim | Download | Application | Theory | Development
Source code
The source code consists of the following individual projects:
- BlueM.Win: .NET desktop app
- BlueM.Sim: Fortran simulation engine
- BlueM.DLLAdapter: .NET wrapper for communication between BlueM.Win and BlueM.Sim
- BlueM.LaPipe: component for water quality calculations
- BlueM.Wave: Tool for time series display and analysis
All source code and issues are managed on GitHub: https://github.com/bluemodel
Most individual BlueM components are configured to build to a common parent output folder ..\bin\<Platform>\<Configuration>. The recommended folder structure is thus to have all individual components in one single parent folder as follows:
BlueM - BlueM.DLLAdapter - BlueM.LaPipe - BlueM.Sim - BlueM.Wave - BlueM.Win
This also ensures that references between projects work out of the box.
Compilation
- → see BlueM.Sim compilation
Testing
- → see BlueM.DLLAdapterTest
Docs
BlueM.Sim:
- → siehe BlueM.Sim Code
Style
- → siehe Code-Formatierung