42 lines
1.7 KiB
Plaintext
42 lines
1.7 KiB
Plaintext
From: dan at control.com (Dan L. Pierson)
|
|
Date: Fri, 23 Apr 1999 14:47:25 GMT
|
|
Subject: Embedding Python - Win32 - Request for Info/Opinions
|
|
References: <371f32af.0@news.inet-systems.net>
|
|
Message-ID: <37218679.236666031@news.randori.com>
|
|
Content-Length: 1373
|
|
X-UID: 1562
|
|
|
|
"Frank McGeough" <frank.mcgeough at synchrologic.com> wrote:
|
|
|
|
> What do I need to install when I put this on a target machine? I start off
|
|
> with creating a Python directory. If I put my COM dll, atl.dll and the
|
|
> python15.dll in this directory I can get my wrapper to register...but do I
|
|
> need to set PythonPath? do I need to install common py files? Where would I
|
|
> put these? Do I just mirror (in a very small way) what the Python install
|
|
> does? What is commonly done by people who are using Python commercially?
|
|
|
|
What we do (thanks to Mark Hammond), is change PC/python_nt.rc to
|
|
create a new registry base for our python:
|
|
|
|
//#define MS_DLL_ID "1.5.1"
|
|
#define MS_DLL_ID "QuickStep"
|
|
|
|
Then we create path and module subkeys under that, all of which point
|
|
to our install directory. We then copy all of the (many) needed .pyc
|
|
files (and the .pyd, etc.) into the install directory. We don't ship
|
|
the .py files by default, but I do have another kit that adds them.
|
|
|
|
The advantage of this is that our app is independant of whatever
|
|
version of Python may also be installed on the machine. The
|
|
disadvantage is that we need our own compile of the main Python dll.
|
|
Actually, we could probably get by with just editing the official
|
|
dll's embedded resources, but that makes me queasy just thinking about
|
|
it...
|
|
|
|
Dan Pierson, Control Technology Corporation
|
|
dan at control.com
|
|
|
|
|
|
|
|
|