On Thu, 3 Mar 2022, 17:36 johnfine wrote: > > Are there options I should have used with CMake to get things to go to the > right place? Or is the place they went "right" and I should have done > something different with the other CMake to find things in that place. > > When I did a *make install* on the fork of libpano13, it put files in > /usr/local/lib64 > But the Fedora package for libpano13-devel puts those files in /usr/lib64 > The build for the fork of hugin finds the files where libpano13-devel put > them. >
It is normal for software that you have compiled yourself to be installed into /usr/local. This way you don't overwrite files installed by the distribution package manager in /usr - i.e. installing into /usr can make a big mess that isn't easy to clear up. The libpano13-devel rpm package only exists for you to compile and link to the libpano13 rpm package in /usr. Just uninstall it and your Hugin build will pick up your forked libpano13 headers in /usr/local/include You may also need to set LD_LIBRARY_PATH for your forked Hugin to use this library at runtime. -- Bruno > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAJV99ZjMk7ss5zj-35piP%2BOwyq-OKVWnt_BvzwxGgD0XE-c3MQ%40mail.gmail.com.
