Next update:
I've done some more work on the PCbuild9 directory. I've removed the
ReleaseAMD64 solution and replaced it with platform x64. I've also taken
some effort to get the 64bit builds of the dependencies ready and
integrate them in the build process.
The openssl package required some hard
Joe Smith wrote:
> Ok. Your nasm workaround is fine, but ML.exe is definately intended to ship
> with VS 2008.
>
> For the record:
> The ml.exe is apparently included in the team edition of the beta, if you
> wanted it, but microsoft has messed up here. Alternatively, one could
> extract versio
"Christian Heimes" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Joe Smith wrote:
>> While ml.exe is intentionally omitted for the express version of Visual
>> C++,
>> the standard versions of Visual Studio are supposed to include ml.exe.
>> The VS 2008 beta 2 version omitted it
Update
--
The new PCbuild9 directory works for x86. I'm unable to test it for
AMD64. The structure is going to change from a ReleaseAMD64 solution
towards x86 platform in the future.
I've also hacked together a small fix for the msvccompiler module. It's
available at http://bugs.python.org/is
> Oh, it's an interesting speed up trick. How was the address table
> generated. Lucky guessing and gut feeling? :]
There is also rebase.exe (resp. editbin /rebase), which may have been
used to produce the initial version of this table.
Regards,
Martin
>> In the future, I think we should have only Release and Debug
>> configurations, and x86 and x64 platforms, and these in all four
>> combinations.
>
> I've tested VS 2008 Beta 2 Express and Standard Edition. I had to
> uninstall the Express Edition in order to test the Standard Edition. As
> far
Joe Smith wrote:
> While ml.exe is intentionally omitted for the express version of Visual C++,
> the standard versions of Visual Studio are supposed to include ml.exe.
> The VS 2008 beta 2 version omitted it by mistake. At the moment there is no
> convenient way to get the latest version. This s
Martin v. Löwis wrote:
> The "platform" feature didn't exist in VS 2003 (atleast you couldn't
> define new platforms), hence those projects made new configurations.
>
> In the future, I think we should have only Release and Debug
> configurations, and x86 and x64 platforms, and these in all four
>
> What combinations of configuration and platform do we need? The migrated
> solution has Release, Debug, ReleaseAMD64 and ReleaseItanium as
> configurations and Win32 as platform. The platform X64 isn't listed but
> I could add it.
>
> Do we need a ReleaseAMD64 when we could use the platform X64?
"Christian Heimes" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Today an user named weck has submitted three patches for VS 2005 support
> [0]. In one of the replies Martin said that he likes to use the upcoming
> VS2008 as new default compiler.
>
> I've downloaded the Beta 2 of
Martin v. Löwis wrote:
> If you have time and energy, you can try to eliminate duplicate and
> unnecessary settings, using VS defaults wherever possible. For
> optimization, it's probably still useful to copy over some of the
> PCbuild8 settings (although I'm not sure what the precise constraints
>
> I'll see if I can take some spare time and port the PCbuild directory to
> VS 2008. Do you have any additional suggestions or wishes?
If you have time and energy, you can try to eliminate duplicate and
unnecessary settings, using VS defaults wherever possible. For
optimization, it's probably sti
Martin v. Löwis wrote:
> Please no. I would much prefer if PCbuild9 was based on PCbuild, not
> PCbuild8. In particular, there shouldn't be subdirectories for the
> individual projects, and the output files should land directly in
> PCbuild9.
K!
I'll see if I can take some spare time and port the
> Should I check in my PCbuild9 directory? It's based on PCbuild8.
Please no. I would much prefer if PCbuild9 was based on PCbuild, not
PCbuild8. In particular, there shouldn't be subdirectories for the
individual projects, and the output files should land directly in
PCbuild9.
Regards,
Martin
__
Today an user named weck has submitted three patches for VS 2005 support
[0]. In one of the replies Martin said that he likes to use the upcoming
VS2008 as new default compiler.
I've downloaded the Beta 2 of VS 2008 from [1] and played with it a bit.
It comes with most tools required to build Pyt
15 matches
Mail list logo
