Also, Apple recommends using -Os for optimization rather than -O3, so I'm making that switch. (Especially when O3 optimization can cause issues which are harder to catch when we don't have a good regression testing).
Le dimanche 30 novembre 2025 à 11:46:42 UTC+1, Guillaume DIDIER a écrit : > I have managed to get the OpenMP issue sorted out, however, my CMake > expertise isn't enough to get a super clean solution. > The built-in FindOpenMPMac.cmake seems rather outdated, which may be part > of the issue. > > Right now, I need to pass -fopenmp to compilers, but also > -L$REPOSITORY/lib -lomp to linker invocations, but I only managed to send > those flags to both compilation and link, which results in compiler > warnings. > > I'll finish updating the documentation in the scripts and then send in a > patch, which I expect you'll need to rework a bit to make the CMake part > cleaner. > > The up to date FindOpenMP instead had a larger set of output variables, > including a list of library to be linked, perhaps updating the CMakeLists / > CMakeModules to use this more recent version would help make this cleaner. > > By the way, once all of this is upstreamed, if I renew my lapsed Apple Dev > Subscription, would it be possible to upload code signed Hugin binaries to > the website ? > > Guillaume > > > Le samedi 22 novembre 2025 à 10:45:50 UTC+1, T. Modes a écrit : > >> Hi Guillaume, >> >> Guillaume DIDIER schrieb am Samstag, 22. November 2025 um 09:50:03 UTC+1: >> >> Here are the first two patches of the series, which concern the source >> code. >> >> thanks again. One I had to rework otherwise it broke compilation on my >> machine. >> The second one I commited. >> >> From a changeling perspective, should I increment the patch version in >> CMakeLists.txt and refer to this version when updating the file >> documentations ? >> >> Odd-numberd minor versions are considers development versions. For these >> the patch level is not used, instead the changeset hash is added to the >> version. >> Only for even-numbered minor versions the patch number can be used. >> Changes to the version should be done in separate changesets to make it >> easier to transplant the changes (cherrypick in git speech) between the >> branches. >> So at the current state this should not be necessary. >> >> Thomas >> > -- 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 visit https://groups.google.com/d/msgid/hugin-ptx/b0aacc39-f077-4f9a-a418-80a49ff65c41n%40googlegroups.com.
