Hi! I changed to private repo but I changed it back to open again. Should be downloadable again. Different approach. I added latest sources and removed my hack "fix", then added Erkans changes in *mac* folder. That was it. I then successfully built the hugin dmg package here: *Download:* https://bitbucket.org/Dannephoto/hugin/downloads/Hugin-2022.1.0_arm64.dmg
*Commit:* https://bitbucket.org/Dannephoto/hugin/commits/8e1961c3033805eff48fdfe760378d4277b3266b To be clear. I share for people to test on apple silicon architecture(M1,M2 etc). It is way faster than using rosetta-based intel version. Personally I only use align_image_stack and enfuse so I can´t tell how things will work in the gui. Would be nice to get some feedback here. Sharing changes and code. I do not favor git. Bitbucket ran mercurial before but was removed a couple of years ago. Too bad. I like hg. With that said I do respect open source gpl regulation telling us to publish changes and code along shared builds. At this stage I don´t expect things to be pushed into main. More work needs to be done for this. But meanwhile, nothing wrong in sharing a builds for testing. lördag 6 maj 2023 kl. 00:04:23 UTC+2 skrev Donald Johnston: > After having to create an Atlassian account to login and access bitbucket, > I get the error message "You do not have access to this repository.” > Is there a less intrusive way to access this download? > > Don J. > > On May 5, 2023, at 3:10 AM, dudek53 <dud...@gmail.com> wrote: > > *Hugin arm64 build here(Standalone):* > https://bitbucket.org/Dannephoto/hugin/downloads/Hugin-2022.1.0_arm64.dmg > > Please test and report if it works or not(Mac M1 or M2 arm64) > > Make sure to run this in terminal before starting the app: > *xattr -cr /Applications/Hugin* > Hit enter > > > Some progress around building a standalone arm64 package. Following Erkans > changes and also adding a change in boost.sh script tha last libs for hugin > to become fully stand alone is handled at the bottom of *boost.sh*. > atomic lib had no prefixed path and libboost_system.dylib cried about where > atomic lib were to be found. All fixed now. > > if [ -f "$REPOSITORYDIR/lib/libboost_atomic.dylib" ]; then > install_name_tool -id "$REPOSITORYDIR/lib/libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_atomic.dylib"; > install_name_tool -change "libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_atomic.dylib"; > fi > > if [ -f "$REPOSITORYDIR/lib/libboost_filesystem.dylib" ]; then > install_name_tool -id "$REPOSITORYDIR/lib/libboost_filesystem.dylib" > "$REPOSITORYDIR/lib/libboost_filesystem.dylib"; > install_name_tool -change "libboost_system.dylib" > "$REPOSITORYDIR/lib/libboost_system.dylib" > "$REPOSITORYDIR/lib/libboost_filesystem.dylib"; > install_name_tool -change "libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_filesystem.dylib" > fi > > if [ -f "$REPOSITORYDIR/lib/libboost_system.dylib" ]; then > install_name_tool -id "$REPOSITORYDIR/lib/libboost_system.dylib" > "$REPOSITORYDIR/lib/libboost_system.dylib"; > fi > > if [ -f "$REPOSITORYDIR/lib/libboost_atomic.dylib" ]; then > install_name_tool -id "$REPOSITORYDIR/lib/libboost_atomic.dylib" > "$REPOSITORYDIR/lib/libboost_atomic.dylib"; > fi > > > On Thu, Apr 27, 2023 at 9:26 PM Gunter Königsmann <gunter.ko...@gmail.com> > wrote: > >> One message of this thread mentioned C++ complains about using a private >> method of wxString. That error message normally means that a function >> expects totally different types of arguments than it gets from the current >> code. >> >> If you allow the system to automatically convert everything to wxString >> and wxString to everything else without that causing an error you can call >> all versions of all functions with all types of arguments in any order >> without causing any error any more. But calling that function with those >> arguments still won't make any sense.p >> > > -- > 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/CAHk3tqi%3DXdZ%2Be3FffqynwMiixrhDp5hkqVpQnNvkQVkypRHwbQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/hugin-ptx/CAHk3tqi%3DXdZ%2Be3FffqynwMiixrhDp5hkqVpQnNvkQVkypRHwbQ%40mail.gmail.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/8ad0fd5e-cc68-4cb9-80cd-6fd3d5f776efn%40googlegroups.com.
