Consolidate Mac build

[T. Modes]

Hello Mac builder,

currently there are at least 3 different build scripts for Hugin I'm aware.

https://bugs.launchpad.net/hugin/+bug/2028086 by p.w.wong

https://sourceforge.net/p/hugin/hugin/merge-requests/4/ by Erkan Ozgur Yilmaz

https://bitbucket.org/Dannephoto/hugin/src/master/ by Dudeck

Two of them wants now be merged with our default repository.

But each of them is different:

e.g. all are using different paths to the compiler:

CC="/opt/local/bin/clang" 

CXX="/opt/local/bin/clang++"

CC="/opt/homebrew/Cellar/llvm/16.0.1/bin/clang"

CXX="/opt/homebrew/Cellar/llvm/16.0.1/bin/clang++"

CC="/opt/homebrew/Cellar/llvm/16.0.3/bin/clang"
CXX="/opt/homebrew/Cellar/llvm/16.0.3/bin/clang++"

Just to name one of them.

We can't have different flavours of the build scripts in the main repository.

So please synchronize your efforts and reach an agreement on one! way for the main repository.

[dudek53]

Agree. I´d say either one of the homebrew compilers could be added as guideline. User has to manually add it anyway I think as brew install any particular clang isn´t in the script yet. Brew seems to replace versions regularly as well so maintaining version 16 will not be for long.

I´d stay out of port install of clang. The p.w.wong isn´t adressing apple silicon versions is he? Which is another can of worms. We should add an additional mac_intel folder as opposed to mac_arm64. I tested on both architectures and intel based scripts works pretty much as is right now  but arm64 is another ballpark.

All in all, my scripts builds on Erkans efforts and what I provide works without any additional changes to source code. Well, work with some workaround tricks but that is probably what we have to live with for now.

Erkan is missing install_name_tool part added in this script:

https://bitbucket.org/Dannephoto/hugin/src/master/mac/ExternalPrograms/scripts/boost.sh

Needed so it becomes standalone.

I reading this Erkan Ozgur Yilmaz. What´s your status in your version? If reading this we could check into a "release"?

[T. Modes]

dud...@gmail.com schrieb am Dienstag, 25. Juli 2023 um 23:09:10 UTC+2:

We should add an additional mac_intel folder as opposed to mac_arm64. I tested on both architectures and intel based scripts works pretty much as is right now  but arm64 is another ballpark.

This is the opposite I meant with consolidate. There are already a lot of scripts for mac alone. Duplicating them for different case is a no go (with only a minor differences). This becomes a maintenance nightmare.

All necessary things should be in one set of scripts. The architecture and/or compiler can then be chosen by a command line switch or an environment variable and then evaluated in the scripts.

[dudek53]

Yes, it should be a fully automated script solution. Getting a base for that should be fairly easy. It would probably require consolidate with the loose ends on the wiki page or other links recommending ports and what not which contradicts some of the sources from the scripts.

This all takes time. And honestly. Personally I cannot make hugin compile  without heavy digging solving strange conflicting behaviours. What is worse, I can't see why my solutions work either.

Best way to start off would be on a fairly vanilla Mac and start without different brew and port libs. That is not gonna happen on my end for a while. I will be at assistance if anyone wants to start the work 👌

--
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 hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/4ed654a9-050e-4360-adc2-ffd3dae69011n%40googlegroups.com.

[ph...@weballey.com]

I'm not sure of what to choose for the repo, since it appears that the orginal README.md has instructions for installing llvm via homebrew. I am using macports which uses a different set of compiler paths and didn't want to mess up my system with another package system, so I adjusted the CC and CXX to work with the what I had.

Maybe this can be resolved by updating to README.md to state that the CC and CXX paths need to be modified according to whether homebrew or macports is used to install llvm?

[dudek53]

Hi Weballey.

If you have a fully working environment based on macports I would like to test that over here. Are you compiling for Intel or arm64? Did you modify any of the sources or is everything working based on your macports sources? 

If possible share exact sources used etc.

Thanks

/D

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/9211be10-f7f9-4eb5-aba2-8e737d96c814n%40googlegroups.com.

[p.w.wong]

I am compiling for intel on MacOS 10.12.6 (Sierra) via the development
tools from macports. As far as I can tell no development libs from
macports are being linked in. Attached below is the diff patches to
the hugin sources that I used to build my dmg.

-phil

>> <https://groups.google.com/d/msgid/hugin-ptx/4ed654a9-050e-4360-adc2-ffd3dae69011n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .

>>
>> --
>> 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 hugin-ptx+...@googlegroups.com.
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/hugin-ptx/9211be10-f7f9-4eb5-aba2-8e737d96c814n%40googlegroups.com
>> <https://groups.google.com/d/msgid/hugin-ptx/9211be10-f7f9-4eb5-aba2-8e737d96c814n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .

>>
>
> --
> 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 hugin-ptx+...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/hugin-ptx/CAHk3tqi6mk0COzwvCv_PH2NM%3DvBWiQrjfOKZKMMHO3Muhv2jNw%40mail.gmail.com.



--

"Pretending that the all-but-inevitable is inconceivable doesn't
make it impossible."

Phillip W. Wong, PE (ph...@weballey.com)