[Proj] Trouble integrating Proj4 into application

[James Kilroy]

Thanks, I'll look at the ENV variables a bit more.  I am already using proj_api.h for my include.

 James T. Kilroy
Instrumental Solutions Inc.
721 China St.
Vicksburg MS 39183


(Office) 601-636-1637
(Cell) 601-415-0589




________________________________
From: nicolas david <ericnico.david at gmail.com>
To: PROJ.4 and general Projections Discussions <proj at lists.maptools.org>
Sent: Mon, June 14, 2010 2:17:22 PM
Subject: Re: [Proj] Trouble integrating Proj4 into application

Hi

I've done quite same thing recently ( debian and ubuntu) and don't have any specific problems. 
a) you have to take care when including proj4 files, because it's an ANSI C library and not a C++ lib. So, within a C++ project you have to use proj_api.h.
b) Concerning ENV variable. I know two of them and one is needed in order to find data file. 
PROJ_LIB : path to your proj data file ( nad, epsg etc..)
PROJ_DEBUG : if set to 1 make proj4 more verbose.

Hope it's helpful.

Nicolas David


2010/6/14 James Kilroy <jt_kilroy at yahoo.com>

>
>
>
>
>
>
>Hello 
>All,
> 
>My name is James 
>Kilroy and I am a brand new user of Proj4.  I have an extensive GIS back 
>ground so I have a good grasp of the concepts, and I have been coding 
>professionally (C/C++) for over 20 years.  I have installed the code base 
>for Proj4 on my Linux server (Fedora, very recent build).  The build went 
>without a hitch, all programs test out fine.  My problem is I can't get the 
>lib to compile into my project.  Keeps giving me lib not found errors, 
>though the lib is built, in place, and has proper permissions.  Are there 
>any specific compiler directives required or ENV variables that are needed that 
>I am not aware of?
> 
>Thanks,
> James 
>Kilroy
>_______________________________________________
>>Proj mailing list
>Proj at lists.maptools.org
>http://lists.maptools.org/mailman/listinfo/proj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20100614/54c251e4/attachment.html>