You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The compiled library can be found at /usr/local/lib, and the header files at /usr/local/include/lazperf (although notably not las.hpp, which the configure script appears to be looking for).
There may be some confusion with the naming conventions lazperf versus laz-perf. Perhaps this changed at some point and broke the search paths.
Please advise!
The text was updated successfully, but these errors were encountered:
For any future travelers, I think I may have sorted this out.
Taking a peek at lib/lazperf_adapter.hpp, it looks like the pointcloud code is build against an older version of lazperf, and the file names and directory structure have changed substantially since, which broke the header paths.
I got it to compile with version 1.5.0 , I will attach the Dockerfile I used.
Devs, let me know if this is worth a PR, or if I should just close this.
Happy holidays everyone!
To reproduce:
docker run pgpointcloud/pointcloud:latest
psql -U [ username ] -d [ database name ]
SELECT pc_lazperf_enabled();
The compiled library can be found at
/usr/local/lib
, and the header files at/usr/local/include/lazperf
(although notably notlas.hpp
, which the configure script appears to be looking for).There may be some confusion with the naming conventions
lazperf
versuslaz-perf
. Perhaps this changed at some point and broke the search paths.Please advise!
The text was updated successfully, but these errors were encountered: