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

The CMake project to check if a dependency exists can be affected by the cache of other profiles #5

Closed
gracicot opened this issue Apr 12, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@gracicot
Copy link
Owner

We currently use the same dummy project to find dependencies for all profile. An argument that affect the cache (such as compiler) will bleed on other profiles.

Furthermore, you can screw the cache using only one profile by setting an argument and then remove it.

We should have one dummy project by profile and clean it if the profile arguments has changed.

@gracicot gracicot added the bug Something isn't working label Apr 12, 2020
@gracicot
Copy link
Owner Author

Fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant