Should systems be a separate CMake target?

[mpusz]

While cleaning up the library file tree I came to the point where I consider separating CMake targets for the library framework and predefined systems. Possibly we should even provide a target per each (sub-)system?

[JohelEGP]

You'd still be able to include all other headers regardless of target. If you wanted header isolation, you'd have to move all of the core components under core/, which would reside at the top level along with systems/si/. To maintain the current <units/ prefix when including the headers, you'd have to move everything under core/units and systems/si/units. Then, rather than having the targets' include directory be include/, they should be include/core/ and include/systems/si.

[mpusz]

BTW, Starting from CMake 3.19 it is possible to specify header files for INTERFACE libraries.

[JohelEGP]

This sounds like a good idea, regardless.

[mpusz]

I just realized that this broke Compiler Explorer :-( Now, we have header files spread across the entire repository so we cannot easily specify a single include path. CMake build and install in CE will also fail as the dependencies will not be met. CE does not support Conan as of now.
Any ideas?

[mpusz]

compiler-explorer/compiler-explorer#2544

[JohelEGP]

Everything in this comment has been addressed. And no answers to the discussion itself that systems shouldn't be a separate CMake target. And I don't expect any such thing to happen.