> I'm glad that everybody is happy with the new PCbuild9 directory. Tcl/Tk
> is the last obstacle. I'm not able to build the 64bit version with the
> cross compiler of VS 2008 Standard Edition.
I'll look into it. I'll probably try to build some beta of Tcl 8.5,
hoping that they manage to release T
Chris Mellon wrote:
> If anyone is curious, I ran pybench for both 2.6 and 3k build against
> VS 2003 and VS 2008. This is using the out of the box settings, and no
> PGO for 2008 (Express version doesn't have it). MSVC 9 was slightly
> faster for 2.6, but somewhat slower for py3k. I'm not sure how
On Nov 23, 2007 8:53 AM, Paul Moore <[EMAIL PROTECTED]> wrote:
> I have just built the current trunk version of Python on Windows,
> using the new PCBuild9 directory, and Visual Studio 2008 Express
> Edition.
>
> Everything went extremely well. I include below my notes on what I
> did, for referenc
On 2007-11-23 23:12, Paul Moore wrote:
> On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
>> bsddb is automatically build by a build step. But you have to convert
>> the project files in build_win32 to VS 2008 first. Simply open the
>> solution file and let VS convert the projects.
>
> V
> VS 2008 Express doesn't have a devenv command
Can you please try out whether the buildbot commands have
any chance to work with the Express edition?
Buildbot operators will have to install VS 2008 one way
or the other, and it would be nice if you could provide
instructions for them what precise
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> bsddb is automatically build by a build step. But you have to convert
> the project files in build_win32 to VS 2008 first. Simply open the
> solution file and let VS convert the projects.
VS 2008 Express doesn't have a devenv command, so
On 23/11/2007, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2007-11-23 18:40, Christian Heimes wrote:
> > M.-A. Lemburg wrote:
> >> Why not include the prebuilt libraries of all external libs in SVN
> >> as well ?
> >
> > For one I'm still using Beta 2 of the standard edition and I'm not
> > allow
Christian Heimes wrote:
> M.-A. Lemburg wrote:
>> Why not include the prebuilt libraries of all external libs in SVN
>> as well ?
>
> For one I'm still using Beta 2 of the standard edition and I'm not
> allowed to distribute binaries build with the Beta. With the new
> pre-build steps it's also ve
On 2007-11-23 18:40, Christian Heimes wrote:
> M.-A. Lemburg wrote:
>> Why not include the prebuilt libraries of all external libs in SVN
>> as well ?
>
> For one I'm still using Beta 2 of the standard edition and I'm not
> allowed to distribute binaries build with the Beta. With the new
> pre-bui
M.-A. Lemburg wrote:
> Why not include the prebuilt libraries of all external libs in SVN
> as well ?
For one I'm still using Beta 2 of the standard edition and I'm not
allowed to distribute binaries build with the Beta. With the new
pre-build steps it's also very easy to build the dependencies. I
On 2007-11-23 16:59, Christian Heimes wrote:
> Paul Moore wrote:
>> _ssl
>>
>>
>> Christian has been making changes to allow this to build without Perl,
>> so I gave it a try. I used openssl 0.9.8g, which I extracted to the
>> build directory (I noticed afterwards that this is the same version
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Why are you building the projects step by step? "Build solution" or F6
> builds everything in the right order.
Because I'm clueless :-)
I knew there must be a way of building the lot, but couldn't find it -
I haven't used Visual Studio
Paul Moore wrote:
> On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
>> I really like to throw out the old junk to have a clean script. Maybe I
>> could leave the old msvccompiler alone and put the new code into
>> distutils.msvc9compiler?
>
> That might work. I'm not sure if throwing th
Paul Moore wrote:
> Install Visual C++ 2008 Express Edition. Only select Silverlight from
> the options (no documentation or SQL Server - Silverlight probably
> isn't actually needed either).
> I already had the Platform SDK installed, but did nothing to tell VS
> about it, or to integrate it. I do
On 23/11/2007, Tim Golden <[EMAIL PROTECTED]> wrote:
> For practicality's sake I'd very much like to help get this
> to the point where you can build Python *and* extensions with
> the VS Express compilers (including, critically, the pywin32
> stuff).
Pywin32 needs MFC (and at one stage, ATL, alth
On 23/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> I've a preliminary patch for distutils.msvccompiler at
> http://bugs.python.org/issue1455. I haven't applied the patch because
> it's not backward compatible with VC 7 and VS 6. We haven't yet agreed
> how to address backward compatibilit
Tim Golden wrote:
> Ah. Thanks for that last bit. I thought this might not build
> without the full VS, so I didn't try poking round for a
> nasm-alike.
I've changed the build_ssl.py script to build openssl for nasm instead
of ml/masm. The MS assembler for x86 is only available in the standard
and
Paul Moore wrote:
> I have just built the current trunk version of Python on Windows,
> using the new PCBuild9 directory, and Visual Studio 2008 Express
> Edition.
>
> Everything went extremely well. I include below my notes on what I
> did, for reference. To be honest, there's nothing in here tha
I have just built the current trunk version of Python on Windows,
using the new PCBuild9 directory, and Visual Studio 2008 Express
Edition.
Everything went extremely well. I include below my notes on what I
did, for reference. To be honest, there's nothing in here that really
warrants a change to
19 matches
Mail list logo