Divide CMake Projects into Their Own Repositories #294
Labels
A-meta
Area: development environment (toolchain, repo, etc.)
C-discussion
Category: This needs to discussed further
C-enhancement
Category: Adding a new feature
Currently, if a user wants to use the rayx-core library in their project, they have to include a lot of likely unnecessary code. Rayx, rayx-ui, and many scripts and other tools are not needed for someone interested solely in our core library.
Dividing this repository into multiple ones is not a trivial task and should be done with consideration of both users' and developers' workflows. There will be pros and cons accompanying these changes, which we need to assess to decide whether we accept and welcome them or keep our current repository structure intact.
This issue is to start a discussion for anyone interested.
The text was updated successfully, but these errors were encountered: