-
Hello, I am trying to make two GUIs which use the same packages and would like to use the multipackage option in order to reduce disk space in case I want to scale up the number of GUIs in the future. I am trying to get a simple example working, but am running into problems. The two GUIs are each a single Pyside2 label, at the moment, with GUI A saying 'Test A' and GUI B saying 'Test B'. I've pasted the code below with the commented lines being the only difference between the two. I am able to make individual spec files for each GUI and get them working with Pyinstaller. However, when I try and use multipackage with the spec file below, GUI_B opens and immediately closes with the error message it can't find python38.dll. GUI_A still works in the multipackage build. Hopefully this is just a error in my spec file, but I can provide additional info if the spec file looks correct. Thanks
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hmm, looking at the .spec files that are used by out multipackage tests:
I.e,
and
Also, due to another referencing bug, multipackage currently doesn't seem to work if you have nested resources (binary extensions or data files that reside in package directories; which definitely is the case with |
Beta Was this translation helpful? Give feedback.
Hmm, looking at the .spec files that are used by out multipackage tests:
MERGE()
seems to be the path to executable, relative to dist dirdependencies
TOC of the Analysis object that was modified during mergeI.e,
and
a.dependencies
should probably come up empty (because it ought to be the reference package), but it seems to end up wi…