On Thursday, 2 November 2017 at 13:01:05 UTC, rikki cattermole
wrote:
On 02/11/2017 1:56 PM, Andre Pany wrote:
On Thursday, 2 November 2017 at 12:21:50 UTC, rikki cattermole
wrote:
Override the shipped sc.ini file with your own. Simple and
effective solution.
What I just found out, by
On 02/11/2017 1:56 PM, Andre Pany wrote:
On Thursday, 2 November 2017 at 12:21:50 UTC, rikki cattermole wrote:
Override the shipped sc.ini file with your own. Simple and effective
solution.
What I just found out, by calling the batch file "vcvars64.bat" from the
visual studio
On Thursday, 2 November 2017 at 12:21:50 UTC, rikki cattermole
wrote:
Override the shipped sc.ini file with your own. Simple and
effective solution.
What I just found out, by calling the batch file "vcvars64.bat"
from the visual studio folder it seems everything is already pre
issue is, there is no way to install DMD using the executable setup
but only extracting the DMD archive. Also editing the sc.ini (by a build
script) I dislike.
I tried to begin with an easy example. I set the environment variables:
SET UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10
using the executable
setup but only extracting the DMD archive. Also editing the
sc.ini (by a build script) I dislike.
I tried to begin with an easy example. I set the environment
variables:
SET UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10
SET UCRTVersion=10.0.16299.0
SET
On Tue, 27 Dec 2016 22:09:49 +, Ryan wrote:
> I have a C library I want to link against that was compiled with VS
> 2013. I have VS2013 and VS2015 installed. I want DMD to use the 2013
> version, since the C-runtime in 2015 is not backwards compatible.
>
> Looking at sc.in
I have a C library I want to link against that was compiled with
VS 2013. I have VS2013 and VS2015 installed. I want DMD to use
the 2013 version, since the C-runtime in 2015 is not backwards
compatible.
Looking at sc.ini I see several entries that relate to the
linker, CRT, and SDK. How do I
02-Feb-2013 18:55, Rainer Schuetze пишет:
On 02.02.2013 14:16, Michael wrote:
Hi,
diff versions of Visual Studio may have diff installation path.
So here mine in proper order:
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\
LINKCMD64=%VCINSTALLDIR%\bin\x86_amd64\link.exe
On 02.02.2013 14:16, Michael wrote:
Hi,
diff versions of Visual Studio may have diff installation path.
So here mine in proper order:
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\
LINKCMD64=%VCINSTALLDIR%\bin\x86_amd64\link.exe
WindowsSdkDir=C:\Program Files (x86)\Micr
Hi,
diff versions of Visual Studio may have diff installation path.
So here mine in proper order:
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio
11.0\VC\
LINKCMD64=%VCINSTALLDIR%\bin\x86_amd64\link.exe
WindowsSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\
P.S.: I
Good day,
I remember hearing something about separating 32-bit and 64-bit
environment configuration in sc.ini, but I don't seem to see any
changes. I really don't get why is sc.ini so messed up and not
working? Is it so very hard to make a configuration file? I can't
get 64
On Sunday, 14 October 2012 at 09:40:36 UTC, Benjamin Thaut wrote:
Is there a way to make dmd ignore the default imports and
library search paths inside sc.ini?
Currently I have to keep two versions of dmd around, one with a
modified sc.ini and one with the original one, which is a bit
On 10/14/12, Benjamin Thaut wrote:
> Is there a way to make dmd ignore the default imports and library search
> paths inside sc.ini?
See http://dlang.org/dmd-windows.html#sc_ini
Is there a way to make dmd ignore the default imports and library search
paths inside sc.ini?
Currently I have to keep two versions of dmd around, one with a modified
sc.ini and one with the original one, which is a bit annoying.
A command line option for the compiler to ignore the defaults
14 matches
Mail list logo
