[Gdal-dev] What's necessary to use GDAL/OGR Libery!

Roger James rogerjames99 at btinternet.com
Mon Jul 14 11:39:50 EDT 2003


Markus,

I have found nmake -f makefile.vc devinstall works better than just
"install". If you have built with vc this also copies the header files
into the include directory.

You may also have to change the

lib:

line in makefile.vc to

lib: $(LIBOBJ)

to stop some complaints.

Roger

> -----Original Message-----
> From: gdal-dev-admin at remotesensing.org [mailto:gdal-dev-
> admin at remotesensing.org] On Behalf Of Frank Warmerdam
> Sent: 14 July 2003 15:14
> To: gdal-dev at remotesensing.org
> Subject: Re: [Gdal-dev] What's necessary to use GDAL/OGR Libery!
> 
> Markus Reichert wrote:
> > But now, I ask myself, which of all the libs, dlls and
> > header files I really need to build a program that is
> > using GDAL/OGR functionality and how to build them in
> > one dirctory so I can use them easily in another
> > Visual Studio project (best without using a
> > makefile)??
> > In the online documentation I have not found
> > information about such "simple" problems - sorry!
> 
> Markus,
> 
> In order to build projects that build and link against GDAL/OGR it is
> generally easiest to "install" GDAL.  This will copy the required
include
> files, DLLs and so forth into a seperate set of directories.  To
configure
> this modify the following variables in the gdal\nmake.opt file to your
> liking ... the defaults are really just what I do on my machine and
not
> that great for general use:
> 
> BINDIR = D:\bin
> PY_INST_DIR = D:\bin\pymod
> LIBDIR = D:\bin\lib
> INCDIR = D:\bin\include
> DATADIR = D:\bin\data
> 
> Now when building a project your should include the INCDIR in your
include
> path, the LIBDIR in your libpath, and BINDIR in your path. All the
include
> files you need should be installed intot he INCDIR directory for
instance.
> The only library you should need to link against is gdal_i.lib, the
stub
> library for gdal11.dll.  Depending on your build options there may be
> lots of other DLLs also required, but you will need to track that
> yourself.
> For instance the DLLs for ECW, Oracle, OGDI, etc.
> 
> I hope this helps.  I have updated the GDAL building page in CVS to
> reflect
> some of this information.
> 
> Best regards,
> --
>
---------------------------------------+--------------------------------
--
> ----
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | Geospatial Programmer for
Rent
> 
> 
> _______________________________________________
> Gdal-dev mailing list
> Gdal-dev at remotesensing.org
> http://remotesensing.org/mailman/listinfo/gdal-dev





More information about the Gdal-dev mailing list