-
Notifications
You must be signed in to change notification settings - Fork 86
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
Fixes compilation with Ninja and IntelLLVM when using OneAPI #544
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #544 +/- ##
=======================================
Coverage 89.48% 89.48%
=======================================
Files 7 7
Lines 5356 5356
=======================================
Hits 4793 4793
Misses 563 563 |
It looks like the CI failed? (haven't looked into why) |
What is the reason for both (note: the CI is failing because the tests aren't being enabled) |
It looks like |
Yes. I added an option because at some point I was using it as a submodule which was imported with add_subdirectory from a parent cmake. It was a little bit confusing to me that the names in the variables defined by options do not include the name of the project they refer to. Besides that, thank you a lot for this library. We are using it extensively in our FDTD solver project: https://github.com/OpenSEMBA/fdtd |
I think these changes have broken the conda-forge package. The shared library doesn't seem to be being built anymore. Did that get disabled? We should be getting:
Now we are only getting:
|
See #558 |
Yes, maybe I disabled that while doing some tests. Maybe is better to revert the merge. Sorry about that. |
I think 1784d4e fixes it. |
I have found some issues trying to compile with the recent Intel One API + Visual Studio 2022. Basically I got this error.
I have implemented some changes in CMakeLists.txt to fix it by considering the case of IntelLLVM which is the compiler Id of the new compiler.
Best regards,
Luis