[gdal-dev] Can't compile GDAL 2.4.0 with Visual 2017 - 32 bits

[Joaquim Manuel Freire Luís]

You would run it with a command like this

"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars32.bat" x86

I do it this way because I also want to control the path and thus avoid contamination from other parts of my otherwise potentially messy environment. But since you run from the "x86 Command prompt for VS 2017" the vcvars32.bat was already run for you so no need to worry about that. The source of your trouble must me than be something else.




Hello Joaquim,
Thank you for answering ,

I run nmake from within the x86 Command prompt for VS 2017, and no I had not previously run that batch.

I just tried that tough, and ran the command :
vcvarsall.abt  x86  10.0.17763.0
(that's my version of the windows SDK), I got "The specified configuration type is missing. The tools for the configuration might not be installed".

Do you know what it means ?

Thanks,

Rémi




De : Joaquim Manuel Freire Luís [mailto:jluis at ualg.pt]
Envoyé : lundi 25 février 2019 12:23
À : PROVIN; gdal-dev at lists.osgeo.org<mailto:gdal-dev at lists.osgeo.org>
Objet : RE: [gdal-dev] Can't compile GDAL 2.4.0 with Visual 2017 - 32 bits

You are running the nmake command from within a cmd window where you had previously run the vcvarsall.bat for 32 bits, right?

From: gdal-dev <gdal-dev-bounces at lists.osgeo.org<mailto:gdal-dev-bounces at lists.osgeo.org>> On Behalf Of PROVIN
Sent: Monday, February 25, 2019 2:45 PM
To: gdal-dev at lists.osgeo.org<mailto:gdal-dev at lists.osgeo.org>
Subject: [gdal-dev] Can't compile GDAL 2.4.0 with Visual 2017 - 32 bits

Hello Jeff,
Thank you for your answer, I had tried that already (I usually compile GDAL this way with NMAKE),
but I had the exact same error.

Maybe this has to do with my installation of Visual Studio ?


Remi




Hi Remi,



Personally I'd recommend using the provided nmake.opt inside GDAL's root

directory, and modifying that for your own local libraries.  (note that

the cleanest way to do this is to create a new file 'nmake.local' and

put your settings in there, leaving the distributed nmake.opt as

reference only, and then execute that with the command:



        nmake /f makefile.vc



(others may recommend using the *.bat magic, but sometimes the raw

commandline is more fun ha)



Have a nice weekend,



-jeff









On 2019-02-21 9:18 AM, PROVIN wrote:

> Hello,

>

> I am trying to compile GDAL (version 2.40, but I also tried 2.3.1) with

> Visual 2017 in 32 bits.

>

> I used the generate_vcxproj.bat to generate my Visual project /

> solution, this way (as indicated) :

>

> generate_vcxproj.bat   15.0 32 gdal_vs2017

>

> The compilation gives the following error :

>

> fatal error C1083: Impossible d'ouvrir le fichier include : 'stdio.h' :

> No such file or directory (compilation du fichier source cpl_list.cpp)

>

> I have this error for all the files cpl_XXXX.cpp  of "port" folder.

>

> It is strange because these files are accessible when I right click on

> the line

>

> #include <stdio>

>

> and open the file.

>

> I tried to retarget the project, tried to reinstall Visual 2017.

>

> I would be glad if anyone had any advice !

>

> Thank you,

>

> REMI

>



--

Jeff McKenna

MapServer Consulting and Training Services

https://gatewaygeomatics.com/


[sgn]

Rémi PROVIN
Ingénieur géomatique
 854 route de Rémire - 97354 Rémire Montjoly
tél : 05-94-25-61-93 - fax : 05-94-25-61-94

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20190225/140eb1ab/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5615 bytes
Desc: image001.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20190225/140eb1ab/attachment-0001.png>