There are small API changes between 2.5 > 2.6 > 2.8 so using the latest binding with older PDAL version will not work. This is a problem when we produce a tool for a client, since we can hardly have an exact match between the binding and the local installation of PDAL. Many users have limited control over what is installed and which version is or can be installed on the computer.
So the need for a static build is really important here if you want PDAL to be embedded in tools.
It could be a new maven artifact named pdal-bundle.
The previous bug report which let to this issue.
There are small API changes between 2.5 > 2.6 > 2.8 so using the latest binding with older PDAL version will not work. This is a problem when we produce a tool for a client, since we can hardly have an exact match between the binding and the local installation of PDAL. Many users have limited control over what is installed and which version is or can be installed on the computer.
So the need for a static build is really important here if you want PDAL to be embedded in tools.
It could be a new maven artifact named
pdal-bundle.The previous bug report which let to this issue.