My name is Oren, I'm from the Knossos development team at MPI Medical Research, Heidelberg, Germany.
Our application uses PythonQt and we would like to figure out what is the best way to deploy.
We use more than the minimal set that PythonQt offers without QtAll, so we definitely would like to have QtAll or at least a sufficient subset.
Given that we strongly prefer building our application statically, I'm contemplating between building QtAll for dynamic use as a DLL - Suboptimal (if at all possible), mixing static app' (including PythonQt bindings) with dynamic library - and building QtAll statically, which is something we could not easily figure out how to do (there seem to be a problem with WebKit).
It would be nice if Florian or someone else can comment on approaches taken in the past in similar scenarios.
Regards,
Oren Shatz
Last edit: Oren 2015-03-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry to say so, but I have always worked with Dlls. I think this is a binary decision, once you build PythonQt statically, you can't load a Dll that links PythonQt, neither statically nor dynamically.
In the long run, I am sure you will switch to Dlls, with a static application it is really difficult to have plugins, but your application looks like it will have load able plugins in the future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I assume you also build your Qt application dynamically, right?
If so, do you have an efficient way to deploy, given the changing nature of Qt library dependencies, without manually gathering them one by one?
(Sorry for moving out of strict PythonQt scope)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, we used Qt dynamically from the start and we deploy on Windows, Linux and MacOS. It is indeed a lot of work to get all this working for all platforms, especially because you need different deployment tools for each platform.
But Qt is our smallest concern, compared to all the other third party libs we need to keep going. On Windows, DependencyWalker really help and we use similar tools on Mac and Linux to handle correct deployment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
My name is Oren, I'm from the Knossos development team at MPI Medical Research, Heidelberg, Germany.
Our application uses PythonQt and we would like to figure out what is the best way to deploy.
We use more than the minimal set that PythonQt offers without QtAll, so we definitely would like to have QtAll or at least a sufficient subset.
Given that we strongly prefer building our application statically, I'm contemplating between building QtAll for dynamic use as a DLL - Suboptimal (if at all possible), mixing static app' (including PythonQt bindings) with dynamic library - and building QtAll statically, which is something we could not easily figure out how to do (there seem to be a problem with WebKit).
It would be nice if Florian or someone else can comment on approaches taken in the past in similar scenarios.
Regards,
Oren Shatz
Last edit: Oren 2015-03-17
Sorry to say so, but I have always worked with Dlls. I think this is a binary decision, once you build PythonQt statically, you can't load a Dll that links PythonQt, neither statically nor dynamically.
In the long run, I am sure you will switch to Dlls, with a static application it is really difficult to have plugins, but your application looks like it will have load able plugins in the future.
Thank you Florian.
I assume you also build your Qt application dynamically, right?
If so, do you have an efficient way to deploy, given the changing nature of Qt library dependencies, without manually gathering them one by one?
(Sorry for moving out of strict PythonQt scope)
Well, we used Qt dynamically from the start and we deploy on Windows, Linux and MacOS. It is indeed a lot of work to get all this working for all platforms, especially because you need different deployment tools for each platform.
But Qt is our smallest concern, compared to all the other third party libs we need to keep going. On Windows, DependencyWalker really help and we use similar tools on Mac and Linux to handle correct deployment.