The libpack used for the Windows builds still contains OCC 7.0.0, and those dependencies aren't being updated automatically via any sort of dependency manager. So, the issue isn't in the code base.

This appears to the a self-compiled version of FC. The latest commit is very recent, equivalent to version 0.17.12594 (which was never provided on the download page). However, the OCC version is 7.0.0, which was superceded in the official development snapshots for Windows about 6 months ago. Gene I...

Looked at the linked duplicate issue, and confirmed that removing the inches " symbol from the tool name resolved the issue.

When I create a single job, save, and reload, the job hierarchy in the IDE looks like it's intact, but the one operation on the job still lacks any of the properties of an uncorrupted instance. Focusing on the tools, because of the output referencing issues with the a tool controller, I find that th...

Issue When I save a file containing Path elements, some Job hierarchies get flattened into single elements at the root, and neither those nor Job elements still in a tree structure are editable. Instead of editing the properties of the element, a double-click opens a translation edit. In usage term...

I need to qualify my last post.

When running CMake to configure a VS14 (2015) solution, the existing CMake files don't work. Generating a VS12 (2013) solution works just fine (at least with the 11.5.3 lib pack).

I installed VS2013, stashed any changes I made to CMake files, and started again. Zero problems, so far (90% through the build). So, either the CMake for VS14 has issues, or I screwed up something at the start. I'll test it out later, by trying to repro my earlier issues with VS14. Thank you for you...

For the versions of the Libpack I didn't have to do anything to the libpack.cmake file but only copy the files to the right place in the libpack. See the 11.5.3 version for example. I'm not sure what you mean by this. Are you copying files after installing the libpack or when you created it? Most o...

I'm using VS2015 (and the corresponding CMake profile) and the libpack you referenced. There is no uselibpack11x.cmake in the source tree, so I created one, essentially modifying the 10x version to account for differences in the naming conventions for some of the directories. I also had to add in bl...

I've hacked together a UseLibPack11x.cmake that configures a mostly buildable VS12 project. Mostly. The root CMakeList.txt is a bit of a soup sandwich in some ways. Still having issues. I've been chasing down the libraries for similar errors, but these persist: Error LNK2001 unresolved external symb...