When using the Windows SDK 7.1 Command Prompt, how do I change the build environment without losing the nmake command? - nmake

I just installed the Windows 7.1 SDK and launched the SDK Command Prompt. If I type nmake, I am greeted with this message:
Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.
NMAKE : fatal error U1064: MAKEFILE not found and no target specified
Stop.
This is what I expect. However, I want to target Windows x64, so I type: setenv /x64. Then if I run nmake, I get an error:
'nmake' is not recognized as an internal or external command,
operable program or batch file.
Why am I getting this error? What am I doing wrong? I am using Windows 8 Consumer Preview 32-bit on my machine.
Edit: here is a diff of the PATH environment variable before and after:
http://diffchecker.com/9jdFi5d

It seems Microsoft forgot to place an nmake.exe binary in the x86_amd64 directory (the others all have it). I suggest copying the nmake.exe in the main Bin directory to the ´Bin/x86_amd64` directory.

Related

Rust running on Windows I am battling with a basic error targeting X86 vs x64

msvcrt.lib(chkstk.obj) : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
I found the problem. trying to run rust from developer powershell was causing the problem. In regular Windows PowerShell without path tweaks for Visual Studio, link.exe is not found in the command path, so cargo appears to magically discover the absolute path name in the x64 tools directory, which is the correct one. The host architecture of the shell does not affect this behavior.
Unfortunately, the launchers named Developer PowerShell and Developer Command Prompt for VS 2019 set up the command path for x86 tools. Perhaps it would be better for cargo to ignore the PATH-located executable on Windows if the registry-resolved tools directory appropriate for the target platform contains the executable file.

dtexec for linux, Argument for "set" is not valid

I am trying to run an SSIS package on Linux and running into an issue trying to pass in a variable. The following command works fine on Windows with SQL 2017, but errors on linux:
dtexec /F Package4.dtsx /SET \Package.Variables[pDIR].Value;"C:\test\\"
The error on linux is:
Microsoft (R) SQL Server Execute Package Utility
Version 14.0.1000.169 for 64-bit
Copyright (C) 2017 Microsoft. All rights reserved.
Argument ""Package.Variables[pDIR].Value"" for option "set" is not valid.
C:\test\: command not found
So the argument is invalid, and then the shell tries to execute the specified value as a command. Are parameters passed differently for the linux version?
After much trial and error I found the following to work:
dtexec /F Package5.dtsx /SET "\Package.Variables[pDIR].Value;"C:\\test\\""

CMake C:/IntelSWTools/ISSM_2016/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc is not a full path to an existing compiler tool

I am having issues compiling this project on zephyr.js, the instructions on their GitHub are for Linux however they do have an environment setup for Windows as well which I have completed to the letter.
When I run the compilation using the makefile I get:
CMake C:/IntelSWTools/ISSM_2016/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc is not a full path to an existing compiler tool.
I am using the msys terminal with MinGW and I have installed CMake separately and configured it... but why is it throwing this error? I have checked, and the file is actually there. If I type C:/IntelSWTools/ISSM_2016/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc. into the terminal, it also executes the compiler successfully.
Any ideas?
(Before anyone tells me to try on Linux, for now, it is a requirement to use Windows for this project)

rm command in Visual Studio 2012 Command Prompt

I have two machines the first one is
Machine A : Windows 7 professional with service pack 1 and VS2012
Machine B : Windows 8.1 and VS2012
Now Machine A gives the following result
E:\>rm
rm: too few arguments
Try `rm --help' for more information.
Whereas Machine B gives the following
C:\>rm
'rm' is not recognized as an internal or external command,
operable program or batch file.
How do I make the rm command work in Windows 8 VS2012 Command Prompt. Is their an add-on I need to install ?
Install GnuWin32 CoreUtils found at http://gnuwin32.sourceforge.net/packages/coreutils.htm. Then add C:\Program Files (x86)\GnuWin32\bin to your PATH.

Problems: Setting up MSTest2012 on a jenkins server without installing VS2012

I trying to setup MSTest2012 on a jenkins server without installing Visual Studio 2012 on it. I made it so far that I don't receive any "Assembly not found" error messages.
I was going to do some functional tests, so I copied a vs2012 project from my local machine to my jenkins server and tried something like that in cmd:
C:\VS2011Stub\Common7\IDE>MSTest.exe /testcontainer:D:\Users\Jenkins\Documents\V
isualStudio2012\Projects\HelloWorld\UnitTestProject4\bin\Debug\UnitTestProject4.
dll
Microsoft (R) Test Execution Command Line Tool Version 11.0.50727.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading D:\Users\Jenkins\Documents\VisualStudio2012\Projects\HelloWorld\UnitTest
Project4\bin\Debug\UnitTestProject4.dll...
D:\Users\Jenkins\Documents\VisualStudio2012\Projects\HelloWorld\UnitTestProject4
\bin\Debug\UnitTestProject4.dll
Ein Aufrufziel hat einen Ausnahmefehler verursacht.
This error message (Ein Aufrufziel hat einen Ausnahmefehler verursacht -> in english: Exception has been thrown by the target of an invocation.) is pretty... unhelpfully.
On my local machine the same cmd-code looks like that:
I dont know what to do... any suggestions, solutions??? Maybe someone have the same problem :/ Maybe mstest2012 still need other files to run correctly??
Im happy about every help!
edit:
I followed these steps to build MSTest.exe (VS2012) as standalone program on my jenkins server
edit2:
!!!Problem solved!!!
A few Microsoft.VisualStudio.QualityTools.#.dll's in GAC folders i copied didnt contain a version=11.0.0.0, so i openend C:\Windows\Assembly an took a look at the Microsoft.VisualStudio.QualityTools.# and checked the aviable versions and added the missing latest 11.0.0.0 Microsoft.VisualStudio.QualityTools.#.dll files on my jenkins server and registered them via gacutil(ver 4.0.30319.17929).
MSTest works now as stand alone program without installing MS Visual Studio 2012.
If anybody needs an instruction file just ask and i will upload it =)

Resources