http://ftp.digitalmars.com/dmd1beta.zip
http://ftp.digitalmars.com/dmd2beta.zip

Be the first kid on your block to build a dmd Win64 app!

Am 14.10.2012 21:54, schrieb Walter Bright:
> http://ftp.digitalmars.com/dmd1beta.zip
> http://ftp.digitalmars.com/dmd2beta.zip
>
> Be the first kid on your block to build a dmd Win64 app!

Nice, did any of the known issues get fixed or is the list still the same?

Kind Regards
Benjamin Thaut

Walter Bright:
> http://ftp.digitalmars.com/dmd2beta.zip
>
> Be the first kid on your block to build a dmd Win64 app!

The changelog section is not in good state, it misses parts and newlines.

Bye,
bearophile

On 10/14/12, Walter Bright <newshound2@digitalmars.com> wrote:
> Be the first kid on your block to build a dmd Win64 app!

But this is without Phobos support?

D:\DMD\dmd2\windows\bin\..\..\src\phobos\std\algorithm.d(317): Error: module string is in file 'std\c\string.d' which cannot be read

I can't test much if Phobos can't be used. :)

On 10/14/2012 3:27 PM, Andrej Mitrovic wrote:
> D:\DMD\dmd2\windows\bin\..\..\src\phobos\std\algorithm.d(317): Error:
> module string is in file 'std\c\string.d' which cannot be read

Fixed.

On 10/15/12, Walter Bright <newshound2@digitalmars.com> wrote:
> On 10/14/2012 3:27 PM, Andrej Mitrovic wrote:
>> D:\DMD\dmd2\windows\bin\..\..\src\phobos\std\algorithm.d(317): Error: module string is in file 'std\c\string.d' which cannot be read
>
> Fixed.
>

Ok so we're only supposed to compile with -c when using -m64? I don't suppose DMD could automatically invoke the VC linker?

On 10/14/2012 6:08 PM, Andrej Mitrovic wrote:
> Ok so we're only supposed to compile with -c when using -m64? I don't
> suppose DMD could automatically invoke the VC linker?
>

It does automatically invoke the VC linker.

You'll need to set the VCINSTALLDIR environment variable. I set it with sc.ini as:

---------------------
[Environment]
LIB=c:\cbx\mars\phobos;c:\cbx\mars\druntime\lib;c:\dm\lib\;c:\curl\lib
DDFLAGS=-Ic:\cbx\mars\phobos
DFLAGS=-Ic:\cbx\mars\phobos;c:\cbx\mars\druntime\import
#LINKCMD=c:\dm\bin\link.exe
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\
WindowsSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\
----------------------

On 10/15/2012 3:44 AM, Walter Bright wrote:
> On 10/14/2012 6:08 PM, Andrej Mitrovic wrote:
>  > Ok so we're only supposed to compile with -c when using -m64? I don't
>  > suppose DMD could automatically invoke the VC linker?
>  >
>
> It does automatically invoke the VC linker.
>
> You'll need to set the VCINSTALLDIR environment variable. I set it with
> sc.ini as:
>
> ---------------------
> [Environment]
> LIB=c:\cbx\mars\phobos;c:\cbx\mars\druntime\lib;c:\dm\lib\;c:\curl\lib
> DDFLAGS=-Ic:\cbx\mars\phobos
> DFLAGS=-Ic:\cbx\mars\phobos;c:\cbx\mars\druntime\import
> #LINKCMD=c:\dm\bin\link.exe
> VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\
> WindowsSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\
> ----------------------

I guess there should be different environments for each architecture specified in sc.ini. Especially the LIB variable will never mix because the windows sdk libraries are called the same on both architectures.

A problem with that is the DFLAGS variable: it is read before the command line, so you don't know whether -m32 or -m64 is passed (and it might even specify the switch itself), so you don't know which architecture to use.

A solution might be to have additional environment blocks [Environment32] and [Environment64] that are evaluated after the command line processing.

On Sunday, 14 October 2012 at 19:55:20 UTC, Walter Bright wrote:
> http://ftp.digitalmars.com/dmd1beta.zip
> http://ftp.digitalmars.com/dmd2beta.zip
>
> Be the first kid on your block to build a dmd Win64 app!

On Win 2008 R2:

1. Path for VS 11:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\x86_amd64

Simple can be renamed to ..\amd64

2. mspdb110.dll not found:

In cmd:

C:\dmd2\windows\bin>path=%path%;C:\Program Files (x86)\Microsoft Visual Studio 1
1.0\Common7\IDE

3.

C:\dmd2\windows\bin>dmd -m64 t64.d
Microsoft (R) Incremental Linker Version 11.00.50727.1
Copyright (C) Microsoft Corporation.  All rights reserved.

LINK : fatal error LNK1104: cannot open file 'phobos64.lib'
--- errorlevel 1104

If phobos.lib renamed to phobos64.lib

Microsoft (R) Incremental Linker Version 11.00.50727.1
Copyright (C) Microsoft Corporation.  All rights reserved.

.\..\lib\phobos64.lib : warning LNK4003: invalid library format; library ignored

t64.obj : error LNK2001: unresolved external symbol main ...

But in 32 mode with same sc.ini works fine.