OK compilation is still ongoing but I'm getting your expected failures EDIT: abdullah, do you think we should start a new thread? and maybe ask a mod to move our conversation there? I think we have determined it's not a PPA packaging issue but a FreeCAD issue. This is with the "add_definitions...

I will call it a day. The problem originates in that: OriginGroupExtension::OriginGroupExtension () { initExtensionType(OriginGroupExtension::getExtensionClassTypeId()); EXTENSION_ADD_PROPERTY_TYPE ( Origin, (0), 0, App::Prop_Hidden, "Origin linked to the group" ); } initializes the Origin...

it should not work (I would be surprised if it does), you have to add a definition (a preprocesor macro that will be passed to c++). The one above should only be a cmake environment variable. I thought that is what CMake did? See Here: https://forum.freecadweb.org/viewtopic.php?f=10&t=16952&...

I am trying to support sgrogan to get there And Thanks for that :D I'm compiling master now, I added HAVE_TBB manually in the CMake gui. How can I check for sure that FreeCAD is using this? Welcome!!!!! ;) If you added a: set(HAVE_TBB ON) it should not work (I would be surprised if it does), you ha...

abdullah wrote: NormandC wrote: That's great news. Now it would be great to see the annoying "Can't find Origin for Body/Part" error in report view when opening an existing file eradicated from existence. :twisted: I am looking at it now. I did not manage to find an associated bug report....

NormandC wrote:That's great news.

Now it would be great to see the annoying "Can't find Origin for Body/Part" error in report view when opening an existing file eradicated from existence.

I am looking at it now. I did not manage to find an associated bug report. Is there none?

Can we have 2 column output? https://gist.github.com/luzpaz/a8bb373b ... 071eaf6181 Yes we can. At least I have nothing against it. I would need to see if there is a way to do it nicely with STL, as I do not want to be coding tab separate strings to produce columns (and I do not know of another way...

Agreed, we can not invent it. It should be reported as unknown (look at About FreeCAD info for build type). This is slightly another thing but related. If TBB is enabled in FC (so if there is a MACRO defining that FreeCAD shall be built with TBB support, for example for the OCAF, for example for th...

abdullah wrote: I think that we cannot invent information we do not have. If we fall back to path finding, then probably the HAVE_TBB macro should not be set and (TBB) should not appear (regardless of how it was compiled). I mean, if cmake does not find what OCC should have put in its path when ins...

For 1. we probably need to consider what happens if the information can't be found and FreeCAD falls back to finding paths to specific files. I think that we cannot invent information we do not have. If we fall back to path finding, then probably the HAVE_TBB macro should not be set and (TBB) shoul...