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.

Sign up for GitHub

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

Jump to bottom

ALLEGRO_TARGETS shouldn't be cached #1512

Open
SiegeLord opened this issue Nov 22, 2023 · 2 comments
Open

ALLEGRO_TARGETS shouldn't be cached #1512

SiegeLord opened this issue Nov 22, 2023 · 2 comments

Comments

@SiegeLord
Copy link
Member

We cache ALLEGRO_TARGETS which makes it a pain to change the monolith vs not (and perhaps other changes too). It shouldn't be cached.
@ReiquelApplegate
Copy link
Contributor

What is the monolith?

@SiegeLord
Copy link
Member Author

This thing:

allegro5/CMakeLists.txt

Line 187 in c4bc6dc

option(WANT_MONOLITH "Include all addons in the main library" off)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SiegeLord @ReiquelApplegate