Windows install to custom location after building from source

2009-03-06 Thread dan . erik . petersen
Hi all -

I have succeeded in building Python 2.6.1 from source under Windows XP
by running Visual C++ 2008 Express on the PCbuild/pcbuild.sln file
both from the Visual C++ application as well as from the commandline
using :

vcbuild pcbuild.sln 'Release|Win32'

This builds fine (allowing for errors in the build of modules like
sql3 and the like where I have not fetched source code), and creates
its products "in-place" in the source directory.

My question/desire is :

I would like to move this Python installation in a clean manner over
to another location outside the unpackaged source directory (e.g. from
C:\Python-2.6.1 to C:\custom_path\python). Is there already some
automatic command that can perform this? If not, which files do I move
where and what should the structure be? How do ensure all the Python
code related to the install is byte-compiled and ready for use?

I have Googled as best as I can but no luck.

Thanks,

Dan
--
http://mail.python.org/mailman/listinfo/python-list


Re: Windows install to custom location after building from source

2009-03-06 Thread dan . erik . petersen
I suppose that what I am looking for is the Windows version of "make
install" as we know it after running configure with --
prefix=custom_location --exec-prefix=custom_location flags and make on
the Linux platform.

Dan
--
http://mail.python.org/mailman/listinfo/python-list


Re: Windows install to custom location after building from source

2009-03-06 Thread dan . erik . petersen
On Mar 6, 11:21 am, Christian Heimes  wrote:
> dan.erik.peter...@gmail.com schrieb:
>
> > I suppose that what I am looking for is the Windows version of "make
> > install" as we know it after running configure with --
> > prefix=custom_location --exec-prefix=custom_location flags and make on
> > the Linux platform.
>
> The Windows build system doesn't have anything related to "make
> install". You have to assemble a distribution yourself or you have to
> create a MSI package. See Tools/msi/
>
> Christian

Thanks guys -

Looks like I'll have to settle on building a distribution myself, as a
solution based on MSI isn't in the cards ... so far, so good.

Dan;
--
http://mail.python.org/mailman/listinfo/python-list