November 07, 2013
i did that, but it still will not work

On Thursday, 7 November 2013 at 10:12:29 UTC, evilrat wrote:
> On Thursday, 7 November 2013 at 08:58:50 UTC, tester wrote:
>> how do make that comiler work?
>> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>>
>> this is a desaster for me. was that release tested? if i amand the pathes and run as admin or not - it will not find the libs (user32)
>>
>> windoes8.1, visual studio2013, 64bit
>
> if it compiles with -m32 and fails with -m64 then i think you need manually edit ur sc.ini to add correct paths for windows sdk/kits and visual studio.

November 07, 2013
does not work with the installer either.


that really sucks


On Thursday, 7 November 2013 at 10:19:03 UTC, tester wrote:
> i did that, but it still will not work
>
> On Thursday, 7 November 2013 at 10:12:29 UTC, evilrat wrote:
>> On Thursday, 7 November 2013 at 08:58:50 UTC, tester wrote:
>>> how do make that comiler work?
>>> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>>>
>>> this is a desaster for me. was that release tested? if i amand the pathes and run as admin or not - it will not find the libs (user32)
>>>
>>> windoes8.1, visual studio2013, 64bit
>>
>> if it compiles with -m32 and fails with -m64 then i think you need manually edit ur sc.ini to add correct paths for windows sdk/kits and visual studio.

November 07, 2013
On Thursday, 7 November 2013 at 11:42:25 UTC, tester wrote:
> does not work with the installer either.
>
>
> that really sucks

well, this is because most people stick with linux, and i think there few to noone  win8 users. so here is the result ...
November 07, 2013
yes, that may be true and i understand that there are still compiler errors.
but the most primitive things that are advertised should work. something like this would get people fired in our company - and rightly so.


On Thursday, 7 November 2013 at 12:06:51 UTC, evilrat wrote:
> On Thursday, 7 November 2013 at 11:42:25 UTC, tester wrote:
>> does not work with the installer either.
>>
>>
>> that really sucks
>
> well, this is because most people stick with linux, and i think there few to noone  win8 users. so here is the result ...

November 07, 2013
El 06/11/13 11:47, Jordi Sayol ha escrit:
> El 06/11/13 10:55, Jordi Sayol ha escrit:
>> El 05/11/13 23:46, Walter Bright ha escrit:
>>> On 11/5/2013 2:41 PM, Brad Anderson wrote:
>>>> Figured it out.  You used linux/win/installer.nsi.  I have no idea why that exists and what it is for.
>>>
>>> It's so you can build the windows installer from a Linux box. I presumed it was the same.
>>>
>>
>> It is not the same. The linux/windows/dinstaller.nsi is a fork of windows/dinstaller.nsi. Mainly differs as it includes everything on itself, removing the need to download dmd/dmc/libcurl every time dmd is installed. There are some other minor changes.
>>
> 
> Errata: s:linux/windows/dinstaller.nsi:linux/win/installer.nsi:
> 
> BTW. Changes on this fork:
> 
> - Built in all the needed components. No downloads during installation.
> 
> - Checks if another dmd version is already installed, and force to uninstall it before proceed. If uninstaller fails, installation can be forced by the command "dmd-2.064.2.exe /f".
> 
> - Changes on the Windows system registry fields and values.
> 
> - Remove the dmd version 1.
> 
> - Not allowed to go ahead if nothing is selected.
> 
> - Changed default path to "C:\dmd". If previous dmd installation is set to another path, installer uses it instead the default.
> 
> 
> It is prepared to be built by the "linux/dmd_win.sh", which is included on "linux/build_all.sh" as well.
> 

Add to these changes:

- Check if a dmd installer instance is already running (only one at a time allowed).

- When uninstalling, keeps root dmd folder if some file/folder added by the user remains there, but not if in "dm" nor "dmd2" folders.

-- 
Jordi Sayol
November 07, 2013
Visual studio doesn't run on Linux, there are very many windows users 64bit
was first supported on Linux though. submit a patch for the installer, we
all have other jobs.
On 7 Nov 2013 14:10, "evilrat" <evilrat666@gmail.com> wrote:

> On Thursday, 7 November 2013 at 11:42:25 UTC, tester wrote:
>
>> does not work with the installer either.
>>
>>
>> that really sucks
>>
>
> well, this is because most people stick with linux, and i think there few to noone  win8 users. so here is the result ...
>


November 07, 2013
On 11/7/2013 12:58 AM, tester wrote:
> how do make that comiler work?
> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>
> this is a desaster for me. was that release tested? if i amand the pathes and
> run as admin or not - it will not find the libs (user32)
>
> windoes8.1, visual studio2013, 64bit
>

There's an attachment to https://d.puremagic.com/issues/show_bug.cgi?id=11457 with an sc.ini, does that one work for you?
November 07, 2013
On Thursday, 7 November 2013 at 08:58:50 UTC, tester wrote:
> how do make that comiler work?
> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>
> this is a desaster for me. was that release tested? if i amand the pathes and run as admin or not - it will not find the libs (user32)
>
> windoes8.1, visual studio2013, 64bit

This never worked automatically before so I don't know how this could suddenly be a disaster. In this release the installer makes an attempt to detect your VC++ and SDK installation and fix up sc.ini to point to them.  It's brand new and only a few people responded to my call for help testing it. Post your sc.ini and the paths to your Windows 8.1 SDK and Visual C++ 2013 installation.
November 07, 2013
On Thursday, 7 November 2013 at 16:25:47 UTC, Brad Anderson wrote:
> On Thursday, 7 November 2013 at 08:58:50 UTC, tester wrote:
>> how do make that comiler work?
>> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>>
>> this is a desaster for me. was that release tested? if i amand the pathes and run as admin or not - it will not find the libs (user32)
>>
>> windoes8.1, visual studio2013, 64bit
>
> This never worked automatically before so I don't know how this could suddenly be a disaster. In this release the installer makes an attempt to detect your VC++ and SDK installation and fix up sc.ini to point to them.  It's brand new and only a few people responded to my call for help testing it. Post your sc.ini and the paths to your Windows 8.1 SDK and Visual C++ 2013 installation.

I run 32bit win7 with VS2013 so I normally do not test cross-compiling with -m64.

The installer correctly found my installation directories:
VCINSTALLDIR=C:\Program Files\Microsoft Visual Studio 12.0\VC\
WindowsSdkDir=C:\Program Files\Windows Kits\8.1\

But I needed to add the follwing to PATH(in order to find mspdb120.dll)
%VCINSTALLDIR%\bin

And the following to LIB, in order to find shell32.lib
LIB=%LIB%;"%WindowsSdkDir%\Lib\winv6.3\um\x64"

Hope it helps.

November 07, 2013
yes i tried that.

i uninstalled d selveral times and reinstalled. itried it with the zip file.
nothing worked.. after a reboot i reinstalled with the installer and used the (bug) appended sc.ini. didn't work. i then replaced all occurences of %VCINSTALLDIR% and %WindowsSdkDir% with the actual path such as C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC and it wouldn't work. i worked with these modifications when i started as administrator.

this is frustrating, since i love to install a new release an do something with it out of the box. never the less i love d and i hope all of hard working guys are not to pis... with my postings, since you all do a great job.

thanks again.



On Thursday, 7 November 2013 at 16:19:39 UTC, Walter Bright wrote:
> On 11/7/2013 12:58 AM, tester wrote:
>> how do make that comiler work?
>> [Issue 11457] New: Cannot compile 64bit apps with Visual Studio 2013
>>
>> this is a desaster for me. was that release tested? if i amand the pathes and
>> run as admin or not - it will not find the libs (user32)
>>
>> windoes8.1, visual studio2013, 64bit
>>
>
> There's an attachment to https://d.puremagic.com/issues/show_bug.cgi?id=11457 with an sc.ini, does that one work for you?