When the configure script checks for the proj library it fails because it
can't find the "proj.h" file,even though the proj.h files directory was
specifically included in the cxxflags.
checking for PROJ >= 6 library... checking for proj_create_from_wkt in
-lproj... no
...
checking for internal_pro
If I try to run the gdal configure script with a --with-proj targeting a
static proj 6 lib I get complaints about not being able to find proj 6
symbols named internal_proj* when the configure script does various test
compiles for proj. These functions don't seem to exist in src and include
director
Nevermind, got it to run with minimal flags.
> gcc testprogram.c -o testprogram -L$projInstallDir/lib -lproj
> ldd testprogram
linux-vdso.so.1 (0x7fffcb57f000)
libproj.so.15 =>
/home/loshjawrence/clonesRedo/agi-asset-pipeline/build/ThirdParty/proj.4/lib/libproj.so.15
(0x7f3f
I tried copying the body the test program that the configure script uses to
see if the specified proj is usable. Running the gcc command manually:
gcc testprogram.c -o testprogram -L$projInstallDir/lib
-Wl,-rpath,$projInstallDir/lib -I$projDir/include -I$projDir/src
Using -L -Wl -rpath to specify
Trying to go through the instructions as-is (apt-get install sqlite3 bin and
lib, rename proj's .so libs, run patchelf, etc.) from
https://trac.osgeo.org/gdal/wiki/BuildingOnUnixGDAL25dev
The gdal configure script is still unable to find proj. Looking through the
config.log, I see there are two -l
Looking at the solution on
https://trac.osgeo.org/gdal/wiki/BuildingOnUnixGDAL25dev
I was only able to build proj 6 as a static library. There was an error when
I tried to use --enable-shared=yes:
-Wl,libproj.so.15 -o .libs/libproj.so.15.1.0
/usr/bin/x86_64-linux-gnu-ld:
/home/loshjawrence/clones
I removed the official sqlite3 binary. Then I renamed our sqlite3_shell
(binary we generate but for some reason has a _shell appended)but like
before, configure couldn't discover it.
I did a
sudo mv $sqlite3InstallDir/bin/sqlite3 /usr/bin
and it was able to find it. I tried other directories lis
Ok, was able to get the proj configure script to go all the way through with
the official sqlite3 binary installed via apt-get and using our generated
libsqlite3.a and the amalgamation files for the include files
Now I just need to figure out how to get the proj configure script to use a
user gene
For the error:
checking for SQLITE3... yes
checking for sqlite3... no
configure: error: Please install sqlite3 binary.
I first tried adding the install dir of our sqlite3 shell executable to the
$PATH var:
> ls $sqlite3InstallDir/bin
sqlite3_shell
> PATH="$sqlite3InstallDir/bin:$PATH"
> echo $PATH
We have a sqlite3_shell binary that gets built, not sure if this is
interchangeable / same thing as the sqlite3 binary that it wants.
ls $sqlite3InstallDir/bin
sqlite3_shell
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
__
On jeudi 16 mai 2019 11:46:53 CDT joshl wrote:
> Thanks Even, setting up the two SQLITE3 vars seemed to get past one of the
> sqlite errors, but now I need to find out where our manually built sqlite3
> binary is since its complaining about that now. Though I'm not sure which
> flags that info will
Thanks Even, setting up the two SQLITE3 vars seemed to get past one of the
sqlite errors, but now I need to find out where our manually built sqlite3
binary is since its complaining about that now. Though I'm not sure which
flags that info will need to get passed to.
current error output:
checking
On jeudi 16 mai 2019 10:35:22 CDT joshl wrote:
> Thanks for the info Richard.
>
> Right now I'm having issues running proj's ./configure. We build sqlite3
> statically using the sqlite-amalgamation, the version we use is 3.26.0.
>
> Using https://trac.osgeo.org/gdal/wiki/BuildingOnUnixGDAL25dev a
Thanks for the info Richard.
Right now I'm having issues running proj's ./configure. We build sqlite3
statically using the sqlite-amalgamation, the version we use is 3.26.0.
Using https://trac.osgeo.org/gdal/wiki/BuildingOnUnixGDAL25dev as a guide,
the configure script is unable to find sqlite3.
Well, I'm glad it's not just me. I was getting worried there for a while...
On Thu, May 16, 2019 at 8:02 AM Richard Duivenvoorde
wrote:
> On 16/05/2019 16.53, joshl wrote:
> > Tried doing the LDFLAGS export but got the same errors. My full manual
> > ./configure command (just running on command
On 16/05/2019 16.53, joshl wrote:
> Tried doing the LDFLAGS export but got the same errors. My full manual
> ./configure command (just running on command line) that I'm testing (to at
> least get past this error) in the gdal git submodule dir is here:
>
> *projInstallDir*='/home/loshjawrence/clone
Tried doing the LDFLAGS export but got the same errors. My full manual
./configure command (just running on command line) that I'm testing (to at
least get past this error) in the gdal git submodule dir is here:
*projInstallDir*='/home/loshjawrence/clonesRedo/agi-asset-pipeline/build/ThirdParty/pr
Did you set ./configure --with-proj=${INSTALL_DIR}?
Where INSTALL_DIR is the install directory (prefix) of proj/gdal.
I also had to set:
export LDFLAGS="-L${INSTALL_DIR}/lib -Wl,-rpath,${INSTALL_DIR}/lib"
to get gdal to actually link against the new proj (vs the system
installed one).
On 5
Sorry, just saw the other thread regarding this issue. At a glance didn't
seem to have the same build issue as I did but I'll comb through when I have
more time later to see it any of those suggestions moves the needle.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
Hello,
I'm having trouble getting gdal to build with proj on linux. They are both
brought in as git submodules in a git repo and get built via cmake.
To get proj 6.0.0 to build, I had to add a small modification to its
CMakeLists.txt where it uses both the src and include folders for the
include_
20 matches
Mail list logo
