[pdal] PDAL Windows debug configuration

[Howard Butler]

On 4/25/18 7:11 AM, Odd Ragnar Lydersen wrote:
> Coming from libLas, to PDAL, I really just want to use the Las functionality, and I have only tested for the las format, and it works.
>
> My test project in VS2017, uses the binaries from OSGeo4W64, while our main program already uses our own compiled GDAL 2.2.3, and it works there as well.
> I had to change the paths in CMake to use our own build, after initial test.
>
> In CMake I turn off all that I can, and I would have liked to turn off even more. (WITH_GEOS, WITH_GDAL, WITH_LIBXML2, ...)
>
> The following binaries I copy from the OSGeo4W64 folder:
> Geos_c.dll, lbxml2.dll, libcurl.dll, iconv.dll
> xerces_c_3_1.dll we already have from GDAL, but this is also a dependency.
>
> So I can't give you an answer on if all of GDAL, or even PDAL will work with what I have done, but at least I can verify that it compiles and runs LasReader and LasWriter.
>

Every configuration option is extra maintenance overhead for the
project, and we are not going to add a bunch of options to make it
convenient to do stuff like this. We are not going to merge patches to
make it easier either. The benefit is tiny in comparison to the extra
effort it requires of the project. What reason do you have to bother
with PDAL at all if it is so much trouble? libLAS is still there...



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 528 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20180425/d9d6f15d/attachment.sig>