Skip to content

Comments

Create NMake64.mak#2621

Closed
fcharlie wants to merge 1 commit intodlang:masterfrom
fcharlie:patch-1
Closed

Create NMake64.mak#2621
fcharlie wants to merge 1 commit intodlang:masterfrom
fcharlie:patch-1

Conversation

@fcharlie
Copy link

No description provided.

@fcharlie fcharlie closed this Oct 17, 2014
@fcharlie fcharlie deleted the patch-1 branch October 17, 2014 17:27
@jmdavis
Copy link
Member

jmdavis commented Oct 18, 2014

FYI. You don't have to create a new pull request to make changes. You can just push any new changes to the same branch (with -f if you've rebased), and the pull will be updated. And you can always edit the pull's description by just clicking on the pencil icon on the top-right of the box.

@fcharlie
Copy link
Author

@jmdavis I Created a New pull request ,Another is the NMake64 complete support
#2622

@WalterBright
Copy link
Member

The trouble with this is it creates another makefile that must be maintained in parallel with the others. I understand being comfortable using nmake, and preferring an nmake makefile, but other than that what is the benefit?

@jmdavis
Copy link
Member

jmdavis commented Oct 19, 2014

@ForceGROUP

Created a New pull request

I know. My point was that it was unnecessary. You could have just updated this one.

@fcharlie
Copy link
Author

@jmdavis I'm sorry, but I'm not too familiar with pull request operations and.

@fcharlie
Copy link
Author

@WalterBright Win64.mak file, there are some limitations when using the new version of VisualStudio, or VisualStudio is installed on a different partition, users need to modify Win64.Mak to the successful completion of compilation

VCDIR=\Program Files (x86)\Microsoft Visual Studio 10.0\VC
SDKDIR=\Program Files (x86)\Microsoft SDKs\Windows\v7.0A

DMD=dmd

CC="$(VCDIR)\bin\amd64\cl"
LD="$(VCDIR)\bin\amd64\link"
AR="$(VCDIR)\bin\amd64\lib"
CP=cp 

NMake64.mak, the code is like this:

DMD=dmd

CC=cl.exe
LD=link.exe
AR=lib.exe
CP=cp

Running VS2013 x64 's native tools command prompt
You can easily build Phobos.

Process of building the whole DMD is still in trouble, I recommend using CMake or Ninja tools for automated builds, even writing a PowerShell script that checks the host machine's environment to find an appropriate version of VisualStudio, compile the DMD, and then, SC.ini, next, generate Makefile druntime, compile, next, Phobos Makefile generated, compiled, Production and installation of packages. On POSIX systems using shell scripts.

CMake's benefits are such that I participated in a project called ClangSetupvNext, users can use the GUI to select the build mode and target, automated build and package LLVM.
Generally hope DMD can better build automation
Thank your

@dnadlinger dnadlinger mentioned this pull request Oct 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants