Okay, I checked again: the feature you depend on is not part of Google Highway 1.0.3, which is the newest published version. Looks like it went in just a few days after the release. I will therefore not be able to package lux 1.1.5 until a Google Highway version with this feature has been released.
I cannot fix this as I'm not going to bundle a second copy of Highway just to build your package. We'll have to wait until a new Highway version is released. Please avoid depending on unreleased features in dependencies. Makes it much harder to actually use your software. Yours, Robert Clausecker Am Freitag, dem 10.02.2023 um 08:09 +0100 schrieb 'Kay F. Jahnke' via hugin and other free panoramic software: > Am 09.02.23 um 22:16 schrieb Robert Clausecker: > > > How is this information “deployed” if not by placing a file > > somewhere? > > CMake specifically asks for a file to be provided in the error > > message. > > Here is the list of files installed for the devel/highway package: > > > > https://cgit.freebsd.org/ports/tree/devel/highway/pkg-plist > > > > Where is this information deployed? If it is not there, where > > would it > > be if it was there? > > The list above does not contain all the files which should be > deployed > on the target machine. If I do a 'make install' on my machine with > hwy > master, it installs these files as well: > > -- Installing: /usr/local/lib/cmake/hwy/hwy-config-version.cmake > -- Installing: /usr/local/lib/cmake/hwy/hwy-config.cmake > -- Installing: /usr/local/lib/cmake/hwy/hwy-config- > relwithdebinfo.cmake > > This is what I mean by 'deploy'. If you like, I can send you the > files. > Maybe you can ask the maintainer of the highway port to look at the > matter - I suspect that these three files have to be added to the > list. > When they are present, CMake should find your highway install with > CONFIG mode, as it's done in may lux CMakeLists.txt > > > The default location stuff is too fragile. > > I agree, that's why I requested the addition of code to make highway > findable with CMake. I'd like to stick with CMake for configuration. > lux > 1.1.4 did rely on the default location, and the patch I proposed to > you > off-list yesterday evening would do just the same. Once the hwy port > is > updated, you can switch back to the unpatched version. I did not mean > to > propose a permanent solution, it's just to get you going with the > 1.1.5 > build if the finding-hwy issue can't be resolved otherwise. > > Kay > > > -- 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/7e116729acd4d37bef202aee231707ef1687ae31.camel%40gmail.com.
