Re: [gdal-dev] GDAL with external zlib

2013-05-15 Thread Mihaela Gaspar
ild GDAL > on windows without it's own zlib since there is nothing in nmake.opt about > it. > > I do believe it is fairly common on linux to build with the system zlib. > > Best regards, > Frank > > > > On Wed, May 15, 2013 at 4:18 PM, Mihaela Gaspar < &g

[gdal-dev] GDAL with external zlib

2013-05-15 Thread Mihaela Gaspar
I have built GDAL, and was experimenting on a project. I have external zlib 1.2.5 The external libraries are generally statically linked. When trying the same thing with gdal, I got a link error: error LNK2005: _deflate_copyright already defined in gdal.lib(deflate.obj) I tried to find where gd

Re: [gdal-dev] Is it possible to build pdb files in Release ?

2013-05-14 Thread Mihaela Gaspar
Thank you, it's perfect. On Tue, May 14, 2013 at 12:41 PM, David Strip wrote: > The pdb file is generated by the /Zi flag. Add that to the list of flags > in your release build. > > > On 5/14/2013 10:55 AM, Mihaela Gaspar wrote: > > I built GDAL in both Debug and

Re: [gdal-dev] What is the difference between gdal.lib and gdal.i.lib ?

2013-05-14 Thread Mihaela Gaspar
u want to avoid using the GDAL DLL. > > Best regards, > Frank > > > > On Tue, May 14, 2013 at 10:11 AM, Mihaela Gaspar < > mihaela.gas...@urbanrobotics.net> wrote: > >> The devinstall option copies gdal.i.lib into the target library >> installation

[gdal-dev] What is the difference between gdal.lib and gdal.i.lib ?

2013-05-14 Thread Mihaela Gaspar
The devinstall option copies gdal.i.lib into the target library installation folder. I see another lib file created, gdal.lib What is the difference between them ? I I link statically, do I use gdal.i.lib ? Thank you. ___ gdal-dev mailing list gdal-dev@li

[gdal-dev] Is it possible to build pdb files in Release ?

2013-05-14 Thread Mihaela Gaspar
I built GDAL in both Debug and Release. The default behavior is to create .pdb files in Debug, but not in Release. I would like to get a pdb file in Release build as well, is it possible ? The only lines I see that have to do with pdb, are: !IFNDEF DEBUG OPTFLAGS= $(CXX_ANALYZE_FLAGS) /nologo /

Re: [gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
kefile< > /span>.vc PLATFORM=x64 > start /b /wait nmake.exe /f ma > kefile< > /span>.vc devinstall PLATFORM=x64 > > The exact same thing builds in Win32... > > > > On Mon, May 13, 2013 at 8:53 AM, Mihaela Gaspar < > mihaela.gas...@urbanrobotics.net>

Re: [gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
The solution from Joaquim Luis worked. I used call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" amd64 Thank you ! On Mon, May 13, 2013 at 11:51 AM, Mihaela Gaspar < mihaela.gas...@urbanrobotics.net> wrote: > Thank you. > I have all the depend

Re: [gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
013-05-13 12:53 PM, Mihaela Gaspar wrote: > > > > In x64,I get linker errors: > > > > |LINK : error LNK2001: unresolved external symbol _OGRFeatureStylePuller > > LINK : error LNK2001: unresolved external symbol _OSRValidate > > ... > > gdal19.dll : fatal e

Re: [gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
vc from > there. > > ** ** > > Best regards, > > Martin > > ** ** > > *From:* gdal-dev-boun...@lists.osgeo.org [mailto: > gdal-dev-boun...@lists.osgeo.org] *On Behalf Of *Mihaela Gaspar > *Sent:* Monday, May 13, 2013 12:15 PM > *To:* gdal-dev@lists.osge

Re: [gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
=x64 The exact same thing builds in Win32... On Mon, May 13, 2013 at 8:53 AM, Mihaela Gaspar < mihaela.gas...@urbanrobotics.net> wrote: > I am trying to build GDAL (1.9.2) in x64. > > In the instructions, I see: > > # Uncomment the following if you are building for

[gdal-dev] Can't build gdal in x64

2013-05-13 Thread Mihaela Gaspar
I am trying to build GDAL (1.9.2) in x64. In the instructions, I see: # Uncomment the following if you are building for 64-bit windows# (x64). You'll need to have PATH, INCLUDE and LIB set up for 64-bit# compiles.!IF "$(PLATFORM)" == "x64" WIN64=YES!ENDIF And then, lower, # Under win64, symbols