Update library build

[abachma2]

This PR updates the CMakeLists.txt file to require at least C++ 14so that the project can be built. The project builds and the unit tests in recycle_unit_tests executable all pass locally.

[gonuke]

There were some major overhauls to Cycamore's CMake infrastructure in the 2nd half of last year that should simplify things if they were to be transferred to here

[abachma2]

My first thought for this update was to copy over what is in Cycamore and then just update the library name. That ended up causing some issues because the src directory here has a sub-directory (toolkit) that has a subdirectory (pyroprocessing) and Cycamore does not have nay subdirectories in src. So some of the build doesn't get linked properly with the contents of the Cycamore CMakeLists and I'm not versed enough in CMake to more selectively pull from the Cycamore file.

[gonuke]

My first thought for this update was to copy over what is in Cycamore and then just update the library name. That ended up causing some issues because the src directory here has a sub-directory (toolkit) that has a subdirectory (pyroprocessing) and Cycamore does not have nay subdirectories in src. So some of the build doesn't get linked properly with the contents of the Cycamore CMakeLists and I'm not versed enough in CMake to more selectively pull from the Cycamore file.

Hmmm.... this is definitely not a conventional design.... some thought will be required.

[abachma2]

Besides some things in the repo structure being unconventional and worth re-visiting, is there anything that should be updated with this PR?

[gonuke]

Does it work? I know that there was substantial restructuring of CMake and its macros, so I'm not sure if that kind of restructuring makes sense here, just on the CMake side, never mind the code side.

[gonuke]

We might be better off, after all, starting in a clean repo for advanced archetypes, and then moving Pyre into that repo...???

[abachma2]

It builds on my machine (rocky 8.9). When I get around to updating the CI I can run on other machine types.

I'm not against moving this to a new repo, but the benefit of that is not clear to me.

[gonuke]

It builds on my machine (rocky 8.9). When I get around to updating the CI I can run on other machine types.

I'm not against moving this to a new repo, but the benefit of that is not clear to me.

Let's leave things here. It is probably worth taking a look at the current version of Cycamore's CMakeLists.txt file and making a few additional changes here. Most/all of them are simplifying changes that come from moving some standard things into macros that can now be imported by all archetype developers.

Alternatively, we could make that a separate issue and just go forward with this now that it builds.

[gonuke]

Alternatively, we could make that a separate issue and just go forward with this now that it builds

I made issue #26 to capture this.

[gonuke]

I wonder if we need to update CI first so we have tests that show this building. Or maybe they need to be part of the same PR?