pylon version detection #29
Description
we're trying to use pylon-cxx with Pylon 25.10 (released oct '25), but there are some naming inconsistencies between this latest version and the .so versions that the crate looks for, e.g. there are some _v1 suffixes or a different version (e.g. *3_5* instead of *3_1*) and we can get the crate to work by just making some symlinks with the name that build.rs expects but this does not seem like a sustainable long term solution.
example of linker error after running cargo build:
= note: /usr/bin/ld: cannot find -lNodeMapData_gcc_v3_1_Basler_pylon: No such file or directory
the corresponding .so in /opt/pylon/lib is libNodeMapData_gcc_v3_5_Basler_pylon_v1.so, where the name differs in some major/minor versions and suffixes. I was able to make a symlink with the expected name and it builds the way I expect. but making these symlinks is not ideal.
I'm wondering if it would be possible to have some sort of version detection so that these strings can be built more automatically, or if such a feature would be desirable. Thoughts?