WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
-
- Posts: 27
- Joined: Sat Dec 01, 2018 12:30 pm
WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Hi all,
after I succeeded to build an 0.17 version under WIN10 with CMake-Gui and
MV2013 I tried to do the same with the 0.18 pre.
CMake CONFIGURE throws me a OpenCASCADE notfound error during configuration
and thus invalid project files as follows:
CMake Error at CMakeLists.txt:632 (MESSAGE):
================================================================
Neither OpenCASCADE Community Edition nor OpenCASCADE was found!
================================================================
No idea where to start looking for, so any hint appreciated.
Thanls a lot - Have a good time out there - Volker
after I succeeded to build an 0.17 version under WIN10 with CMake-Gui and
MV2013 I tried to do the same with the 0.18 pre.
CMake CONFIGURE throws me a OpenCASCADE notfound error during configuration
and thus invalid project files as follows:
CMake Error at CMakeLists.txt:632 (MESSAGE):
================================================================
Neither OpenCASCADE Community Edition nor OpenCASCADE was found!
================================================================
No idea where to start looking for, so any hint appreciated.
Thanls a lot - Have a good time out there - Volker
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
In the cmake build options you should find the key OCCT_CMAKE_FALLBACK. Toggle this check box and rerun configure.
-
- Posts: 27
- Joined: Sat Dec 01, 2018 12:30 pm
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Hi @wmayer,
Hi all,
sorry, cannot find key OCCT_CMAKE_FALLBACK in the
cmake build options.
Only have the following OCC related keys with the mentioned values:
OCC_INCLUDE_DIR OCC_INCLUDE_DIR-NOTFOUND
OCC_LIBRARY Z:/_00_FREECAD_OWN-COMP/_01_LIBS/0.18/FreeCADLibs_11.11_x64_VC12/lib/TKernel.lib
OCE_DIR OCE_DIR-NOTFOUND
I start from my release source dir Z:\_00_FREECAD_OWN-COMP\_01_SRC\FreeCAD-0.18_pre
my libpack dir is Z:\_00_FREECAD_OWN-COMP\_01_LIBS\0.18\FreeCADLibs_11.11_x64_VC12
and my build dir is Z:\_00_FREECAD_OWN-COMP\_01_BUILD\0.18_pre
Including the vorrect libpack path into the CMake configuring works, but the
"Neither OpenCASCADE Community Edition nor OpenCASCADE was found!" error stays.
Do I start with the correct src dir?
Any hint warmly appreceated.
Thanks a lot - Have a good time out there - Volker
Hi all,
sorry, cannot find key OCCT_CMAKE_FALLBACK in the
cmake build options.
Only have the following OCC related keys with the mentioned values:
OCC_INCLUDE_DIR OCC_INCLUDE_DIR-NOTFOUND
OCC_LIBRARY Z:/_00_FREECAD_OWN-COMP/_01_LIBS/0.18/FreeCADLibs_11.11_x64_VC12/lib/TKernel.lib
OCE_DIR OCE_DIR-NOTFOUND
I start from my release source dir Z:\_00_FREECAD_OWN-COMP\_01_SRC\FreeCAD-0.18_pre
my libpack dir is Z:\_00_FREECAD_OWN-COMP\_01_LIBS\0.18\FreeCADLibs_11.11_x64_VC12
and my build dir is Z:\_00_FREECAD_OWN-COMP\_01_BUILD\0.18_pre
Including the vorrect libpack path into the CMake configuring works, but the
"Neither OpenCASCADE Community Edition nor OpenCASCADE was found!" error stays.
Do I start with the correct src dir?
Any hint warmly appreceated.
Thanks a lot - Have a good time out there - Volker
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
If you have the entries grouped, it is in the ungrouped section.vcfbauplusfe wrote: ↑Wed Dec 05, 2018 8:45 pm sorry, cannot find key OCCT_CMAKE_FALLBACK in the
cmake build options.
You might also need to set the OCC_INCLUDE_DIR which would be <PathToLibpack>/include/opencascade
"fight the good fight"
-
- Posts: 27
- Joined: Sat Dec 01, 2018 12:30 pm
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Hi @sgrogan,
Hi all,
thanks @sgrogan - the hint with the OCC_INCLUDE_DIR was the knot to be sworded.
Configure and Generate now runs fine.
BTW:
What about all the othet XYZ_DIR-NOTFOUND (e.g. OCE, NGLIB, MEDFILE etc.)?
Will they cause troubles later on somewhere?
Thanks a lot.
Have a good time - Volker
Hi all,
thanks @sgrogan - the hint with the OCC_INCLUDE_DIR was the knot to be sworded.
Configure and Generate now runs fine.
BTW:
What about all the othet XYZ_DIR-NOTFOUND (e.g. OCE, NGLIB, MEDFILE etc.)?
Will they cause troubles later on somewhere?
Thanks a lot.
Have a good time - Volker
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
It shouldn't. Usually FreeCAD's CMake will look for these, that point to a XYZcongig.cmake file. Depending on the version of the package this may or may not work to set all the other XYZ variables. If it is doesn't work FreeCAD tries to find them another way, sometimes the user must supply them.vcfbauplusfe wrote: ↑Wed Dec 05, 2018 10:12 pm What about all the othet XYZ_DIR-NOTFOUND (e.g. OCE, NGLIB, MEDFILE etc.)?
Will they cause troubles later on somewhere?
If your build succeeds you might want to save a copy of CMakeCache.txt (from the build directory) for future reference.
Did you have any other problems? Other than the link to the most recent libpack, I owe the wiki some love before the next release (I've said that before )
"fight the good fight"
-
- Posts: 27
- Joined: Sat Dec 01, 2018 12:30 pm
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Hi @sgrogan,
Hi all,
haven't started VS2013 compilation yet but will do so tomorrow.
If the 0.18_pre will compile without errors I would send you a list of suggestions for
"Newbie-clarifying formulations"
Sorry that I complained about the libpack link, but I lost the approriate posting
that I had seen before but couldn't find it later when I did need it.
Have a good time all - Volker
Hi all,
haven't started VS2013 compilation yet but will do so tomorrow.
If the 0.18_pre will compile without errors I would send you a list of suggestions for
"Newbie-clarifying formulations"
Sorry that I complained about the libpack link, but I lost the approriate posting
that I had seen before but couldn't find it later when I did need it.
Have a good time all - Volker
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
No sorrys necessary, it's very valid constructive criticism. That's how we get better.vcfbauplusfe wrote: ↑Wed Dec 05, 2018 10:38 pm Sorry that I complained about the libpack link, but I lost the approriate posting
that I had seen before but couldn't find it later when I did need it.
"fight the good fight"
-
- Posts: 27
- Joined: Sat Dec 01, 2018 12:30 pm
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Hi all,
as promised the report about 0.18_pre VS2013 compilations:
DEBUG X64 ran fine with the typical "4 skipped" as 0.17 RELEASE X64 did.
RELEASE X64 threw 7 errors and also the "4 skipped".
The ERRORS as follows:
1. LINK : fatal error LNK1181: cannot open input file '..\..\..\lib\Release\MEFISTO2.lib'
2. LINK : fatal error LNK1181: cannot open input file '..\..\..\lib\Release\StdMeshers.lib'
3. LINK : fatal error LNK1181: cannot open input file '..\..\..\..\lib\Release\NETGENPlugin.lib'
4. LINK : fatal error LNK1181: cannot open input file '..\..\..\..\lib\Release\NETGENPlugin.lib'
5. LINK : fatal error LNK1181: cannot open input file '..\App\Release\MeshPart.lib'
6. LINK : fatal error LNK1181: cannot open input file '..\App\Release\Fem.lib'
7. error MSB4175: The task factory "CodeTaskFactory" could not be loaded from the assembly
The SKIPPED ones as follows:
35> Skipped Build: Project: dist-git, Configuration: Release x64 ------
35>Project not selected to build for this solution configuration
36>------ Skipped Build: Project: distdfsg-git, Configuration: Release x64 ------
36>Project not selected to build for this solution configuration
37>------ Skipped Build: Project: DevDoc, Configuration: Release x64 ------
37>Project not selected to build for this solution configuration
97>------ Skipped Build: Project: INSTALL, Configuration: Release x64 ------
97>Project not selected to build for this solution configuration
Maybe the errors seem to be a problem with the libpack
FreeCADLibs_11.11_x64_VC12
I used?
Hope these lines helps us a bit further to the 0.18 release.
Have a good time all out there - Volker
as promised the report about 0.18_pre VS2013 compilations:
DEBUG X64 ran fine with the typical "4 skipped" as 0.17 RELEASE X64 did.
RELEASE X64 threw 7 errors and also the "4 skipped".
The ERRORS as follows:
1. LINK : fatal error LNK1181: cannot open input file '..\..\..\lib\Release\MEFISTO2.lib'
2. LINK : fatal error LNK1181: cannot open input file '..\..\..\lib\Release\StdMeshers.lib'
3. LINK : fatal error LNK1181: cannot open input file '..\..\..\..\lib\Release\NETGENPlugin.lib'
4. LINK : fatal error LNK1181: cannot open input file '..\..\..\..\lib\Release\NETGENPlugin.lib'
5. LINK : fatal error LNK1181: cannot open input file '..\App\Release\MeshPart.lib'
6. LINK : fatal error LNK1181: cannot open input file '..\App\Release\Fem.lib'
7. error MSB4175: The task factory "CodeTaskFactory" could not be loaded from the assembly
The SKIPPED ones as follows:
35> Skipped Build: Project: dist-git, Configuration: Release x64 ------
35>Project not selected to build for this solution configuration
36>------ Skipped Build: Project: distdfsg-git, Configuration: Release x64 ------
36>Project not selected to build for this solution configuration
37>------ Skipped Build: Project: DevDoc, Configuration: Release x64 ------
37>Project not selected to build for this solution configuration
97>------ Skipped Build: Project: INSTALL, Configuration: Release x64 ------
97>Project not selected to build for this solution configuration
Maybe the errors seem to be a problem with the libpack
FreeCADLibs_11.11_x64_VC12
I used?
Hope these lines helps us a bit further to the 0.18 release.
Have a good time all out there - Volker
Re: WIN 10 0.18 CMAKE configure error - OpenCASCADE not foud
Strange, I would expect errors for the Debug builds due to the Libpack, but Release should work (I use this Libpack for the Win daily builds)vcfbauplusfe wrote: ↑Thu Dec 06, 2018 2:59 pm Maybe the errors seem to be a problem with the libpack
FreeCADLibs_11.11_x64_VC12
I used?
Maybe for the release build you could delete the cache in CMake-Gui, then re-run config and generate now that you have the necessary switches, then build clean and build all?
"fight the good fight"