Thanks, I think this double use is an aberration of cmake-gui.
If I delete everything , do a new git clone and run cmake alone or with the envvars you suggest I get a succesful cmake and make will progress.
However, I get this on console from which cmake was run. Fedora disables or restricts certain things if this is "critical" maybe it matters. Don't know what it's trying to do the system but Fed is stricter than most.
Code: Select all
#cmake-gui
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Error: could not load cache
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
** (cmake-gui:24905): CRITICAL **: 15:05:39.406: Failed to get connection to xfconfd: The connection is closed
(cmake-gui:24905): dconf-WARNING **: 15:05:39.659: failed to commit changes to dconf: The connection is closed
Having done make and make install of the downloaded files, I used cmake-gui to turn off CXX build and add PY stuff and run configure. I exited and ran make and make install:
Code: Select all
Install the project...
-- Install configuration: ""
-- Installing: /usr/lib64/python2.7/site-packages/ocl.so
-- Up-to-date: /usr/lib/python2.7/site-packages
-- Installing: /usr/lib/python2.7/site-packages/pyocl.py
-- Installing: /usr/lib/python2.7/site-packages/camvtk.py
-- Installing: /usr/lib/python2.7/site-packages/procmemory.py
-- Installing: /usr/lib/python2.7/site-packages/STLTools.py
It seems like that has produced the python bindings. Now to see whether FreeCAD can find them.
Yes, running the same file I used before I no longer get the "opencamlib not working". On the face of it that seems like a workaround.