-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDAL doesn't build the 3Di driver on Ubuntu 22.04 #466
Comments
specify correct SQLITE3 on command line
also when you run the executable, make sure that sqlite3 library is on your LD_LIBRARY_PATH. when you use different one it crashes |
I tried specifying the SQLite3 driver explicitly, but that made no difference:
When running
|
update: I forgot to add the custom FindSQLite3.cmake file back. When I use the custom FindSQLite3.cmake from this repo and pass in the SQLite3 library paths by hand, it works. So in summary: |
I noticed that when compiling MDAL on Ubuntu 22.04, the 3Di driver is not built.
tl;dr: the 3Di driver depends on SQLite3, which isn't found with the included
FindSQLite3.cmake
even when correctly installed; removing it to use the defaultFindSQLite3.cmake
fixes that issue, but then the linker fails onmdal_unittests
with an SQLite3 symbol error.Full details are as follows:
The 3Di driver can only be built when the NetCDF and SQLite3 drivers are found:
MDAL/mdal/mdal_driver_manager.cpp
Lines 46 to 48 in 93b6c2e
MDAL/mdal/mdal_driver_manager.cpp
Lines 241 to 243 in 93b6c2e
and when running
cmake
I get the following output:Consequently, as SQLite3 is not found, the
mdal_3di
driver is not built afterwards when runningmake
.SQLite3 is correctly installed, though:
Removing the custom
FindSQLite3.cmake
file from the projectcmake
directory to rely on the defaultcmake
implementation ofFindSQLite3.cmake
fixes that problem, insofar that SQLite3 is now found:but now, when running
make
, although themdal_3di
driver is now successfully built, the build fails at the end when linkingmdal_unittests
:The text was updated successfully, but these errors were encountered: