[gdal-dev] PROJ_DATA/PROJ_LIB set during build time for python bindings?

[Even Rouault]

Hi,

A default PROJ_DATA value is "burnt" into libproj at its build time. Its 
value evaluates to "${CMAKE_INSTALL_FULL_DATADIR}/proj"

Similarly for GDAL_DATA which evaluates to 
"${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_DATADIR}/gdal"

Even

Le 04/09/2023 à 06:53, Ryan Yang a écrit :
> Hi!
>
> I see that PROJ_DATA is an env variable to be set for pointing to the 
> directory containing proj.db. However, I was wondering if there's a 
> way to configure this to be set during build time via some cmake arg 
> or if this was intended to be a dynamic env variable that can always 
> change?
>
> Asking because currently building gdal python bindings for bazel, but 
> it seems to require an env set for PROJ_LIB/PROJ_DATA whenever I'm 
> importing gdal.
>
> Thanks in advance!
> Ryan
>
>
> This email may be confidential and/or privileged. If you received this 
> communication by mistake, please don't forward it to anyone else, 
> delete all copies and attachments, and let me know that it has gone to 
> the wrong person.
>
> Statements made above may reflect a potential business arrangement. 
> Any such statements are provided solely as a basis for further 
> discussion, and are not intended to be and do not constitute a legally 
> binding obligation. No legally binding obligations will be created, 
> implied, or inferred until an agreement is duly executed in writing by 
> all parties.
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20230904/e1bc4383/attachment.htm>