[lastools] Install serf/geo lookup CSVs when tools feature is used

[maredman]

Is your feature request related to a problem? Please describe.

When you build the lastools port with the tools feature, some exe's are copied to the installed/tools folder using the snippet below from the portfile.cmake.

if(BUILD_TOOLS)
    vcpkg_copy_tools(TOOL_NAMES las2las64 las2txt64 lascopcindex64 lasdiff64 lasindex64 lasinfo64 lasmerge64 lasprecision64 laszip64 txt2las64  AUTO_CLEAN)
endif()

I noticed when I was running las2las64.exe, that it prints out a warning because I'm using data with an uncommon projection, and it's trying to open serf/geo/pcs.csv to use as a lookup table, but the port doesn't install that CSV. The warning I get is: "cannot open 'pcs.csv' file. check for \LAStools\bin\serf\geo\pcs.csv file. download latest version."

You can see this message if you search this file in the LAStools repo: https://github.com/LAStools/LAStools/blob/b2f578b4f03c9016d519b319cd61c903a74cf744/src/geoprojectionconverter.cpp

Proposed solution

I'd like to add a line to the portfile.cmake to also copy the CSVs when the "tools" feature is used on the lastools port like:

    # Copy CSV files that are used as lookup tables by las2las.
    file(COPY ${SOURCE_PATH}/bin/serf/geo
         DESTINATION ${CURRENT_PACKAGES_DIR}/share/${PORT}/serf)

I haven't contributed to vcpkg before. Would this be suitable to submit for a PR?

Describe alternatives you've considered

No response

Additional context

No response

[dg0yt]

It might be possible to install the data. However:

• It is necessary to find the location which is actually used by the tool/lib.
  Did you verify your proposal? vcpkg moves tools to an unusual folder.
• The installed package should be relocatable. But for some build types the tool may not be able find it is own location (as a a base path). (The focus of vcpkg is libraries for development, not general app management.)

[maredman]

The lastools code expects the CSV files to be in a folder "/serf/geo" that is relative to the location of the running tool. This can be confirmed by looking at the link to the code I pasted in the initial issue description and searching open_geo_file. On Windows systems it uses GetModuleFilename to find the path of the lastool executable and on other systems it uses readlink("/proc/self/exe", path, MAX_GEO_PATH_LENGTH);.

I have a fork of vcpkg and I did verify (with the x64-windows triplet) that I can copy the CSV files into the installed port, and that the tool will run appropriately and access the CSVs when I copy them to my application's bin folder and have the CSVs in bin/serf/geo.

Since the CSVs need to be relative to the lastool path, I originally thought about copying the CSVs into the tools folder instead of the share folder, but then when I was reading about the vcpkg directory layout convention (https://learn.microsoft.com/en-us/vcpkg/reference/installation-tree-layout), it seemed like the CSVs should go in the share folder since they're configuration-independent files.

@dg0yt - thank you for taking a look at this! Does the above answer your questions?