Any ideas? Happens when I do a very simple dub project and try to
compile using the MS linker(x86 but set in sc.ini or 64). I'm
linking in glfw(using correct arch of course)
{
"name": "Test",
"description": "A minimal D application.",
"copyright": "Copyright © 2016, Jas
ld using dmd for x86.
midimonitor ~master: building configuration "application"...
Linking...
Microsoft (R) Incremental Linker Version 14.00.23506.0
Copyright (C) Microsoft Corporation. All rights reserved.
LINK : fatal error LNK1104: cannot open file '_CMDLINE'
--- errorlevel 1104
dmd failed with exit code 1104.
Sheesh, why is it so hard to do simple stuff?
On Monday, 11 January 2016 at 20:19:50 UTC, Jason Jeffory wrote:
Sheesh, why is it so hard to do simple stuff?
1) Have you tryed passing --arch=x86_64 to dub?
2) > "versions-x86_64": ["XYZ"]
This is like a architecture dependent condition for version
definition.
So if your project will b
**
Performing "debug" build using dmd for x86.
midimonitor ~master: building configuration "application"...
Linking...
Microsoft (R) Incremental Linker Version 14.00.23506.0
Copyright (C) Microsoft Corporation. All rights reserved.
LINK : fa
quot;UseAmd64Impl"],
doesn't actually make it 64
**
Performing "debug" build using dmd for x86.
midimonitor ~master: building configuration "application"...
Linking...
Microsoft (R) Incremental Linker Version 14.00.23506.0
Copyrig
On Monday, 11 January 2016 at 23:26:51 UTC, Tobi G. wrote:
On Monday, 11 January 2016 at 20:19:50 UTC, Jason Jeffory wrote:
Sheesh, why is it so hard to do simple stuff?
1) Have you tryed passing --arch=x86_64 to dub?
2) > "versions-x86_64": ["XYZ"]
This is like a architecture dependent co
On Tuesday, 12 January 2016 at 01:44:17 UTC, Jason Jeffory wrote:
So, how do I set the json to compile for x64?
You don't. You pass -ax86_64 (or --arch=x86_64) on the command
line. If you find that inconvenient, just make a batch file to do
it for you.
On Tuesday, 12 January 2016 at 03:52:33 UTC, Mike Parker wrote:
Actually, you could add -m64 in a dflags field (see [1]), but
then you're in a situation where DUB thinks you're compiling in
32-bit, so configuration fields that are architecture-dependent
will be off.
[1] http://code.dlang.or
On Tuesday, 12 January 2016 at 03:47:35 UTC, Mike Parker wrote:
On Tuesday, 12 January 2016 at 01:44:17 UTC, Jason Jeffory
wrote:
So, how do I set the json to compile for x64?
You don't. You pass -ax86_64 (or --arch=x86_64) on the command
line. If you find that inconvenient, just make a bat
On 12/01/16 4:53 PM, Mike Parker wrote:
On Tuesday, 12 January 2016 at 03:52:33 UTC, Mike Parker wrote:
Actually, you could add -m64 in a dflags field (see [1]), but then
you're in a situation where DUB thinks you're compiling in 32-bit, so
configuration fields that are architecture-dependent w
10 matches
Mail list logo
