@bluescarni I saw that blog post. I think that's very exciting.
I wonder if they are experimenting with this to see if they can use this this by default for MSVC?
The author of cmake, Bill Hoffman, will be visiting LANL (where I work) tomorrow. Do we have any questions regarding cmake? We still didn't resolve #458, so I plan to ask him about it. If anybody has any other things you want me to ask, let me know.
Use case of relative paths would be conda. First you build symengine against conda's gmp. Another user will install both and try to build symengine.py. Then symengine.py will find symengine and through SymEngineConfig.cmake find gmp with a relative path.
So, in SymEngineConfig.cmake, it's useful to first look at the full path of the dependencies and then the relative path
@certik Not sure if they will ever switch to clang as default. From an outsider's perspective, it seems like it would make a ton of sense, as the current MSVC compiler is antiquate to the point that it's next to impossible to implement certain modern C++ features
but there might be other considerations at play, it's difficult to tell with Microsoft... maybe they need to be backwards-compatible with buggy MSVC behaviour, who knows