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
Den lör 5 aug. 2023 00:[email protected] <[email protected]> skrev: > 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? > > On Wednesday, July 26, 2023 at 9:10:49 AM UTC-7 [email protected] wrote: > > 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 👌 > > Den ons 26 juli 2023 17:24T. Modes <[email protected]> skrev: > > [email protected] 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. > > -- > 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/4ed654a9-050e-4360-adc2-ffd3dae69011n%40googlegroups.com > <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 [email protected]. > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAHk3tqi6mk0COzwvCv_PH2NM%3DvBWiQrjfOKZKMMHO3Muhv2jNw%40mail.gmail.com.
