> On 30 Mar 2017, at 21:57, Chuanist <for...@gimpusers.com> wrote: > > Pat— > > thanks for the suggestion. It makes me think that, indeed, Ufraw is a hard nut > to crack. It's kind of too bad, because the bundled and installed Ufraw in the > previous version of GIMP was very seamless and convenient to use.
Hello - I am a satisfied Mac user and an avid photographer; I use for the post-production of my pictures GIMP, namely the distribution (released by Simone Karin Lehmann) "GIMP on OS X", available under the URL http://sourceforge.net/projects/gimponosx . This distribution comes with a pre-compiled gimp-ufraw plugin; loading a RAW picture in GIMP is handled in this way. However "GIMP on OS X" lacks a standalone ufraw and ufraw-batch. Needing for my RAW pictures ufraw-batch, I compiled ufraw and ufraw-batch from the source code; however this is not completely described in the ufraw documentation. Here is what I did. For the compiler, you need to install Xcode (from the Apple Store, free) and the Xcode command line tools; how to do that is described in a lot of places, Google will help. For the libraries, I have installed the ones supplied by the Macports projects: +--------------+--------------+---------+ | | Package | Version | +--------------+--------------+---------+ | LCMS | lcms2 | 2.8 | | EXIV2 | exiv2 | 0.25 | | JPEG | jpeg | 9b | | JPEG2000 | openjpeg | 2.1.2 | | TIFF | tiff | 4.0.7 | | PNG | libpng | 1.6.28 | | ZIP | zip | 3.00 | | BZIP2 | bzip2 | 1.0.6 | | LENSFUN | lensfun | 0.3.2 | | CFITSIO | cfitsio | 3.390 | | GTKIMAGEVIEW | gtkimageview | 1.6.4 | +--------------+--------------+---------+ How to install them is described in the Macports home page, http://www.macports.org . The Macports libraries are compiled with clang and clang++ as C and C++ compilers; while clang and gcc are fully compatible, and their object files linkable together, clang++ and g++ use different name mangling schemes; so, if you want e.g. exiv2 support (exiv2 is a C++ package) you need to change the default compilers. So, finally, I unpacked, configured, compiled and installed ufraw/ufraw-batch with the following commands: tar xzf ufraw-0.22.tar.gz cd ufraw-0.22/ CC=clang CXX=clang++ CPPFLAGS=-I/opt/local/include \ LDFLAGS=-L/opt/local/lib \ ./configure --prefix=/opt/local/share/ufraw-0.22 make sudo make install sudo ln -s /opt/local/share/ufraw-0.22 /opt/local/share/ufraw ln -s /opt/local/share/ufraw/bin/ufraw ~/Applications/ufraw ln -s /opt/local/share/ufraw/bin/ufraw-batch ~/Applications/ufraw-batch ln -s /opt/local/share/ufraw/share/man/man1/ufraw.1 ~/man/man1/ufraw.1 Notes: - Macports include files are in /opt/local/include . - Macports libraries are in /opt/local/lib . - I installed ufraw in /opt/local/share/ufraw-0.22 , a directory soft-linked to /opt/local/share/ufraw ; when a new release will come, say 0.xy, it will be enough to install it in /opt/local/share/ufraw-0.xy and, then, change the soft link. - The executables ufraw and ufraw-batch are soft-linked to ~/Applications, where OS X expects to find user executables. - I have created ~/man/... for personal man files, and linked there ufraw.1, in order to have the output of "man ufraw". HTH -- Maurizio Loreti -- maurizio.lor...@gmail.com _______________________________________________ gimp-user-list mailing list List address: gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
