What is needed:
Dev Branch:
Building and testing the whole C++ project. (OS: Linux only)
Master Branch:
Buidling C++ ExecutionGraphServer, and GUI-Client for
Stiching together the ExecutionGraphServer into the Electron App (urgh...)
Approaches:
-
Make docker containers with all dependecies installed (linux: ubuntu, macOs?, windows??) and use them to build the whole setups. Where can we setup this stuff? Travis? GitLab?
-
Write Travis bash scripts -> to build at least for ubuntu and macOs... and AppVeyor for Windows.
Second approach sucks but is the way people to it ...? However with the docker approach we can run the build locally and its not that frustrating. We can also just Setup Travis Bash scripts to run docker and publish the docker containers and use them from Travis...
Everything could be steered with cmake -> Building C++ /Building GUI-Client with npm,
Fixing stuff for the Electron-App, placing the DLL at the right place (OS dependent shit...)
@simonspoerri what do you think?
What is needed:
Dev Branch:
Building and testing the whole C++ project. (OS: Linux only)
Master Branch:
Buidling C++ ExecutionGraphServer, and GUI-Client for
Stiching together the ExecutionGraphServer into the Electron App (urgh...)
Approaches:
Make docker containers with all dependecies installed (linux: ubuntu, macOs?, windows??) and use them to build the whole setups. Where can we setup this stuff? Travis? GitLab?
Write Travis bash scripts -> to build at least for ubuntu and macOs... and AppVeyor for Windows.
Second approach sucks but is the way people to it ...? However with the docker approach we can run the build locally and its not that frustrating. We can also just Setup Travis Bash scripts to run docker and publish the docker containers and use them from Travis...
Everything could be steered with
cmake-> Building C++ /Building GUI-Client with npm,Fixing stuff for the Electron-App, placing the DLL at the right place (OS dependent shit...)
@simonspoerri what do you think?