Mac Build

[Niklas Mischkulnig]

Why hasn't there been a Mac build on sourceforge for over one year (there isn't a windows build for the 2016.0.0 yet)?

[Carlos Eduardo G. Carvalho (Cartola)]

Probably there is no volunteer with enough skills and/or time and/or the platforms to do the job on those platforms. Could you help?

Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/

2016-04-01 16:55 GMT-03:00 Niklas Mischkulnig <nik...@mischkulnig.de>:

Why hasn't there been a Mac build on sourceforge for over one year (there isn't a windows build for the 2016.0.0 yet)?

--
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/edf3037d-062a-49f6-a0c2-8269f1a17d73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steve]

Yea it would be great to have a build of this.. 

[Niklas Mischkulnig]

I am working on it

[Carl von Einem]

Hi Niklas,

the panotools wiki has an article about building a bundle for OS X:

<http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode>

Maybe this is of help for you. It would be great to add what's needed
for a proper workflow on your version of OS X.

Thanks,
Carl

Niklas Mischkulnig wrote on 06.04.16 21:33:

[David Haberthür]

Ciao Niklas

> I am working on it

That’s great news, I never managed to successfully build it on my Mac.
I would be very grateful for an up to date build for OS X.

Habi

[Niklas Mischkulnig]

I compiled it successfully using cmake and homebrew's libraries, but building the external programs (http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode#Building_the_.22External_Programs.22), i.e. boost, doesn't really work ( for example: sh: g++-4.2: command not found )

Maybe there is someone who can help out.

[Carlos Eduardo G. Carvalho (Cartola)]

I don't have a Mac, but have worked giving support to a server a long time ago. There is a project called FINK that makes opensource packages for Mac. It is a place where you will maybe find a gcc/g++ to install on Mac.

http://www.finkproject.org/

Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/

--

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/ccfbe1c7-9f36-4dbd-bfce-f6a4d566fbdc%40googlegroups.com.

[Niklas Mischkulnig]

I have gcc-5 installed via homebrew(similar to fink), how can I set the script to use that? CC=gcc-5 CXX=g++-5 ../../scripts/boost.sh doesn't do anything

[Niklas Mischkulnig]

Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to feeling that boost isn't really built,  ## Now building architecture x86_64 ## is printed out, and nearly immediately after that mv: rename ./stage-x86_64/lib/libboost_thread.dylib to ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . That should be the compiled output boost library, right?

[T. Modes]

Am Samstag, 9. April 2016 11:11:54 UTC+2 schrieb Niklas Mischkulnig:

Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to feeling that boost isn't really built,  ## Now building architecture x86_64 ## is printed out, and nearly immediately after that mv: rename ./stage-x86_64/lib/libboost_thread.dylib to ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . That should be the compiled output boost library, right?

These Mac scripts needs probably some tweaking. Since they were used last some dependencies have changes.
From boost Hugins needs now only boost::filesystem (instead of boost::thread we are using std::thread)
In build-all.sh there are references to glib, lensfun, make, tclap, liblcms which are not needed anymore (maybe also libffi - I don't know which lib is using it).
So this needs also some more work.

[Niklas Mischkulnig]

I got most of the required deps compiled, but enblend still resists:

In file included from enblend.cc:147:

In file included from ./common.h:39:

In file included from /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/lambda.hpp:23:

/Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/detail/operator_return_type_traits.hpp:835:65: error: reference to 'map' is ambiguous

struct plain_return_type_2<other_action<subscript_action>, std::map<Key, T, Cmp, Allocator>, B> {

                                                           ~~~~~^

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/map:830:29: note: candidate found by name lookup is 'std::__1::map'

class _LIBCPP_TYPE_VIS_ONLY map

                            ^

/Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/detail/container_fwd.hpp:87:73: note: candidate found by name lookup is 'std::map'

    template <class Key, class T, class Compare, class Allocator> class map;

                                                                        ^ 

[Niklas Mischkulnig]

Anyone an idea?

Here is the full output: https://gist.github.com/mischnic/a40fc98594af70256e95559112fe87ef

[Niklas Mischkulnig]

Hello again, 

I copied the include, bin and lib files from the homebrew packages, but now it's Xcode:

When compiling the "vigra_impex Framework", this is the error;

no such file or directory: '/Users/niklas/development/test/src/foreign/vigra/vigra_impex/bmp.cxx'

The whole vigra folder is missing (was removed in 2011 http://hg.code.sf.net/p/hugin/hugin/rev/9e26ccb0d3d0 ). Does someone know why there is still something in the XCode project? Downloading the source gives the errors on the screenshot. 

The whole mac thing seems to be really outdated.

[Carlos Eduardo G. Carvalho (Cartola)]

Hi,

congrats on your effort to port to Mac! I've made the first Hugin port to FreeBSD in 2004 and now Greg Lehey maintains it. It can be a hard work.

From the Hugin FreeBSD ports page I've clicked in the vigra dependency and then on its Long description to reach the Vigra page, where you can see some binaries available to Mac. Maybe it will suppress the need to compile it as a dependency.

I've mentioned the FreeBSD ports page as another alternative to search for the dependencies in a place where they're all mapped already.

Good luck,

Carlos E G Carvalho (Cartola)
http://cartola.org/360
http://www.panoforum.com.br/

--

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/1079014f-8c6c-43b0-a780-45a3d4671ba1%40googlegroups.com.

[Sukima]

So how can us mac users help with this endeavor? Right now I'm using a VirtualBox VM of Ubuntu just to move from 2014 to 2015 (what apt-get gives you on Ubuntu 15).

[Niklas Mischkulnig]

Here is a (hopefully working) build (version 2016) . Please test it and tell me if something crashes (there might still be a wrong dylib install path lurking in a dark corner :D ). 

https://www.dropbox.com/s/oi6etuyobwkxwbb/Hugin.zip?dl=1

[Donald Johnston]

I downloaded the zip file, unpacked it, renamed the folder to hugin2016 and moved it to the application directory.

Trying to start it I got the message about “can’t run it because of unknown developer”; in security settings clicking on the “run anyway” didn’t help so I changed the setting to “allow apps from anywhere”.

When hugin started both windows opened (panorama stitcher and preview).

I was then able to turn off the “allow apps from anywhere” and hugin starts okay.

I received the following error message when I loaded a number of different jpeg images from my camera and cell phone (even after rebooting and renaming the directory back to hugin, and moving the hugin app to the application directory).

Could not decode image:

/Users/me/Pictures/0ShadeBW.jpg

Abort

When I tried loading a tif file it opened the image and gave the error:

Read error at scanline 0; got 3212 bytes, expected 3213 (in module "TIFFFillStrip")

When I clicked on Okay hugin crashed.

Another tif file crashed hugin directly.

Back to hugin 2014 and all the files load okay.

--
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/b54aec89-34a4-4cbd-a43e-5f7722dfb213%40googlegroups.com.

[Donald Johnston]

Also … thanks Niklas for doing this work for the Mac users!!!!

On Apr 17, 2016, at 2:09 PM, Niklas Mischkulnig <nik...@mischkulnig.de> wrote:

[AKS-Gmail-IMAP]

Thank you Niklas. Here are the console messages for Test A - attempting to open an existing pto, which results in Hugin vanishing, and Test B - attempting to add a jpg which Hugin reports as an unsupported image file format. Both tests seem to report the same console messages. When looking into the Hugin package I do not see libxpc.dylib. Perhaps this is a clue. I do not see libxpc.dylib in previous a Hugin. 

Test A:

4/17/16 9:54:55.120 PM Hugin[8124]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

Call location:

4/17/16 9:54:55.120 PM Hugin[8124]: 0   CarbonCore                          0x00007fff933f96df ___Gestalt_SystemVersion_block_invoke + 113

4/17/16 9:54:55.120 PM Hugin[8124]: 1   libdispatch.dylib                   0x00007fff872f240b _dispatch_client_callout + 8

4/17/16 9:54:55.120 PM Hugin[8124]: 2   libdispatch.dylib                   0x00007fff872f2303 dispatch_once_f + 67

4/17/16 9:54:55.120 PM Hugin[8124]: 3   CarbonCore                          0x00007fff93385fbc _Gestalt_SystemVersion + 987

4/17/16 9:54:55.120 PM Hugin[8124]: 4   CarbonCore                          0x00007fff933857d0 Gestalt + 139

4/17/16 9:54:55.120 PM Hugin[8124]: 5   libwx_osx_cocoau-3.0.0.2.0.dylib    0x000000010e811b8f _Z19UMAGetSystemVersionv + 31

4/17/16 9:54:55.120 PM Hugin[8124]: 6   libwx_osx_cocoau-3.0.0.2.0.dylib    0x000000010e85e374 _ZNK8wxWindow21MacHasScrollBarCornerEv + 228

4/17/16 9:55:00.542 PM Hugin[8124]: assertion failed: 15E65: libxpc.dylib + 78986 [2CC7CF36-66D4-301B-A6D8-EBAE7405B008]: 0x89

Test B:

4/17/16 10:01:08.735 PM Hugin[8161]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.4 instead of 10.11.4. This is not a bug in Gestalt -- it is a documented limitation. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.

Call location:

4/17/16 10:01:08.735 PM Hugin[8161]: 0   CarbonCore                          0x00007fff933f96df ___Gestalt_SystemVersion_block_invoke + 113

4/17/16 10:01:08.735 PM Hugin[8161]: 1   libdispatch.dylib                   0x00007fff872f240b _dispatch_client_callout + 8

4/17/16 10:01:08.735 PM Hugin[8161]: 2   libdispatch.dylib                   0x00007fff872f2303 dispatch_once_f + 67

4/17/16 10:01:08.735 PM Hugin[8161]: 3   CarbonCore                          0x00007fff93385fbc _Gestalt_SystemVersion + 987

4/17/16 10:01:08.735 PM Hugin[8161]: 4   CarbonCore                          0x00007fff933857d0 Gestalt + 139

4/17/16 10:01:08.735 PM Hugin[8161]: 5   libwx_osx_cocoau-3.0.0.2.0.dylib    0x0000000110183b8f _Z19UMAGetSystemVersionv + 31

4/17/16 10:01:08.735 PM Hugin[8161]: 6   libwx_osx_cocoau-3.0.0.2.0.dylib    0x00000001101d0374 _ZNK8wxWindow21MacHasScrollBarCornerEv + 228

4/17/16 10:01:14.976 PM Hugin[8161]: assertion failed: 15E65: libxpc.dylib + 78986 [2CC7CF36-66D4-301B-A6D8-EBAE7405B008]: 0x89

Thank you for taking this on.

Allan

[Niklas Mischkulnig]

No, that is a different problem to be solved by the wxWidgets developers.

First of all, thank you all for your quick responses and will to test.

Here is a new build: 

At least on my machine, I had to go into the Hugin.app settings, under programs and set alternative enblend/enfuse executables to ./enblend and ./enfuse to make PTBatcherGui work.  

https://www.dropbox.com/s/oi6etuyobwkxwbb/Hugin.zip?dl=1 (still the same link)

Changes:

1. The vigra library wasn't compiled with png, tiff or jpeg support, thus the decode-errors.

2. There were some missing binaries in Hugin.app, making auto-controlpoint-finding fail.

Niklas

[Sukima]

So what changes to the source were needed to get the Mac version to compile? Do you have plans to send a patch to the core team? Or at least a patch others can apply? The more devs who can compile the more options there are to upkeep the Official mac build and / or mirror them.

[Sukima]

Also, Thank you for this! It was far more then I could do. I see Xcode and start confusing my mouse with my keyboard (IDEs make coding so much harder IMHO). You rock BTW!

[Niklas Mischkulnig]

https://trac.macports.org/attachment/ticket/41463/patch-src-hugin1-icpfind-AutoCtrlPointCreator.cpp.diff

(Discussion here: https://trac.macports.org/ticket/41463)

(I am quite certain that) this is the only change to Hugin's own source code to make it compile with clang (I wasn't able to compile it using gcc, that caused even more problems). 

The (three ?) other changes were made to libtiff, gettext and wxWidgets.

Maybe there is someone who can tell me exactly what program needs which libraries (especially which boost library) and binaries(like cpfind, celeste, ...)  to shrink down the application sizes (currently 2* ~80mb and 1* ~50mb) ?

[Niklas Mischkulnig]

Thank you!

I hate Xcode as well and only learned how it worked along the way. Is there a way to compile Hugin using (c)make like the standard version which relies on libraries in /usr/local/ ?

[Jan Dubiec]

On 2016-04-18 14:40, Niklas Mischkulnig wrote:
[...]

> Maybe there is someone who can tell me exactly what program needs which
> libraries (especially which boost library) and binaries(like cpfind,
> celeste, ...) to shrink down the application sizes (currently 2* ~80mb
> and 1* ~50mb) ?

I don't know Macs but I'm quite sure that there is strip utility
(https://en.wikipedia.org/wiki/Strip_%28Unix%29) for Macs.

If you want to know about dependencies, read about CMake's --graphviz
option. It allows you to generate graphs like this:
* for the whole project –
https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
* for the whole project with external dependencies –
https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
* for a module (hugin in this case) –
https://www.dropbox.com/s/bfsz6byb86o2l89/HuginHg.hugin.pdf?dl=0
* for a module with external dependencies –
https://www.dropbox.com/s/7h1yauyooqo0ggj/HuginHg.hugin-ext.pdf?dl=0.

/J.D.

[Bill Brody]

I just downloaded the 2016 build and everything appears to work well on my MacBook Pro OS X 10.10.5 from creating a new panorama to opening a project file from the 2014 version. Thank you so very much. Compiling Hugin for a Mac is beyond my skill set and more importantly beyond my patience.
Eclipse is an alternative development environment. You might like it more than Xcode.

[Harry van der Wolf]

The fact the mac bundles are that big is due to the "bundle all dependencies" inside the app. That gives a lot of redundancy in the apps. That is already for years and years a fact and as long as Apple doesn't change their policy it will stay that way.

When compiling with XCode this strip functionality is automatically executed but results in about 10% size reduction. But my information is going years back.

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 hugin-ptx+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5714F841.2020009%40onet.pl.

[Niklas Mischkulnig]

The main duplicate and large part are the dylibs under Hugin.app/Libraries/. These could be in a folder alongside Hugin.app, PTBatchGui.app and calibratelensgui.app, reducing the total filesize from 231 mb to 231-(2*35)=180mb. Putting the Resources/xrc folder there as well would shave off another 15 mb (resulting in 165mb).

Is it worth the effort?

Niklas

[Harry van der Wolf]

In the time that I built the bundles I once build the Hugin.app as a full bundle and made symlinks to all redundant libraries in both other apps. That decreased the size of the apps indeed but it required all thee apps to be in the same folder (which as such is quite logical).

However, this build scenario made the compilation even harder and even though the 3 apps are a big chunk of data: What is 180 MB even on a (small) 128 GB solid state disk. Leave alone on a 750+ GB disk.

At that time I simply wanted to try, but it wasn't worth all the hassle.

Besides: If a user wants it differently then he/she can buid it himself/herself.

Note that I have left OSX about 2½ years ago. 

I think you did an awesome job in building the new 2016 version for Mac. If enough users have tested the builds I would suggest to upload them to sourceforge where the other older bundles reside as well.

If you get too many downloads on your dropbox account it will be completely blocked for others to download. Only you yourself can use it then.

I experienced that myself with another build (not for mac). I used dropbox mainly to share things with my family. Even that was no longer possible. With 180 MB bundles this might go faster then you expect.

Harry

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/a7cc3b06-7e9c-4ecd-8d65-866a67480afe%40googlegroups.com.

[Niklas Mischkulnig]

Thank you for your tips! 

Here is a new link (just being cautious):

https://drive.google.com/uc?export=download&id=0B_seRjFxxDleU1YtQ1Zka1BXM2c

[Donald Johnston]

I loaded in two images and when I ran “2. Align" in the Assistant the checkpoint finder ran and then gave the following error; the preview window shows that the images aren’t aligned:

Warning The assistant did not complete successfully. Please check the resulting project file.

I then ran “2. Align” again and it worked … images are now aligned.

This is the pro file from the last test before I did the second Align.

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1200 v95  E12.8258 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin  cropFactor=1
i w7360 h4912 f0 v54.4166340882032 Ra0 Rb0 Rc0 Rd0 Re0 Eev12.8257537576407 Er1 Eb1 r0 p0 y-20.4062377830762 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0  Vm5 n"_DSC5269_DxO.jpg"
#-hugin  cropFactor=1
i w7360 h4912 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev12.8257537576407 Er1 Eb1 r0 p0 y20.4062377830762 TrX0 TrY0 TrZ0 Tpy0 Tpp0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0  Vm5 n"_DSC5270_DxO.jpg"


# specify variables that should be optimized
v Ra0
v Rb0
v Rc0
v Rd0
v Re0
v Vb0
v Vc0
v Vd0
v Eev1
v r1
v p1
v y1
v


# control points
c n0 N1 x3696.05966609671 y1825.30402029857 X419.664144377767 Y1831.3791601006 t0
c n0 N1 x4005.85096352495 y2776.69482726997 X801.844803925653 Y2863.91897705157 t0
c n0 N1 x3991.1244493935 y3225.0397065645 X790.797643119916 Y3347.46771351515 t0
c n0 N1 x4162.15742898987 y3600.03572867001 X993.580960490438 Y3731.96143608346 t0
c n0 N1 x4852.77490011735 y1839.81710109775 X1720.83845723934 Y1877.58132796898 t0
c n0 N1 x4748.07475131188 y2719.70018168613 X1620.00190890946 Y2778.88928851275 t0
c n0 N1 x4618.61465209862 y3086.02970255621 X1490.81382660912 Y3162.65766912122 t0
c n0 N1 x4212.84238489859 y3930.37235253843 X1054.84347636389 Y4078.14975286439 t0
c n0 N1 x4821.82879546977 y4158.19332481704 X1718.27641164762 Y4249.65408313429 t0
c n0 N1 x5402.02653987854 y1879.92170584667 X2278.58493077799 Y1929.86733045436 t0
c n0 N1 x5557.51399906224 y2775.85797813578 X2441.98215452036 Y2812.3667458965 t0
c n0 N1 x5146.70921097711 y3385.54422255936 X2044.17753552017 Y3437.46458359526 t0
c n0 N1 x5182.00481127046 y3944.03424354976 X2085.82704156097 Y3994.98314388063 t0
c n0 N1 x5256.95626452093 y4336.25820912707 X2165.4512415092 Y4378.35735832791 t0
c n0 N1 x6130.95821212135 y1889.27724162455 X2966.03387872573 Y1954.49506406677 t0
c n0 N1 x5960.49427513845 y2741.70674625863 X2822.56590170796 Y2768.23782579663 t0
c n0 N1 x6201.46814991463 y3356.27333275119 X3049.46863441504 Y3344.15421521082 t0
c n0 N1 x6101.68454244844 y3588.9962172638 X2962.15904543771 Y3571.82304696196 t0
c n0 N1 x5703.08666662653 y4141.71600741062 X2596.16205631548 Y4137.81717756846 t0
c n0 N1 x6837.40354874217 y1976.50238689428 X3583.61627305083 Y2047.60050923055 t0
c n0 N1 x6511.00218893558 y2857.26345072051 X3316.35476105764 Y2861.82108139742 t0
c n0 N1 x6724.56821021902 y3098.83778794662 X3502.465885435 Y3077.79310778096 t0

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions 
#hugin_enfuseOptions 
#hugin_hdrmergeOptions -m avg -c
#hugin_verdandiOptions 
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRStacks false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType tif
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 90
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW
#hugin_outputStacksMinOverlap 0.7
#hugin_outputLayersExposureDiff 0.5
#hugin_optimizerMasterSwitch 1
#hugin_optimizerPhotoMasterSwitch 21

[Niklas Mischkulnig]

Did you use the most recent build, redownload? You should have seen a log window before the  "Warning The assistant did not complete succ.... " comes up. Unfortunately, the error message is at the end of that window, which goes after instantly (to someone who can change that: please do! Save the whole log into the same folder as the project file).  Start up Quicktime, create a new screen recording (ctrl + cmd + n and the red button), make the alignment fail again, stop the recording. Then look through the video and search the last error message before the window closes. 

[Donald Johnston]

Another error. I loaded an old project with 18 images that requires exposure fusion and stitching. The project loaded fine, the preview window show the aligned preview as it should be.  When I ran the stitcher it goes for a while and then fails with the following Status Report. I then reloaded the original images as a new project, aligned the images, and got the same failure.

============================================
Stitching panorama…
============================================

Platform: Mac OS X (Darwin 15.4.0 x86_64)
Version: 2016.1.0 built by Niklas Mischkulnig
Working directory: /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
Output prefix: IMG_0809 - IMG_0826Test2016

Blender: Unknown blender (enblend —version failed)
Exposure fusion: Unknown exposure fusion (enfuse —version failed)
ExifTool: FAILED

Number of active images: 18
Output exposure value: 15.9
Canvas size: 7298x2179
ROI: (108, 190) - (7237, 1174) 
FOV: 144x43
Projection: Equirectangular(2)
Using GPU for remapping: false

Panorama Outputs:
* Exposure fused from stacks

First input image
Number: 0
Filename: /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
Size: 2592x1728
Projection: Normal (rectilinear)
Response type: custom (EMoR)
HFOV: 34
Exposure value: 16.0


Remapping LDR images without exposure correction…
Multiple images output
loading IMG_0809.JPG
remapping IMG_0809.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0000.tif
loading IMG_0810.JPG
remapping IMG_0810.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
loading IMG_0811.JPG
remapping IMG_0811.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
loading IMG_0812.JPG
remapping IMG_0812.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
loading IMG_0813.JPG
remapping IMG_0813.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
loading IMG_0814.JPG
remapping IMG_0814.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
loading IMG_0815.JPG
remapping IMG_0815.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
loading IMG_0816.JPG
remapping IMG_0816.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
loading IMG_0817.JPG
remapping IMG_0817.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0008.tif
loading IMG_0818.JPG
remapping IMG_0818.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0009.tif
loading IMG_0819.JPG
remapping IMG_0819.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0010.tif
loading IMG_0820.JPG
remapping IMG_0820.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0011.tif
loading IMG_0821.JPG
remapping IMG_0821.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0012.tif
loading IMG_0822.JPG
remapping IMG_0822.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0013.tif
loading IMG_0823.JPG
remapping IMG_0823.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0014.tif
loading IMG_0824.JPG
remapping IMG_0824.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0015.tif
loading IMG_0825.JPG
remapping IMG_0825.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0016.tif
loading IMG_0826.JPG
remapping IMG_0826.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0017.tif

On Apr 18, 2016, at 11:26 AM, Niklas Mischkulnig <nik...@mischkulnig.de> wrote:

[Donald Johnston]

To add to this error information I did two additional tests with these images.

1. the first three images so it was an exposure stack. All fine until “Create panorama…”; same failure.

Blender: Unknown blender (enblend —version failed)

Exposure fusion: Unknown exposure fusion (enfuse —version failed)
ExifTool: FAILED

2. images 1, 4, and 7; so no exposure stack just a three image pano … same failure (except no enfuse failed).

Blender: Unknown blender (enblend —version failed)

ExifTool: FAILED

--
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/F79DD5A3-28FE-423A-B4BE-7E4024D17CEC%40accesscomm.ca.

[AKS-Gmail-IMAP]

This Hugin goes into spinning ball heaven in the Fast Panorama preview when touching in the Overview or main image when the Layout tab is selected. At that point it needs to be force quit. The point at which the spinning ball occurs appears to be at the same moment a correctly functioning Hugin would try to highlight what it thinks is a layout connection to identify.

In the Fast Panorama preview (preview ought to be capitalized here, right?), in the Projection mode, changing the projection type in its control snaps back to its original setting, unless you first change the Guides: type. The projection type does change and update after changing the Guides: setting, even also when setting it back to what it was.

These bugs seem familiar for some reason.

Allan

On Apr 17, 2016, at 3:09 PM, Niklas Mischkulnig <nik...@mischkulnig.de> wrote:

[Niklas Mischkulnig]

I had to go into the Hugin.app settings, under programs and set alternative enblend/enfuse executables to ./enblend and ./enfuse to make PTBatcherGui work.

You received this message because you are subscribed to a topic in the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hugin-ptx/Rz-LY9isDIs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6064FADF-81DD-4C90-900C-5E993D3A8B34%40accesscomm.ca.

[Harry van der Wolf]

With regard to the exiftool error: In the previous builds exiftool was also incorporated in the bundles. I assume that was forgotten for this bundle.

W.r.t. enblend and enfuse: Please check whether they are inside the bundles. If not: then it is the same error as above. If the enblend --version command works it means that enblend is available.

If you have an external enfuse and enblend you can point hugin towards these versions.

Harry

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CACd%3DvwA_8_UKV%2BmCdd8f0BxOatuUOmXR9hshV2qcQ9gPD7Spdg%40mail.gmail.com.

[Niklas Mischkulnig]

Exiftool and enblend/enfuse are in there: (both PTBatcherGUI.app and Hugin.app), see the attachments

when enblend is called, it is exspected to be somewhere in PATH, i.e. /usr/local/bin; ./enblend , however,  searches in the current dir, next to Hugin

You can try that out in bash.  That is why I set enblend and enfuse to alternative paths, since I couldn't find a path to enblend and enfuse in the src. Or could Hugin change PATH ?

[Harry van der Wolf]

The problem in this case is that macos is not the working directory, but the directory one higher.

The directory that contains pkginfo and Info.plist is the working folder.

I'm not sure (as I can not test myself) that a path like ./MacOS/enblend might work

Harry

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/a8a3ac3e-eaa6-44b7-b969-df6b1c5cf9b4%40googlegroups.com.

[Niklas Mischkulnig]

First I thought the following: 

I looked through the code and noticed that PTBatcherGui first tries to use the "alternative path" and then falls back to the bundled version of enblend. Now I can't get it to fail to find enblend. There is no other reason for not finding enblend apart from it not being bundled in MacOS/ .

But then: #if defined __WXMAC__ && defined MAC_SELF_CONTAINED_BUNDLE ; sure __WXMAC__ is set but MAC_SELF_CONTAINED_BUNDLE isn't (doing that creates a whole lot more compile errors).  That means that it searches in path.

What's going on, especially with ExifTool, the code, which searches it, is quite complex?

[dgjohnston]

Yes thanks Niklas that was the fix. I remember seeing that in your first link but when I used the second link it totally went out of mine. 

Thanks again also for doing all this work. I've tested large pto files that I have and all seems to be working now. 

Don Johnston

Sent from my Samsung device

[Sukima]

The spinning ball of heaven is happening to me on el capitain with Hugin version 2014 so it is possible there are Mac bugs long lived that are not unique to this new build.

For reference to reproduce open Hugin and set interface to expert. Then select mask. Click crop. Click mask. Force quit cause it should have frozen.

Again this with version 2014 downloaded from sourceforge. I will try this new build tomorrow and see if 2016 fixes it.

[David Haberthür]

Dear Niklas
Thanks for providing us Mac users with a fresh build.
Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) with it.
I can open a panorama, but when I want to see the OpenGL preview, Hugin instantly crashes hug

Unfortunately, I cannot get anything useful from the Console-App which would hint at the bug I’m hitting.
The only thing I get in the console is
—
25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: (net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal code: 1
—

When I work with the ‘old’ preview window I can stitch some of my recent panoramas without problems.
Will try to make a new one for testing soon.
Habi

> On 13 Apr 2016, at 17:37, Niklas Mischkulnig <nik...@mischkulnig.de> wrote:
>
> Hello again,
>
>
>
> I copied the include, bin and lib files from the homebrew packages, but now it's Xcode:
>
> When compiling the "vigra_impex Framework", this is the error;
>
>
> no such file or directory: '/Users/niklas/development/test/src/foreign/vigra/vigra_impex/bmp.cxx'
>
> The whole vigra folder is missing (was removed in 2011 http://hg.code.sf.net/p/hugin/hugin/rev/9e26ccb0d3d0 ). Does someone know why there is still something in the XCode project? Downloading the source gives the errors on the screenshot.
>
>
>
> The whole mac thing seems to be really outdated.
>
>
> Am Sonntag, 10. April 2016 17:29:12 UTC+2 schrieb Niklas Mischkulnig:
> Anyone an idea?
>
> Here is the full output: https://gist.github.com/mischnic/a40fc98594af70256e95559112fe87ef
>
> Am Samstag, 9. April 2016 23:57:54 UTC+2 schrieb Niklas Mischkulnig:
> I got most of the required deps compiled, but enblend still resists:
>
> In file included from enblend.cc:147:
> In file included from ./common.h:39:
> In file included from /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/lambda.hpp:23:
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/detail/operator_return_type_traits.hpp:835:65: error: reference to 'map' is ambiguous
> struct plain_return_type_2<other_action<subscript_action>, std::map<Key, T, Cmp, Allocator>, B> {
> ~~~~~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/map:830:29: note: candidate found by name lookup is 'std::__1::map'
> class _LIBCPP_TYPE_VIS_ONLY map
> ^
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/detail/container_fwd.hpp:87:73: note: candidate found by name lookup is 'std::map'
> template <class Key, class T, class Compare, class Allocator> class map;
> ^
>
>
> Am Samstag, 9. April 2016 16:19:55 UTC+2 schrieb T. Modes:
>
> Am Samstag, 9. April 2016 11:11:54 UTC+2 schrieb Niklas Mischkulnig:
> Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to feeling that boost isn't really built, ## Now building architecture x86_64 ## is printed out, and nearly immediately after that mv: rename ./stage-x86_64/lib/libboost_thread.dylib to ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . That should be the compiled output boost library, right?
>
> These Mac scripts needs probably some tweaking. Since they were used last some dependencies have changes.
> From boost Hugins needs now only boost::filesystem (instead of boost::thread we are using std::thread)
> In build-all.sh there are references to glib, lensfun, make, tclap, liblcms which are not needed anymore (maybe also libffi - I don't know which lib is using it).
> So this needs also some more 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/1079014f-8c6c-43b0-a780-45a3d4671ba1%40googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

> <Bildschirmfoto 2016-04-13 um 17.32.24.png>

[David Haberthür]

Dear Niklas
Thanks for providing us Mac users with a fresh build.
Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) with it.
I can open a panorama, but when I want to see the OpenGL preview, Hugin instantly crashes hug

Unfortunately, I cannot get anything useful from the Console-App which would hint at the bug I’m hitting.
The only thing I get in the console is
—
25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: (net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal code: 1
—

When I work with the ‘old’ preview window I can stitch some of my recent panoramas without problems.
Will try to make a new one for testing soon.
Habi

>> On Apr 17, 2016, at 2:09 PM, Niklas Mischkulnig <nik...@mischkulnig.de> wrote:
>>
>> Here is a (hopefully working) build (version 2016) . Please test it and tell me if something crashes (there might still be a wrong dylib install path lurking in a dark corner :D ).
>>
>> https://www.dropbox.com/s/oi6etuyobwkxwbb/Hugin.zip?dl=1
>>

>> Am Samstag, 2. April 2016 08:45:28 UTC+2 schrieb Niklas Mischkulnig:
>> Why hasn't there been a Mac build on sourceforge for over one year (there isn't a windows build for the 2016.0.0 yet)?
>>

>> --
>> 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/b54aec89-34a4-4cbd-a43e-5f7722dfb213%40googlegroups.com.

>> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> 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/CF33958A-A2F2-4C66-9EBB-0ABF135B2A5F%40accesscomm.ca.

[Niklas Mischkulnig]

You could try to open Hugin using the Terminal, maybe there are more meaningful error messages there.

- Open Terminal

- drag Hugin.app over the Terminal window and let go

- remove one space and add /Contents/MacOS/Hugin  to the path

- press enter, Hugin should start; look at the terminal window for error messages during the crash.

Niklas

[T. Modes]

Am Montag, 18. April 2016 14:40:54 UTC+2 schrieb Niklas Mischkulnig:

https://trac.macports.org/attachment/ticket/41463/patch-src-hugin1-icpfind-AutoCtrlPointCreator.cpp.diff

(Discussion here: https://trac.macports.org/ticket/41463)

Thanks, I committed a slightly modified patch (the line mentioned has already changed).
 

Maybe there is someone who can tell me exactly what program needs which libraries (especially which boost library) and binaries(like cpfind, celeste, ...)  to shrink down the application sizes (currently 2* ~80mb and 1* ~50mb) ?

 

From boost we need only boost::filesystem. It is used by huginbase,  hugin_lensdb and pto_move.
The README file contains an uptodate list of all dependencies for Hugin. Most of them are used in huginbase and therefor also pulled into all other programs.

[T. Modes]

Am Dienstag, 19. April 2016 20:36:18 UTC+2 schrieb Niklas Mischkulnig:

But then: #if defined __WXMAC__ && defined MAC_SELF_CONTAINED_BUNDLE ; sure __WXMAC__ is set but MAC_SELF_CONTAINED_BUNDLE isn't (doing that creates a whole lot more compile errors).  That means that it searches in path.

What's going on, especially with ExifTool, the code, which searches it, is quite complex?

When MAC_SELF_CONTAINED_BUNDLE is defined special code for the Mac bundles is used to look for the binaries in the bundle (it calls the function MacGetPathToBundledExecutableFile).
So I assume for a bundled version this define is needed. (And may explain the problems with enblend/enfuse/assistant).
I changed the code from the makefile version to now the wxWidgets version for stitching and assistant some time ago. Since then nobody has build a Mac bundle. So it may be that there are some glitches which I introduced when I reworked the code. Maybe only an include is missing? But without the (exact) error messages this is impossible to say.

Thomas

[Niklas Mischkulnig]

Compiling works(see attached errors and patch) 

But the problems in PTBatcherGUI remain, although enblend and ExifTool are bundled inside the .app (see screenshots)

Blender: Unknown blender (enblend —version failed)

ExifTool: FAILED

Niklas

[David Haberthür]

Ciao Niklas.

> You could try to open Hugin using the Terminal, maybe there are more meaningful error messages there.
> - Open Terminal
> - drag Hugin.app over the Terminal window and let go
> - remove one space and add /Contents/MacOS/Hugin to the path
> - press enter, Hugin should start; look at the terminal window for error messages during the crash.

Great idea, I haven’t though of this [1].
When I open Hugin this way in the Terminal, I get a single line after the crash, namely
—
lcms: Error #12288; Output profile is operating on wrong colorspace
—

I thought that’s maybe something related to the .tiff Images I’m using as an input for this panorama.
So I tried to make a new panorama with only .jpg images, which worked fine apart from a small note in the Terminal regarding
—
ERROR: 17:52:45.166226 (/Users/niklas/development/test/src/hugin1/hugin/ProjectionGridTool.cpp:371) createTexture(): GL Error when building mipmap levels: invalid frame buffer operation
—

But then I re-opened an old panorama, and got the same lcms error again when opening the fast preview.
On others I don’t get it, which makes it quite hard to pin down to an exact cause…

How can I continue to help with debugging?

Habi


[1: ]Or more precisely I did `cd /Applications/Hugin_2016/ && open Hugin.app/‘, which gives no output after a crash…

> To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/39509940-ad22-4f6e-9e36-b1b46de0a54f%40googlegroups.com.

[T. Modes]

Am Montag, 25. April 2016 17:44:32 UTC+2 schrieb Niklas Mischkulnig:

Compiling works(see attached errors and patch) 

Thanks, applied the patch (but the patch was backwards)

But the problems in PTBatcherGUI remain, although enblend and ExifTool are bundled inside the .app (see screenshots)

Blender: Unknown blender (enblend —version failed)

ExifTool: FAILED

Could you apply the attached patch and try again? It will print the used path additionally, so maybe this helps us a bit further.

Thomas

[T. Modes]

Hi David

Am Montag, 25. April 2016 17:59:16 UTC+2 schrieb David Haberthür:

When I open Hugin this way in the Terminal, I get a single line after the crash, namely
—
lcms: Error #12288; Output profile is operating on wrong colorspace
—

Could you provide a file which shows this error?
Maybe I can reproduce the error also on other systems.

Thomas

[Niklas Mischkulnig]

Here you go:

enblend: enblend

Blender: Unknown blender (enblend —version failed)

exiftool: exiftool

ExifTool: FAILED

[Donald Johnston]

I received the same error and I’ve attached the jpg file that caused the problem.

lcms: Error #12288; Output profile is operating on wrong colorspace

I got that error with a large version of the attached image as well.  Also with a tif file.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/39509940-ad22-4f6e-9e36-b1b46de0a54f%40googlegroups.com.

[Niklas Mischkulnig]

I first noticed that error, when converting the raw images from Sukima's workflow thread to jpg using Adobe Camera Raw, the converted images are attached (in sRGB and AdobeRGB, though both cause the same error)

lcms: Error #12288; Output profile is operating on wrong colorspace

[T. Modes]

Hi Niklas

Am Montag, 25. April 2016 18:55:00 UTC+2 schrieb Niklas Mischkulnig:

Here you go:

enblend: enblend

Blender: Unknown blender (enblend —version failed)

exiftool: exiftool

ExifTool: FAILED

Okay, it does not find the executables. So we need to dig deeper.
The attached patch activates more debug information (it goes to the console). Maybe it helps to find which functions fails.

Thomas

[T. Modes]

Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:

I first noticed that error, when converting the raw images from Sukima's workflow thread to jpg using Adobe Camera Raw, the converted images are attached (in sRGB and AdobeRGB, though both cause the same error)

lcms: Error #12288; Output profile is operating on wrong colorspace

All affected files contains an icc profile. But I don't get an error.
Can you check if Hugin has found a monitor profile? (Go to about screen, tab system, is there a line "Monitor profile:.."? If yes, please provide the file mentioned here.)

Thomas

[Alexandr Krylovskiy]

Hi Niklas,

first of all, thank you for your efforts! 

I'll be keeping an eye on this thread, so you've got yourself another tester :)

Trying that build from goole drive, Hugin crashed loading a single 16-bit TIFF file with the following error in terminal:

lcms: Error #12288; Output profile is operating on wrong colorspace

Couldn't find this error being discussed here, so I thought it might be of help.

Best regards,

Alex

On Monday, April 18, 2016 at 7:26:10 PM UTC+2, Niklas Mischkulnig wrote:

Thank you for your tips! 

Here is a new link (just being cautious):

https://drive.google.com/uc?export=download&id=0B_seRjFxxDleU1YtQ1Zka1BXM2c


Am Montag, 18. April 2016 18:50:23 UTC+2 schrieb Harry van der Wolf:

In the time that I built the bundles I once build the Hugin.app as a full bundle and made symlinks to all redundant libraries in both other apps. That decreased the size of the apps indeed but it required all thee apps to be in the same folder (which as such is quite logical).

However, this build scenario made the compilation even harder and even though the 3 apps are a big chunk of data: What is 180 MB even on a (small) 128 GB solid state disk. Leave alone on a 750+ GB disk.

At that time I simply wanted to try, but it wasn't worth all the hassle.

Besides: If a user wants it differently then he/she can buid it himself/herself.

Note that I have left OSX about 2½ years ago. 

I think you did an awesome job in building the new 2016 version for Mac. If enough users have tested the builds I would suggest to upload them to sourceforge where the other older bundles reside as well.

If you get too many downloads on your dropbox account it will be completely blocked for others to download. Only you yourself can use it then.

I experienced that myself with another build (not for mac). I used dropbox mainly to share things with my family. Even that was no longer possible. With 180 MB bundles this might go faster then you expect.

Harry

2016-04-18 18:29 GMT+02:00 Niklas Mischkulnig <nik...@mischkulnig.de>:

The main duplicate and large part are the dylibs under Hugin.app/Libraries/. These could be in a folder alongside Hugin.app, PTBatchGui.app and calibratelensgui.app, reducing the total filesize from 231 mb to 231-(2*35)=180mb. Putting the Resources/xrc folder there as well would shave off another 15 mb (resulting in 165mb).

Is it worth the effort?

Niklas

Am Montag, 18. April 2016 18:05:10 UTC+2 schrieb Harry van der Wolf:

The fact the mac bundles are that big is due to the "bundle all dependencies" inside the app. That gives a lot of redundancy in the apps. That is already for years and years a fact and as long as Apple doesn't change their policy it will stay that way.

When compiling with XCode this strip functionality is automatically executed but results in about 10% size reduction. But my information is going years back.

Harry

2016-04-18 17:07 GMT+02:00 Jan Dubiec <j...@onet.pl>:

On 2016-04-18 14:40, Niklas Mischkulnig wrote:
[...]

> Maybe there is someone who can tell me exactly what program needs which
> libraries (especially which boost library) and binaries(like cpfind,
> celeste, ...)  to shrink down the application sizes (currently 2* ~80mb
> and 1* ~50mb) ?

I don't know Macs but I'm quite sure that there is strip utility
(https://en.wikipedia.org/wiki/Strip_%28Unix%29) for Macs.

If you want to know about dependencies, read about CMake's --graphviz
option. It allows you to generate graphs like this:
* for the whole project –
https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
* for the whole project with external dependencies –
https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
* for a module (hugin in this case) –
https://www.dropbox.com/s/bfsz6byb86o2l89/HuginHg.hugin.pdf?dl=0
* for a module with external dependencies –
https://www.dropbox.com/s/7h1yauyooqo0ggj/HuginHg.hugin-ext.pdf?dl=0.

/J.D.

--
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/5714F841.2020009%40onet.pl.

For more options, visit https://groups.google.com/d/optout.

--
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/a7cc3b06-7e9c-4ecd-8d65-866a67480afe%40googlegroups.com.

[Niklas Mischkulnig]

At least on my machine, there is no such line.

I will look into this error (comes up after opening the about screen): 

 Kann Datei '/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt' nicht öffnen (Fehler 2: No such file or directory)

[T. Modes]

Hi Nikolas,

Am Dienstag, 26. April 2016 15:30:40 UTC+2 schrieb Niklas Mischkulnig:

At least on my machine, there is no such line.

I will look into this error (comes up after opening the about screen): 

 Kann Datei '/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt' nicht öffnen (Fehler 2: No such file or directory)

The file COPYING was renamed to COPYING.txt. I updated already one shell script, but maybe the XCode project files still addresses the old file COPYING and needs be updated.

[Niklas Mischkulnig]

This is the output with the two patches:

cout:

INFO 17:04:06.828634 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc

INFO 17:04:06.829864 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale

log:

enblend: enblend

Blender: Unknown blender (enblend --version failed)

exiftool: exiftool

ExifTool: FAILED

By the way, the colorspace crash still happens (if http://hg.code.sf.net/p/hugin/hugin/rev/ca640dfdbf7f was related to this)

[T. Modes]

Am Dienstag, 26. April 2016 17:10:23 UTC+2 schrieb Niklas Mischkulnig:

This is the output with the two patches:

cout:

INFO 17:04:06.828634 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc

INFO 17:04:06.829864 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale

There should be more output to cerr. Something is missing.

log:

enblend: enblend

Blender: Unknown blender (enblend --version failed)

exiftool: exiftool

ExifTool: FAILED

By the way, the colorspace crash still happens (if http://hg.code.sf.net/p/hugin/hugin/rev/ca640dfdbf7f was related to this)

I know, that's why I want know if there is monitor profile.
 

[Niklas Mischkulnig]

I found the reason: In Xcode when I set the MAC_SELF_CONTAINED_BUNDLE flag, it applies it recursively to all other targets, except base_wx.

I attached the compile errors in Executor.cpp.

[T. Modes]

Am Dienstag, 26. April 2016 17:46:23 UTC+2 schrieb Niklas Mischkulnig:

I found the reason: In Xcode when I set the MAC_SELF_CONTAINED_BUNDLE flag, it applies it recursively to all other targets, except base_wx.

I attached the compile errors in Executor.cpp.

Okay, we make progress. Mainly a simply include was missing.
I committed the changes to the repository.
Attached is a modified patch. It contains both former patches and some little bugfixes from your last report.

Thomas

[Alexandr Krylovskiy]

Please disregard my previous E-mail, I've missed the third page of the thread.

There is no "Monitor profile: " line on my machine either (13'' macbook pro retina 2013 running 10.11.4)

[Niklas Mischkulnig]

Everything seems to be working now.

In patch-xrc.sh, I had to change line 12 to hugin_exiftool_arg="../src/hugin1/base_wx/hugin_exiftool_copy.arg"

bash:

INFO 18:43:49.061780 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc

INFO 18:43:49.062303 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale

INFO 18:43:59.837025 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) MacGetPathToBundledExecutableFile(): Mac: executable's full path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:43:59.837742 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) MacGetPathToBundledExecutableFile(): Mac: executable's full path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:44:00.089661 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

INFO 18:44:00.090335 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

INFO 18:44:01.490650 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) MacGetPathToBundledExecutableFile(): Mac: executable's full path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/nona

INFO 18:44:01.491851 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) MacGetPathToBundledExecutableFile(): Mac: executable's full path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:44:01.492607 (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) MacGetPathToBundledResourceFile(): Mac: the resource file's path in the application bundle: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

log:

enblend: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Blender: enblend 4.1.1

exiftool: /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool/exiftool

ExifTool version: 9.76

[Donald Johnston]

Thomas, I use a display profile created by Spyder4Pro.  The contents of the system tab from Hugin are:

Operating System: Mac OS X (Darwin 15.4.0 x86_64)

Architecture: 64 bit

Free memory: 0 kiB

Hugin

Version: 2016.1.0 built by Niklas Mischkulnig

Path to resources: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/

Path to data: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/

Hugins camera and lens database: /Users/donaldjohnston/.hugindata/camlens.db

Multi-threading using C++11 std::thread and OpenMP

Libraries

wxWidgets: wxWidgets 3.0.2

wxWidgets Library (wxMac port)

Version 3.0.2 (Unicode: wchar_t, debug level: 0),

compiled at Apr 17 2016 17:11:02

Runtime version of toolkit used is 10.11.

libpano13: 2.9.19 

Boost: 1.60.0

Exiv2: 0.25

SQLite3: 3.8.10.2

Vigra: 1.10.0

LittleCMS2: 2.7

So I see no mention of a profile but I’ve attached the icc profile I use.

[Niklas Mischkulnig]

Here is a new build which correctly finds enblend and ExifTool in PTBatcherGui.app, though the colorspace error still happens.

https://drive.google.com/uc?export=download&id=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Niklas

[Alexandr Krylovskiy]

Unfortunately I can't launch the new build:

> ./Hugin

dyld: Library not loaded: /Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib

  Referenced from: /Users/krylovskiy/distr/photo/Hugin/Hugin.app/Contents/MacOS/./Hugin

  Reason: image not found

zsh: trace trap  ./Hugin

[T. Modes]

Am Mittwoch, 27. April 2016 15:34:35 UTC+2 schrieb Niklas Mischkulnig:

Here is a new build which correctly finds enblend and ExifTool in PTBatcherGui.app, though the colorspace error still happens.

Concerning the colorspace error, can somebody please test the following:

1.) Save the jpg from http://fotovideotec.de/browser_farbmanagement/ (sorry, the image is german, but I found no english version)
2.) Load the image in Hugin (it will ask for the HFOV, simply use 50 deg or cancel the dialog, it does not matter)
3.) Select the image on the photo tab -> Is is correctly displayed (blue sky, yellow-green tree) or displayed with wrong colors or does Hugin crash?

If Hugin does not crash, continue
4.) Go to the control points tab -> Is the image displayed with correct colors or with wrong colors?
5.) The same on the mask tab -> Is the image displayed with correct colors or with wrong colors?
6.) Now open the fast preview windows -> Does it crash now? Or is the image displayed with correct/wrong colors?

Thanks

[Niklas Mischkulnig]

Crashes instantly on step 2.) after closing the dialog.

[T. Modes]

Hi Niklas,

Am Mittwoch, 27. April 2016 17:47:29 UTC+2 schrieb Niklas Mischkulnig:

Crashes instantly on step 2.) after closing the dialog.

I feared this. But this excludes some issues.
Can you please apply the attached patch with some more diagnostic output.

When starting Hugin you should get a message box with some more information (you may expand the box).
It should print something like:
18:26:30: Created sRGB profile
18:26:30: Profile: sRGB built-in
18:26:30: Colorspace: RGB

Thanks,

Thomas

[Donald Johnston]

3) it looks the same on the photos tab as it does on the web site.

4) good

5) good

6) crash

lcms: Error #12288; Output profile is operating on wrong colorspace

--
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/395956d4-6953-4c39-bdda-222a58db0e15%40googlegroups.com.

[Donald Johnston]

I tried both to “cancel” the dialog box and to enter “50” and both ways it only crashes at step 6.

-- 
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/57809224-b7b1-4b63-b544-494d4399f87b%40googlegroups.com.

[Donald Johnston]

Niclas, I get the same error with the new build:

dyld: Library not loaded: /Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib

  Referenced from: /Applications/Hugin/Hugin.app/Contents/MacOS/hugin

  Reason: image not found

Trace/BPT trap: 5

And here is the detailed report if it helps …

Process:               hugin [2715]

Path:                  /Applications/Hugin/Hugin.app/Contents/MacOS/Hugin

Identifier:            hugin

Version:               ???

Code Type:             X86-64 (Native)

Parent Process:        bash [1995]

Responsible:           Terminal [1993]

User ID:               501

Date/Time:             2016-04-27 10:54:35.398 -0600

OS Version:            Mac OS X 10.11.4 (15E65)

Report Version:        11

Anonymous UUID:        A8B1503F-C972-23E6-559F-F8074FE4989B

Sleep/Wake UUID:       01B2B422-9831-4A0E-BF52-CCED392577BB

Time Awake Since Boot: 7400 seconds

Time Since Wake:       2400 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)

Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:

dyld: launch, loading dependent libraries

Dyld Error Message:

  Library not loaded: /Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib

  Referenced from: /Applications/Hugin/Hugin.app/Contents/MacOS/hugin

  Reason: image not found

Binary Images:

    0x7fff65f5f000 -     0x7fff65f960d7  dyld (360.21) <D9B236BC-4AC1-325F-B3EF-3F06DBDA7119> /usr/lib/dyld

    0x7fff933a8000 -     0x7fff9349aff7  libiconv.2.dylib (44) <F05A0A5A-92A9-3668-8F20-F27CBDA26BE9> /usr/lib/libiconv.2.dylib

Model: MacBookPro9,1, BootROM MBP91.00D3.B0D, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.1f175

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

Bluetooth: Version 4.4.4f4 17685, 3 services, 19 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en1

Serial ATA Device: APPLE HDD HTS541010A9E682, 1 TB

Serial ATA Device: HL-DT-ST DVDRW  GS31N

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: FaceTime HD Camera (Built-in)

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: IR Receiver

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: USB 3.0 Bus

Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1

-- 
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/18ce314d-59ad-4056-a6b1-7fd3bd35c08a%40googlegroups.com.

[Niklas Mischkulnig]

I am working on the library errors, but compiling all dependencies will take a while.

Here:

19:29:31: Created sRGB profile

19:29:31: Profile: sRGB built-in

19:29:31: Colorspace: RGB

[T. Modes]

Am Mittwoch, 27. April 2016 19:32:15 UTC+2 schrieb Niklas Mischkulnig:

I am working on the library errors, but compiling all dependencies will take a while.

Here:

19:29:31: Created sRGB profile

19:29:31: Profile: sRGB built-in

19:29:31: Colorspace: RGB

That looks okay. I will have to search further.

[T. Modes]

Hi Niklas,

Maybe in some Mac OS header conflict with our implementation.
Could you please test the attached patch?

Thomas

[Niklas Mischkulnig]

Hi Thomas,

nope, that doesn't change anything.

But I found out, that it works in the non-OpenGL preview window (see screenshot)

Niklas

[Dale Bengston]

Niklas and everyone,

Thank you so much for working on this! I'm testing the April 18 build downloaded from Google Drive... same problem as others with embedded color profiles. (I stripped profiles out of my images so I could continue to test.) I am so happy to be using something besides 2014.0.0. I will post back with other issues if I encounter any.

Thanks again for taking this on,

Dale

[T. Modes]

Am Donnerstag, 28. April 2016 19:59:12 UTC+2 schrieb Niklas Mischkulnig:

Hi Thomas,

nope, that doesn't change anything.

But I found out, that it works in the non-OpenGL preview window (see screenshot)

That's a good news. That means that at least the internal profile is okay.
I have attached 2 variants for testing. Both are using different approaches. Hopefully one is working now.

Thomas

[Sukima]

I don't wish to detract this thread to much from finding a stable build for Mac users but when that task is complete it leaves a burning question: How does the Hugin community prevent such a  tragedy in the future?

If there was a way to keep the source up-to-date then building a release binary would not be difficult as there are enough developers out there with XCode. But changing the code of something that a) uses open-gl which has a long history of destroying any sanity one might have had (mainly from graphics card drivers that are near impossible manage; see Lunis's reaction to Nvidia on that point) and b) does math on digital photography which is best left to the realm of PHDs, Adobe employees, and Gods!

That diatribe aside, I'd love to see how the Mac specific source code can be kept up-to-date with the Hugin core so binaries can easily be made and mirrors can be uploaded to. Thoughts, ideas?

BTW thank you so much for taking it on to make a Mac build of 2016. The old version is almost unusable on El Capitain. and I've yet to get a working linux virtualbox running well enough to manage the intensity needed by a panorama stitcher!

On Saturday, April 2, 2016 at 2:45:28 AM UTC-4, Niklas Mischkulnig wrote:

Why hasn't there been a Mac build on sourceforge for over one year (there isn't a windows build for the 2016.0.0 yet)?

[Niklas Mischkulnig]

Unfortunately neither is working.

[T. Modes]

Hi Niklas,

Am Freitag, 29. April 2016 13:00:40 UTC+2 schrieb Niklas Mischkulnig:

Unfortunately neither is working.

That's strange. Maybe we need to locate the error more precise. I'm attaching 2 patches.
Please apply only one at once. If none of the both files prevents the crashes, I have searched at the wrong place.

Thomas

[T. Modes]

Hi Sukima,

Am Donnerstag, 28. April 2016 23:36:47 UTC+2 schrieb Sukima:

I don't wish to detract this thread to much from finding a stable build for Mac users but when that task is complete it leaves a burning question: How does the Hugin community prevent such a  tragedy in the future?

If there was a way to keep the source up-to-date then building a release binary would not be difficult as there are enough developers out there with XCode.

It's vice versa. The source code was still working at Mac OS. But nobody of the many Mac OS users was able and willing (until now) to build it.
There are some minor glitches which can be easily solved if someone build on Mac OS.

Thomas

[dgjohnston]

Yes a really really big thanks to Niklas for the work to get this compiled and to Thomas for doing the debugging. Don't give up you two. We Mac users are relying on you. 

Don Johnston

Sent from my Samsung device

--
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/bae3d91b-80f1-4d31-b0e1-549c89065688%40googlegroups.com.

[Niklas Mischkulnig]

Same as before.

Niklas

[T. Modes]

Hi Niklas,

Am Samstag, 30. April 2016 12:02:32 UTC+2 schrieb Niklas Mischkulnig:

Same as before.

That's strange. At least the skip_profile.diff patch has disabled all lcms code in the fast preview window.
So I don't know why it still bring the "wrong colorspace" error from lcms.
Can you run Hugin in a debugger so we can get more information where it crashes?
Or are there other log files which could shed some light on the issue?

Thomas

[Niklas Mischkulnig]

Hi Thomas, 

an excerpt from system.log is attached, maybe it's helpful.

I can't really debug it, because all the debug symbols seem to be stripped, even though I set Xcode to not do that (see gdb.log anyway).

Niklas

[Niklas Mischkulnig]

Hey,

I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I had to add --ignore-whitespace. 

It works now(see image).

Sorry, 

Niklas

[Michael Holden]

I want to thank everyone who is contributing to the mac build endeavour. I've made a few attempts to compile from source over the pas year or so, and while I may have come close I never ended up with a functional application. I'm not a software engineer, and haven't built mac apps, so this isn't really very surprising. I've checked back every few months, and was delighted to find this thread. Reading through it made me very very grateful for your collective efforts. It is easy to forget how advances in open source software are made by individual people from all over the world, one patch at a time, on threads like this one. I'm not sure if or how I can be of assistance other than by breaking stuff, and if that's the case, want  to express my sincere gratitude for having stuff to break in the first place. Much respect to you all.

[T. Modes]

Hi Niklas,

Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:

Hey,

I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I had to add --ignore-whitespace. 

It works now(see image).

Sorry, 

Niklas

No problem. So we have tracked down the problem.
I had an idea. I committed a changeset to the repository. Could you please test it? (But check before that all patches are removed)
If this does not work, I will prepare another test patch.

Thomas

[David Haberthür]

On 26 Apr 2016, at 09:12, T. Modes <Thomas...@gmx.de> wrote:
Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:
I first noticed that error, when converting the raw images from Sukima's workflow thread to jpg using Adobe Camera Raw, the converted images are attached (in sRGB and AdobeRGB, though both cause the same error)

lcms: Error #12288; Output profile is operating on wrong colorspace

All affected files contains an icc profile. But I don't get an error.
Can you check if Hugin has found a monitor profile? (Go to about screen, tab system, is there a line "Monitor profile:.."? If yes, please provide the file mentioned here.)

I don’t see a monitor profile on my OS X 10.11.4, see attached screenshot (that’s the full output of the System tab)

Habi

[Niklas Mischkulnig]

Hi Thomas,

still crashes.

Niklas

[Niklas Mischkulnig]

Here is a new build, hope it works:

https://drive.google.com/uc?export=download&id=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Niklas

[Stefan Peter]

On 28.04.2016 23:36, Sukima wrote:
> I don't wish to detract this thread to much from finding a stable build
> for Mac users but when that task is complete it leaves a burning
> question: How does the Hugin community prevent such a tragedy in the
> future?

I think that there is only one way: participation. The sources of the
development version of Hugin are freely available and can be compiled by
any user on any operating system she or he are interested in.

I, for example, do nightly builds for several Ubuntu versions. So
whenever something breaks these builds, I can speak up. And I get plenty
of help from other builders and Thomas, the main developer, in these
cases. This results in much less problems showing up when a release happens.

These nightly builds are scripted and run with no interaction required
every night. Of course, when something breaks I have to interfere. And
as my are targeted towards the Ubuntu crowd, the actual building and
distribution is automated, curtsey of the invaluable launchpad.net
infrastructure. However, if anyone is interested in the scripts, they
are available at
https://stefa...@bitbucket.org/stefanpeter/nightly4hugin.git

Producing nightly builds for your operating system of choice has another
benefit: There are much more users involved in beta
testing when nightly builds are available. So the overall quality of
Hugin increases by following the opensource mantra "release early,
release often".

Of course, nightly builds of the development version may be broken from
time to time. So if you plan to offer these for your operating system of
choice, make sure there is a fall back option in the form of a stable
version that can be installed. And please communicate this fact to your
end users.

Regards

Stefan Peter

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
(See https://en.wikipedia.org/wiki/Posting_style for details)

[Donald Johnston]

Okay, partially works for me.  I took a RAW image from my camera and used Photomatix to convert it to jpeg. I used DxO Optics pro to convert the same image to tif and jpeg.

Hugin opens and displays the jpeg from Photomatix.

When I open tif or jpeg image created by DxO; hugin crashed with:

lcms: Error #12288; Output profile is operating on wrong colorspace

Here is a link to the three files if it helps:

https://www.dropbox.com/sh/4hv4giyrbnur4no/AACG2K8BPLzeuDTXcQQo2fAea?dl=0

--
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/2da31ea6-78c7-415c-8b11-53edaa4c10e7%40googlegroups.com.

[T. Modes]

Hi Niklas,

Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:

still crashes.

That's strange.
Could you please apply the attached patch. It will print some more information to stdout like:

CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
TexManager
inputICC: farbverdreht
monitorProfile:
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192

It should (hopefully) not crash, but will not take the icc profile in the fast preview window into account.
And we are testing all parameters which goes to cmsCreateTransform, which is the function I assume is crashing.

Thomas

[Niklas Mischkulnig]

This is about the only error which we are trying to solve right now. The problem is that a color profile is embedded inside the image; for now, you'll have to make panoramas out of pictures without color profiles.

Niklas

[Donald Johnston]

We can do that! Thanks again Niklas for all the work (and patience) you’ve put into this.

I’ll do some deeper testing on Hugin and let you know if I run into anything else.

To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/cff69924-3168-4042-a241-35205183c3e0%40googlegroups.com.