[QGIS-Developer] Compiling against homebuilt GDAL

[Even Rouault]

When you run "make -jSOMETHING" the error message may be quite above the 
end of the standard error stream. Look further above for a "error:" 
string or something like that. Or just  re-run "make", and wait for it 
to fail. The error message should then just be in the last lines

Le 12/03/2024 à 11:44, Thomas Larsen Wessel a écrit :
> Sorry for the late reply.
>
> @Richard; Your advice is certainly useful. I could use some advice on 
> best practices :)
>
> After *installing* GDAL, I was able to run cmake without issues. But 
> then make would fail at 56% every time (simply printing "Error 2"). By 
> coincidence I found out, that if I just ran the same make command one 
> more time (without cleaning), it would progress beyond the 56%, and 
> run for another 20 minutes before it failed at 64%. If I ran for a 
> third time it would progress a bit more (or maybe the output just 
> looks different), but still at 64%. Any additional attempts give no 
> further progress.
>
> mkdir build; cd build
> GDAL_DIR=/home/velle/install-gdal-3.7.2 cmake .. 
> -DCMAKE_BUILD_TYPE=DEBUG 2>&1 | tee cmakelog.txt
> time make -j4 VERBOSE=1 2>&1 | tee make_j4_1.txt
> time make -j4 VERBOSE=1 2>&1 | tee make_j4_2.txt
> time make -j4 VERBOSE=1 2>&1 | tee make_j4_3.txt
>
> The last part of make_j4_3.txt looks like this:
>
> Dependencies file 
> "src/core/CMakeFiles/qgis_core.dir/vectortile/qgsvtpktiles.cpp.o.d" is 
> newer than depends file 
> "/home/velle/b/QGIS/build/src/core/CMakeFiles/qgis_core.dir/compiler_depend.internal".
> Dependencies file 
> "src/core/CMakeFiles/qgis_core.dir/vectortile/qgsvtpkvectortiledataprovider.cpp.o.d" 
> is newer than depends file 
> "/home/velle/b/QGIS/build/src/core/CMakeFiles/qgis_core.dir/compiler_depend.internal".
> Dependencies file 
> "src/core/CMakeFiles/qgis_core.dir/vectortile/qgsxyzvectortiledataprovider.cpp.o.d" 
> is newer than depends file 
> "/home/velle/b/QGIS/build/src/core/CMakeFiles/qgis_core.dir/compiler_depend.internal".
> Consolidate compiler generated dependencies of target qgis_core
> make[2]: Leaving directory '/home/velle/b/QGIS/build'
> make  -f src/core/CMakeFiles/qgis_core.dir/build.make 
> src/core/CMakeFiles/qgis_core.dir/build
> make[2]: Entering directory '/home/velle/b/QGIS/build'
> make[2]: Nothing to be done for 'src/core/CMakeFiles/qgis_core.dir/build'.
> make[2]: Leaving directory '/home/velle/b/QGIS/build'
> [ 64%] Built target qgis_core
> make[1]: Leaving directory '/home/velle/b/QGIS/build'
> make: *** [Makefile:166: all] Error 2
>
> I don't see anything failing until the point it aborts. Can I get more 
> details about what is failing?
>
>
>
> It took some time to find the VERBOSE=1 option, but even with verbose 
> output I don't understand what is going on. Is it
>
>
>
>
>
> On Thu, Feb 29, 2024 at 8:52 AM Matthias Kuhn <matthias at opengis.ch> wrote:
>
>
>
>     On Wed, Feb 28, 2024 at 7:45 PM Even Rouault via QGIS-Developer
>     <qgis-developer at lists.osgeo.org> wrote:
>
>         and then when configuring QGIS, use
>         GDAL_DIR=$HOME/install-gdal-3.7.2  . I'm not totally sure
>         about that last part. may require tweaking. you could alter
>         the PATH to point to $HOME/install-gdal-3.7.2/bin so that
>         "gdal-config" from your installed GDAL is picked up
>
>
>     It will first try to locate GDAL via cmake config
>     (https://github.com/qgis/QGIS/blob/master/cmake/FindGDAL.cmake#L16).
>     Only if that fails it will fall back to the gdal-config executable.
>
>     To help cmake find a package on a custom install prefix, refer to
>     https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure
>
>     in your case I'd suggest using `-D
>     GDAL_ROOT=$HOME/install-gdal-3.7.2` after installing
>
>     Matthias
>
-- 
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/qgis-developer/attachments/20240312/227e8fe4/attachment-0001.htm>