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

CMake feature detection #247

Open
rleigh-codelibre opened this issue Oct 16, 2018 · 3 comments
Open

CMake feature detection #247

rleigh-codelibre opened this issue Oct 16, 2018 · 3 comments

Comments

@rleigh-codelibre
Copy link

As mentioned in https://lists.boost.org/Archives/boost/2018/10/243729.php I would be happy to implement this type of functionality.

Would a PR implementing the detection logic be acceptable? Or is someone already working on this?

Thanks,
Roger

@jzmaddock
Copy link
Collaborator

I'm quite certain that I'm not qualified to comment - anyone else?

@eldiener
Copy link
Contributor

I am not qualified to judge a CMake implementation either. I did suggest that doing this for config ( and predef also ) and then having current Boost libraries which are converted to CMake use the CMake implementations in config and predef to replace the bjam code they already have now is a much better solution than having each library do their own CMake implementation for what they will need.

@rleigh-codelibre
Copy link
Author

I have done some initial work on this in the linked PR (#249). There will be more to come, this is just the initial step to make it installable and re-usable by downstream consumers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants