Skip to content

Develop blueCFD-Core 2017-1 and port OpenFOAM 5.x to Windows #58

@wyldckat

Description

@wyldckat

Development steps:

Note: Don't forget to update issue #53 as development goes on.

  1. Resync changes which we have internally at the intersection of OpenFOAM-4.x and OpenFOAM-dev, with the fixes which were done in blueCFD-Core-4.x. Note: for both the OpenFOAM-dev and ThirdParty-dev repositories.

  2. Merge our internal branch blueCFD-Core-dev at this intersection of 4.x+dev to the intersection of 5.x+dev. Note: for both the OpenFOAM-dev and ThirdParty-dev repositories.

  3. Create the new branch blueCFD-Core-5.x and merge up to the latest commit of OpenFOAM-5.x. Note: for both the OpenFOAM-dev and ThirdParty-dev repositories.

  4. Create a new MSys2 installation on Windows for blueCFD-Core 2017 and adapt the infrastructure from blueCFD-Core 2016.

  5. Git clone OpenFOAM-dev and ThirdParty-dev repositories on Windows, by checking out the blueCFD-Core-5.x branch, adjust the infrastructure and compile OpenFOAM 5.x on Windows. Also fix the remaining loose details from steps 1 to 3, namely changes that couldn't be applied directly.

  6. Adapt to the latest MS-MPI version.

  7. Run Alltest - see if Implement the ability to run the 'tutorials/Allrun' script for just X seconds per solver #57 can be done here.

  8. If there is still enough time, see issues Bring back stack tracing #7, Check status on MSwindows/signals #4 and Using exit(1) instead of ::abort on Windows #5.

  9. Test issue CompressibleInterDyMFoam tutorial case fail to pass the test. #22 to see if it still occurs.

  10. Adapt the installer scripts from blueCFD-Core 2016-2 to 2017-1, test the installer(s) and wrap up the release - do it in issue Create the installer for blueCFD-Core 2017-1 #59.

  11. Release blueCFD-Core 2017-1 to the public,

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions