nmake

Linker Error Building GDAL

折月煮酒 提交于 2019-12-05 01:50:55
问题 I am building GDAL from source using the MSVC 2015 64-bit command prompt. I am using Windows 8. Part way through the build, I get the following error: Creating library gdal_i.lib and object gdal_i.exp odbccp32.lib(dllload.obj) : error LNK2019: unresolved external symbol _vsnwprintf_s referenced in function StringCchPrintfW gdal201.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\link.EXE"' : return

Building Qt - NMAKE : fatal error U1077: 'cd' : return code '0x2'

旧巷老猫 提交于 2019-12-04 18:47:00
问题 I'm trying to build Qt5.5 with static linking using msvc2015 but I'm having the following errors (actually there's a whole lot of them but I'm only listing a few, they're all quite the same): K:\Archivos de programa\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2873: 'uint_fast64_t': symbol cannot be used in a using-declaration K:\Archivos de programa\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(52): error C2039: 'intmax_t': is not a member of '`global namespace'' K:\Archivos

printing long compilation lines with MS NMAKE

只愿长相守 提交于 2019-12-04 11:27:58
I have a legacy MS NMAKE Makefile I need to fix a few bugs in. There are some very long command lines I wish to debug that are being executed using the NMAKE trick of "inline files" : dep: cmd @<<tmpfilename cmd_args.. << When changing the line to dep: echo cmd @<<tmpfilename cmd_args.. << NMAKE complains that the line is too long. Is there any other trick I can apply in order to view the command line NMAKE is actually executing? Elazar Leibovich In order to keep the temporary file that keeps your command line append the KEEP keyword after the final << . For example dep: echo cmd @<

nmake.exe is not found in the windows\system32 folder? how to setup nmake command in windows?

一个人想着一个人 提交于 2019-12-04 05:25:28
问题 When I type the nmake command in the Command Prompt, I am getting this error: 'nmake' is not recognized as an internal or external command operable program or batch file. Also, I couldn't find the nmake.exe file in my system. How to setup the nmake command on Windows? 回答1: NMake is part of Microsoft's build tools for building C++ projects. You can get nmake as well as the MSVC++ compiler by downloading Visual C++ Express. Visual C++ Express which runs perfectly fine on Windows 7 . It will

Building Qt - NMAKE : fatal error U1077: 'cd' : return code '0x2'

旧巷老猫 提交于 2019-12-03 12:10:26
I'm trying to build Qt5.5 with static linking using msvc2015 but I'm having the following errors (actually there's a whole lot of them but I'm only listing a few, they're all quite the same): K:\Archivos de programa\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(50): error C2873: 'uint_fast64_t': symbol cannot be used in a using-declaration K:\Archivos de programa\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(52): error C2039: 'intmax_t': is not a member of '`global namespace'' K:\Archivos de programa\Microsoft Visual Studio 14.0\VC\INCLUDE\cstdint(52): error C2873: 'intmax_t': symbol

Using nmake with wildcards in the makefile

独自空忆成欢 提交于 2019-12-03 06:31:59
I am attempting to set up an nmake makefile to export our balsamiq mockup files to png files automatically, but I'm afraid I can't make heads nor tails of how to make a generic rule for doing so, without explicitly listing all the files I want exported. This page details the command line syntax for exporting the files, and this page contains an example which looks like it contains a generic rule for .obj files to .exe files. The makefile I have tried so far looks like this: .bmml.png: "C:\Program Files\Balsamiq Mockups\Balsamiq Mockups.exe" export $< $@ But this doesn't work. If I simply run

VS2012 nmake using v110_xp toolset?

做~自己de王妃 提交于 2019-12-03 03:25:47
Is there a way to use v110_xp toolset (instead of default "v110") when compiling with "nmake" ? I'm trying to compile a Qt5 library for VisualStudio2012 and I need it to work on Windows XP machines too. I've managet to compile all Qt5 libraries using VS2012 with nmake, but even simple test applications fails to run on XP machines giving me the " The procedure entry point _except_handler4_common could not be located in the dynamic link library msvcrt.dll ". ( On Windows 7 machines my test application is working normally ) Edit Makefile.Debug or Makefile.Release file Add -D_USING_V110_SDK71_ to

nmake fatal error U1034: syntax error : separator missing

落花浮王杯 提交于 2019-12-02 16:38:23
问题 # gnsdk C# wrapper sample makefile ## CC=Csc.exe CP=cp GNSDK_LIB_PATH=../../../../lib/$(GNSDK_PLATFORM) GNSDK_WRAPPER_LIB_PATH=../../lib/$(GNSDK_PLATFORM) GNSDK_MARSHAL_LIB=$(GNSDK_WRAPPER_LIB_PATH)/gnsdk_csharp_marshal.dll GNSDK_CSHARP_LIB=../../lib/gnsdk_csharp.dll CSHARP_FLAGS=/noconfig /nowarn:1701,1702 /nostdlib+ /errorendlocation CSHARP_REFS=/reference:$(GNSDK_CSHARP_LIB) /reference:"Microsoft.CSharp.dll" /reference:"mscorlib.dll" /reference:"System.Core.dll" /reference:"System.Data

nmake modify macro based on target

与世无争的帅哥 提交于 2019-12-02 13:47:58
问题 I've got a Makefile.mak where I optionally create a test.exe or a DLL from my C-based source code. I'm using CL.EXE and NMAKE. I'd like to modify my CFLAGS macro like this when the target is TEST.EXE: CFLAGS = $(CFLAGS) -DMAIN And, of course, I use this in my C code: #ifdef MAIN ... int main()... yada yada #endif I had tried !IF $@ == "test.exe" but it crashed out and doesn't work logically since the $@, target, isn't deterministic in that part of the makefile. The logical place to define the

Use NMAKE to make all source in a directory?

蹲街弑〆低调 提交于 2019-12-02 09:49:51
问题 Using nmake, is it possible to have the makefile build all the .cpp files in the current directory automatically, without having to specify them individually? So, instead of something like: O = $(OBJ_DIR)/main.obj {$(SOURCE_DIR)}.cpp{$(OBJ_DIR)}.obj: ---COMPILE $< HERE--- I'd like to avoid having to specify each obj to make. Can this be done? 回答1: .cpp.obj: $(CC) $(CFLAGS) $*.cpp is a default rule that will automatically resolve .obj dependencies from .cpp files... 回答2: You can use a rule