Op di 2 mrt. 2021 om 11:43 schreef 'Kay F. Jahnke' via hugin and other free panoramic software <[email protected]>:
> > Thank you for confirmig a mac build! This is great, you're now only the > third person I know of who's succeeded in building pv on a mac. I don't > have a mac myself, so it's hard for me to code for it. Please note that > the mac branch has not yet been updated to contain my new code, I'll do > that soon-ish. Old macs are like old pcs, they won't have fast SIMD > units. I routinely build on an old IBM Thinkpad R60e with a core2 Duo, > to confirm that the code works on 32bit intel hardware with SSE only. It > works, but it takes forever... My desktop is a Haswell core-i5, which > has AVX2. This is where it starts being fun :D > > Since you're the one who's building hugin on the mac, maybe you can give > me a hint on how to write a 'port file' to provide a pv package for > macports? Is that hard? And is it hard to provide a package which users > can simply download from the app store? I proposed to bundle pv with > hugin, because it would make a good addition to the suite, what do you say? > > Kay > > I was not correct, or at least not clear enough, in my answer. I did take over from Ippei Ukai, but also mentioned I abandoned Mac in 2012/2013 or so. I simply never threw my 2008 macbook away. At that time I also maintained the macports build of hugin and enblend/enfuse, but that is now also long, long ago. But I will have a look at it. The current Hugin builders on Mac are Niklas Mischkulnig and Bob Campbell. All credits to them (not to me). I certainly do not have an Apple M1 and will not buy one either. I am a happy Linux user since 1993 (early adapter) and simply wandered off for a couple of years, both to Apple and Windows. Making a package for the MacOS app store is a different thing. You have to register as a developer at Apple. I did a complete rant some days ago about how I hate how Apple does things, but also realised at that time that I had registered around 2008, when I took over from Ippei. And yes, that still worked. - So, you have to register at Apple as a developer giving quite some info. - You have to offer your bundle to Apple where Apple checks for malware/Apple standards/"other things". That is actually a good thing, but will take time and sometimes your bundle is rejected while you know it is perfectly fine. I have a java app which I also packaged as a MacOS bundle. Apart from the fact that I won't release it via the apple store, it will not be accepted either as it is built outside Xcode thereby lacking some controls/standards (and Apple spyware?). With regard to bundling with Hugin: I agree with Thomas that where possible we should integrate. You already explained the big differences in code, so that might not be possible. I can't judge that as I'm not a C/C++ programmer. As it is all open source, it might still be possible to migrate/integrate it. And otherwise: could it be possible to call pv from hugin to run it as enblend replacement. Just like multiblend can be called from hugin (with a simpler command set) as enblend replacement? Also: panomatic was first an external tool and most of it is now integrated in cpfind. I hope we see the same for pv blending/fusing functionality if it really is an improvement. My personal point of view is to help where I can if "something" can mean an improvement for all of us. And if it is mature try to integrate it. Harry -- 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/CAGARPptLO9_GLJY8cQaumqPvSc0biNiiYg4t%3DUEaiPHKMK-cQg%40mail.gmail.com.
