I just figured out the solution. I think PyInstaller was finding some of
the DLLs, but not all of them. They likely depended on each other using
relative paths, so they worked when I manually included all of them. When I
didn't, however, the ones that were included tried to find the others via a
Sorry, out of ideas. Maybe the PyInstaller dll loader is ignoring the
modifications to PATH, but then why is it working for me?
On Wed, Jun 12, 2019 at 7:27 AM Ben Green
wrote:
> Eric,
>
> I was setting the path in the main script right before I imported the SWIG
> module. At your suggestion, I
Eric,
I was setting the path in the main script right before I imported the SWIG
module. At your suggestion, I tried using a runtime_hook to point to a boot
file, and I set os.environ["PATH"] in the boot file. I still have the same
issue.
On Sunday, June 9, 2019 at 9:21:15 AM UTC-4, Eric Fahlg
Eric,
I had tested setting the path at the beginning of the main script, but that
was unfruitful. I had not thoroughly looked into runtime_hooks, because it
didn't seem to be any different than what I was already attempting. Given
your suggestion, though, I gave it a shot. I set up a runtime ho
Ben, I think we're doing exactly that in our code. Exactly when are you
setting PATH? Do you use the runtime_hooks in your .spec file to point to
a boot file, so it happens as part of initialization of the product exe?
XXX.spec contains (among all the other stuff):
analyzed = Analysis(
scrip
The problem:
I have a small program that imports a SWIG module, which imports some DLLs.
I need to create an executable for this program that can reference these
external DLLs as external DLLs, not by bundling them in the executable.
>From what I've read, this doesn't seem to be possible. I've t
