As Open Ephys is moving towards utilizing CI for different repos (such as the Sockets repo, and the Miniscope docs), we will need to make a decision about how this will look for liboni. Here we can start a discussion and start thinking about which questions are most important.
Also important to discuss how to update the existing libraries that point to liboni and clroni to minimize disruptions.
We probably need to separate liboni, cpponi, and clroni into different repos. clroni is used as a NuGet package, so CI would be useful there, but does liboni need to be packaged as a NuGet package as well? How should clroni link to liboni as a library? Submodules? DLLs?
The different testing programs (oni-repl and clroni-repl) might need to go into separate repos as well. While these programs do not need NuGet packages, it would be helpful to use CI to compile releases (i.e., pre-build executables) after updates.
As Open Ephys is moving towards utilizing CI for different repos (such as the Sockets repo, and the Miniscope docs), we will need to make a decision about how this will look for liboni. Here we can start a discussion and start thinking about which questions are most important.
Also important to discuss how to update the existing libraries that point to liboni and clroni to minimize disruptions.
We probably need to separate liboni, cpponi, and clroni into different repos. clroni is used as a NuGet package, so CI would be useful there, but does liboni need to be packaged as a NuGet package as well? How should clroni link to liboni as a library? Submodules? DLLs?
The different testing programs (oni-repl and clroni-repl) might need to go into separate repos as well. While these programs do not need NuGet packages, it would be helpful to use CI to compile releases (i.e., pre-build executables) after updates.