Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divide CMake Projects into Their Own Repositories #294

Open
Atraxus opened this issue Jun 28, 2024 · 0 comments
Open

Divide CMake Projects into Their Own Repositories #294

Atraxus opened this issue Jun 28, 2024 · 0 comments
Labels
A-meta Area: development environment (toolchain, repo, etc.) C-discussion Category: This needs to discussed further C-enhancement Category: Adding a new feature

Comments

@Atraxus
Copy link
Collaborator

Atraxus commented Jun 28, 2024

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.

@Atraxus Atraxus added C-enhancement Category: Adding a new feature A-meta Area: development environment (toolchain, repo, etc.) C-discussion Category: This needs to discussed further labels Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: development environment (toolchain, repo, etc.) C-discussion Category: This needs to discussed further C-enhancement Category: Adding a new feature
Projects
None yet
Development

No branches or pull requests

1 participant