DREAM3D: Recent Updates that will break the dockerfile

imikejackson commented 6 years ago

The filters in FiberToolbox were move to another plugin so the FiberToolbox plugin is deprecated and not used anymore.
Their are 2 libraries for each plugin now, a .plugin file which do not have a dependency on QtWidgets or QtGui and the .guiplugin which does have a dependency on those Qt5 components. If you are just running PipelineRunner you should be able to configure a Docker image without the QtWidgets and QtGui dependencies.
DREAM3D now uses the cmake infrastructure that TBB started including in their latest releases which means that the TBB that is installed through apt-get will not work. At least without alternate cmake codes added back into DREAM.3D

psavery commented 6 years ago

Okay. Thanks for the update Mike! I’m at a conference now, but will look into this soon... probably next week.

psavery commented 6 years ago

Hi Mike @imikejackson,

I took a look at this today. I made some changes to the docker file here: PR #2.

Strangely enough, it seems that TBB was still found just fine. So I left it the way it is.

The Dream3D build was successful. However, I got an error when I tried to run PipelineRunner. The error is pasted below:

Plugin Being Loaded: "/usr/local/dream3d/Bin/Plugins/libOrientationAnalysis.plugin"
Pointer:  QObject(0x0) 

The plugin did not load with the following error
Cannot load library /usr/local/dream3d/Bin/Plugins/libOrientationAnalysis.plugin: (libQt5Gui.so.5: cannot open shared object file: No such file or directory)

Possible causes include missing libraries that plugin depends on."

This caused the PipelineRunner to fail.

I removed the QtGui runtime install since the .plugin file shouldn't depend on it. But it looks like it still needs to link to it at runtime? This could be a problem on my end. But let me know what you think.

Thanks, Patrick

psavery / afrl-dockerfiles

DREAM3D: Recent Updates that will break the dockerfile #1