align rayx-core with expectations to a shared library #422
Description
this issue is about using rayx-core as a library
this should align with common sense expectations when using a library
- probably split sources and includes into separate folders
- consider IDE workflow (people may like to have .h and .cpp files next to each other)
- probably put things considered not-part-of-the-api into an extra namespace
detail(or find some other methods, c++ modules would work) - go over all of rayx-core and take decisions on where to put RAYX_API and where not. currently this is kinda arbitrary
NOTE: the project is not really a shared library. it is a combination of shared library and two binaries (rayx, rayx-ui)
NOTE: review other bigger projects, to get inspiration