CloudCompare forum

I am a beginner.
To add this plugin, I was asked to provide 3 paths:LASLIB_DEBUG_LIBRARY LASLIB_INCLUDE_DIR LASLIB_RELEASE_LIBRARY. However, the guide that I found in the documentation said I should fill liblas path in there. I think there are some differences between liblas and laslib. So what should I do to load las data?

By default, CloudCompare uses libLAS to open LAS files. But libLAS is somehow deprecated and can only load LAS 1.1 and 1.2 files.

We recently added the QLAS_FWF_IO plugin which is based on LASlib. LASlib is able to load 1.3 files, notably with FWF data (FWF = Full Wave Form). This is a work in progress, and FWF data can't actually be used for anything right now. Therefore the plugin is only useful if you need to load LAS 1.3 files.

In a near future, the aim is to remove the libLAS support and replace it by the QLAS_FWF_IO plugin (= LASlib).

If you really want to compile QLAS_FWF_IO then you will indeed have to supply the right path for LASlib files. With Visual 2012 and 2013, you can compile it with the https://github.com/cloudcompare/LAStools fork.

daniel wrote:By default, CloudCompare uses libLAS to open LAS files. But libLAS is somehow deprecated and can only load LAS 1.1 and 1.2 files.

We recently added the QLAS_FWF_IO plugin which is based on LASlib. LASlib is able to load 1.3 files, notably with FWF data (FWF = Full Wave Form). This is a work in progress, and FWF data can't actually be used for anything right now. Therefore the plugin is only useful if you need to load LAS 1.3 files.

In a near future, the aim is to remove the libLAS support and replace it by the QLAS_FWF_IO plugin (= LASlib).

If you really want to compile QLAS_FWF_IO then you will indeed have to supply the right path for LASlib files. With Visual 2012 and 2013, you can compile it with the https://github.com/cloudcompare/LAStools fork.

So what I should do is to compile LasTools and then provide include and lib path to cmake, right?

Yes. In fact you only need to compile LASlib (see the Visual 2012 and 2013 solution files in the corresponding folder).