Conversation
|
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. |
|
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? |
I know. My point was that it was unnecessary. You could have just updated this one. |
|
@jmdavis I'm sorry, but I'm not too familiar with pull request operations and. |
|
@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 NMake64.mak, the code is like this: Running VS2013 x64 's native tools command prompt 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. |
No description provided.