[C++-sig] Delayed load of pythonXX.dll

[G Hansford]

> If you want to disable scripting support you probably want to delay-load
> not only the python runtime, but boost.python, too. Your problem stems
> from statically linking with boost.python, which depends on the python
> runtime library, forcing you to provide that at program startup.


That seems like the thing to do - I imagine what I will do is just move all
of my scripting code out to a separate DLL altogether. I was just hoping to
avoid having any external dependencies (minus python itself), but I suppose
this is a reasonable concession. Apparently there is a way to avoid this
problem if you're using SWIG, but at this point I would still rather use
boost.python.

Thanks for your help...