2>c:\users\aio\miniconda3\envs\freecad_py3\library\include\vtk-8.1\vtkAtomic.h(28): fatal error C1083: Cannot open include file: 'tbb/atomic.h': No such file or directory
3>c:\users\aio\miniconda3\envs\freecad_py3\library\include\vtk-8.1\vtkAtomic.h(28): fatal error C1083: Cannot open include file: 'tbb/atomic.h': No such file or directory
3> TaskCreateNodeSet.cpp
3>c:\users\aio\miniconda3\envs\freecad_py3\library\include\vtk-8.1\vtkAtomic.h(28): fatal error C1083: Cannot open include file: 'tbb/atomic.h': No such file or directory
3> ViewProviderAnalysis.cpp
3>c:\users\aio\miniconda3\envs\freecad_py3\library\include\vtk-8.1\vtkAtomic.h(28): fatal error C1083: Cannot open include file: 'tbb/atomic.h': No such file or directory
FreeCAD_trunk - Microsoft Visual Studio-000071.png (15.04 KiB) Viewed 1918 times
I updated windows today without problems. Maybe you have not the freecad/label/dev in your channels. I can imagine that the latest build from last Sunday is compiled against latest tbb. So either add freecad/label/dev to the channels or try this:
"conda update --all -c freecad/label/dev"
But I am not sure if the latter works.
BTW. Didn't know about the reverting tools. Seems like a nice feature.
sgrogan wrote: ↑Fri Sep 21, 2018 9:09 pm
mkl may be a dependency of numpy and scipy, I'm not sure how the conda-forge packages are linked.
exactly. And openblas is an alternative to mkl. So specifying the feature openblas will pull in only packages which are compiled with openblas. I think openblas should also work on windows, but mkl is better tested.
so you are building freecad yourself? I assumed you are using a build from conda-forge.
In this case I don't know. I will report back if I encounter the same problem when I create new builds tomorrow. tbb was updated 2 days ago, so it is possible some incompatibility where introduced.
ok for linux and osx I get a tbb linking error. I guess it's because occt is still build with the older version of tbb, but the dependency-solver doesn't care about the tbb-version and pulls in the newer tbb-version. So to get a fast solution for this problem, I have created a PR for occt [1] to build with the latest tbb and pin the runtimedependency of occt to the tbb-version it was build with. In the long run we might add tbb to conda-forge-pinnings [2].
Btw.: I do not have the problem on windows because there I do not build occt with tbb enabled. Does anyone know what the advantages of tbb are?
vtk is one of the most painful dependencies. As it seems to depend on tbb it has to be updated too. But I remeber big troubles when I worked the last time on the vtk-feedstock... At least I think that the recipe won't work out of the box, if we only rerender and try to build.