Opened 2 years ago

Closed 23 months ago

#6032 closed defect (fixed)

build error when using SETARGV option

Reported by: ccjklppp Owned by: warmerdam
Priority: high Milestone: 2.1.0
Component: Utilities Version: 2.0.0
Severity: major Keywords:
Cc:

Description

using file pattern (i.e. c:\doq\*.tif) as source dataset for gdaltindex and gdalbuildvrt results with error: ERROR 4: `C:\doq\*.tif' does not exist in the file system

Change History (7)

comment:1 Changed 2 years ago by Even Rouault

It depends on the binary distribution of GDAL you use has been compiled. If it has been compiled with the SETARGV option of http://trac.osgeo.org/gdal/browser/trunk/gdal/nmake.opt uncommented, I believe it should work. From I can see in http://build.gisinternals.com/sdk/build-output/vc8-20150714-1-10-29-46-vc8-dev.txt , the binaries of gisinternals.com should have wildcard support.

comment:2 Changed 2 years ago by ccjklppp

I compiled the official gdal 2.0.0 version myself

comment:3 Changed 2 years ago by Even Rouault

Resolution: invalid
Status: newclosed

Maybe you can try my above hint ?

I'm closing with the assumption that this will fix your issue.

comment:4 Changed 2 years ago by ccjklppp

When ן uncomment the VCDIR and SETARGV variables (and set the paths as needed), I get an error in the compilation:

plugins:

        for %d in (                  ) do  cd %d  && nmake /nologo /f makefile.vc plugin  && cd ..  || exit 1

        cd ..\..

        cd apps

        nmake /nologo /f makefile.vc

NMAKE : fatal error U1073: don't know how to make 'lib\amd64\setargv.obj'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\amd64\nmake.EXE"' : return code '0x2'

Stop.
Last edited 2 years ago by ccjklppp (previous) (diff)

comment:5 Changed 2 years ago by ccjklppp

Resolution: invalid
Status: closedreopened
Summary: using file-pattern (i.e. c:\doq\*.tif) in gdal utilities doesn't workbuild error when using SETARGV option

comment:6 Changed 2 years ago by ccjklppp

ok... I found the problem. when using the nmake.opt with the 'VCDIR' and 'SETARGV' as following, the build fails:

# Location of Visual C++ directory (only required for following SETARGV stuff)
VCDIR   = 	"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC"

# Enable the following if VCDIR set properly, and you want the utility
# programs to be able to expand wildcards. 
SETARGV =	$(VCDIR)\lib\amd64\setargv.obj

but when using only 'SETARGV' variable with the full path, the build succeeds.

# Location of Visual C++ directory (only required for following SETARGV stuff)
#VCDIR   = 	"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC"

# Enable the following if VCDIR set properly, and you want the utility
# programs to be able to expand wildcards. 
SETARGV =	"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\lib\amd64\setargv.obj"

I don't know why...

So, I think you can delete the 'VCDIR' variable from the original nmake.opt file because it's only confusing and unneeded.

Last edited 2 years ago by ccjklppp (previous) (diff)

comment:7 Changed 23 months ago by Even Rouault

Milestone: 2.0.12.1.0
Resolution: fixed
Status: reopenedclosed

trunk r29657 "nmake.opt: make it less error prone to define SETARGV when paths include spaces (#6032)"

Note: See TracTickets for help on using tickets.