arsf / lag

LiDAR Analysis GUI
GNU General Public License v2.0
22 stars 5 forks source link

Installation and Dependencies #15

Closed ada-foss closed 11 years ago

ada-foss commented 12 years ago

Determine whether LAG is making use of files exclusive to the RSG system, which would prevent any third parties from easily compiling and installing LAG. If that is the case, request these files upstream and/or provisionally provide them from LAG.

Principally, headers, library objects, and .pc files from laslib need to be checked. Also, any include statement that refers to anything like <laslib/someheader.hpp> may need to be changed to just <someheader.hpp>.

ada-foss commented 12 years ago

As now explained to me, LAG has been built hinging on a local and customised installation of laslib. This is based around a .pc file somewhere in $PKG_CONFIG_PATH, which points to (or should point to) the rest of the installation. However, no such file exists outside of PML.

ada-foss commented 12 years ago

The reason for this is that there exists no standard way of installing laslib on linux systems. The standard makefiles for laslib only provide a statically linkable object, unsuitable for any package management system. The sole maintainer of laslib however, is reluctant to make the necessary changes, citing that manual installation of laslib is beneficial to the LAStools project.

Internally, we use a customised Makefile, the distribution of which is currently being negotiated with laslib's maintainer.

ada-foss commented 12 years ago

A patch has been produced for the latest (29th August 2012) release of LASlib, which updates the Makefiles to mimic a propper build and installation process, in a crude way. Is being tested now.

ada-foss commented 11 years ago

Issue was neglected for a while, so LASlib was updated to a later version (27th November 2012) and, after brief testing, was bundled into the testing branch. For the time being, this will serve as the working solution.

When/if LASlib changes its build process, this will need to be updated. This also adds the responsibility of maintaining the patched build process for LASlib. Should be done periodically to avoid headaches updating and maintaining radically different versions of LASlib.