-
Notifications
You must be signed in to change notification settings - Fork 264
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
Build failure with cmake option using TBB in VS2017, windows 10 #287
Comments
Thanks for reporting this issue! Looks like there are some compiler warnings that are treated as an error. Can you also share the output from the “output” tab from your VS? |
Sorry for that i forgot. The output line is almost a thousand line so i upload it as a file |
Thanks for the log. I think the problematic code from the latest TBB is this:
While I investigate further, you can ignore C4180 by adding |
Thank you sir it worked well now. |
No problem. In fact, this is still a build issue with latest TBB so let me reopen this issue again. Will close it once /wd4180 as well as CI scripts are updated. |
I just added single line in the cmake file following your guide. Like below.
So the builds (Debug,x64), (Release,x64) had no problem |
From the code perspective, I think it is fine with the one-liner. I need to add proper TBB check in the CI to prevent this from happening again. |
As we are revisiting CI's in general, bumping up this issue again. |
Build failure occured in VS2017 while following install.md.
Creating solution with CMAKE option 'cmake .. -G"Visual Studio 15 2017 Win64" -DJET_TASKING_SYSTEM=OpenMP' and building solution in VS2017 was successful.
And I tried to build solution after run cmake with the option -DJET_TASKING_SYSTEM=TBB. But it wasn't successed.
Information::
Windows 10 (ver 1809)
tbb version: 2020.0.166 (latest)
tbb path: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2020.0.166\windows\tbb
CMAKE:
Build failure in VS2017
I spent several hours to solve this but I still can't figure out why this was happened and which caused this error so i made this issue.
Problem summary:
The text was updated successfully, but these errors were encountered: