On 22/06/2012 3:10 AM, KACVINSKY Tom wrote:
I found what I was looking for:
python setup.py bdist_wininst
bdist_wininst is for creating installers for Python packages which
install into an existing Python directory structure. It isn't used to
create a installer for Python itself (which unless I misunderstand,
seems what you are trying to do).
Apart from generating an "official" MSI like Python itself ships as,
IIUC, there is no other way to take a built tree and create an
installer. On the other hand though, a built tree will generally work
fine if transplanted somewhere else, so long as a couple of registry
entries are created. So you could do something like creating an inno
installer script that takes your built tree and generates a custom
installer for your build.
Mark
But... I follow all of the instructions for building Python on Windows and then
follow the instructions for using bdist_wininst, and I get this:
C:\Users\tky\Python\Python-2.6.8>PCbuild\amd64\python.exe setup.py bdist_wininst
running bdist_wininst
running build
running build_ext
INFO: Can't locate Tcl/Tk libs and/or headers
Traceback (most recent call last):
File "setup.py", line 2049, in <module>
main()
File "setup.py", line 2044, in main
'Lib/smtpd.py']
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\core.py", line 152, in
setup
dist.run_commands()
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\dist.py", line 975, in
run_commands
self.run_command(cmd)
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\dist.py", line 995, in
run_command
cmd_obj.run()
File
"C:\Users\tky\Python\Python-2.6.8\lib\distutils\command\bdist_wininst.py", line
125, in run
self.run_command('build')
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\cmd.py", line 333, in
run_command
self.distribution.run_command(command)
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\dist.py", line 995, in
run_command
cmd_obj.run()
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\command\build.py", line
134, in run
self.run_command(cmd_name)
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\cmd.py", line 333, in
run_command
self.distribution.run_command(command)
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\dist.py", line 995, in
run_command
cmd_obj.run()
File "C:\Users\tky\Python\Python-2.6.8\lib\distutils\command\build_ext.py",
line 340, in run
self.build_extensions()
File "setup.py", line 167, in build_extensions
raise ValueError("No source directory; cannot proceed.")
ValueError: No source directory; cannot proceed.
Does anyone know of a way to get bdist_wininst to work out of the box? I am
not comfortable with hacking distutils. What do the maintainers do in this
case?
Thanks,
Tom
-----Original Message-----
From: python-list-bounces+tky=3ds....@python.org
[mailto:python-list-bounces+tky=3ds....@python.org] On Behalf Of KACVINSKY Tom
Sent: Wednesday, June 20, 2012 4:29 PM
To: python-list@python.org
Subject: RE: Custom build of Python
Terry,
At this stage, I don't want or need an MSI. I just want something that will
bundle the executables/dynamic load libraries + compiled Python files and stick
them into a compliant directory structure.
Regards,
Tom
-----Original Message-----
From: python-list-bounces+tky=3ds....@python.org
[mailto:python-list-bounces+tky=3ds....@python.org] On Behalf Of Terry Reedy
Sent: Wednesday, June 20, 2012 4:13 PM
To: python-list@python.org
Subject: Re: Custom build of Python
On 6/20/2012 2:24 PM, KACVINSKY Tom wrote:
I had reason to build Python 2.6.8 with Microsoft Visual Studio 2010.
I was able to get the pcbuild solution to build, and I have the
necessary exes/dlls/pyds in the amd64 build directory. What is not
clear to is how to complete the build and make an installation. I
could not find any documentation for this.
If you mean 'make a .msi file', I am not sure that is not officially supported
beyond the inclusion of msilib.
Any help on this matter would be appreciated.
3.3 is now being built with VS2010. Perhaps its repository has something that
will help you.
--
Terry Jan Reedy
--
http://mail.python.org/mailman/listinfo/python-list
This email and any attachments are intended solely for the use of the
individual or entity to whom it is addressed and may be confidential and/or
privileged.
If you are not one of the named recipients or have received this email in error,
(i) you should not read, disclose, or copy it,
(ii) please notify sender of your receipt by reply email and delete this email
and all attachments,
(iii) Dassault Systemes does not accept or assume any liability or
responsibility for any use of or reliance on this email.
For other languages, go to http://www.3ds.com/terms/email-disclaimer
--
http://mail.python.org/mailman/listinfo/python-list
This email and any attachments are intended solely for the use of the
individual or entity to whom it is addressed and may be confidential and/or
privileged.
If you are not one of the named recipients or have received this email in error,
(i) you should not read, disclose, or copy it,
(ii) please notify sender of your receipt by reply email and delete this email
and all attachments,
(iii) Dassault Systemes does not accept or assume any liability or
responsibility for any use of or reliance on this email.
For other languages, go to http://www.3ds.com/terms/email-disclaimer
--
http://mail.python.org/mailman/listinfo/python-list