Hi support,
More details, I am using the GNU compiler Collection c++ gcc-g++ version 11.2.0-1.
Whatever i try, the swab function causes the problem: not declared in this scope.
Thanks,
Mabula
I use Capture One 21 (I am aware that 22 should support the Sony A7IV).
And I use Affinity Photo 1.10.4.1198 (Photoshop replacement). Affinity support says their software depends on LibRAW for camera support... Yet, FastRawViewer 2.0 already seems to support the camera already.
And I use darktable 3.8.0 (both Windows and Linux).
Hello, any idea when the Sony A7IV will be added to the library?
It turns out some of the editing software I use, used LibRAW to read the raw files. Until that is updated, I can't edit my raw files in those...
Thank you!
Thanks - the rawpy folks mentioned the terminal output all looks fine, but that perhaps I should try again and enable the RPi RAW support. When compiling LibRaw I made the folder ~/Desktop/libraw into which I cloned the LibRaw repo.
- Can I remove that folder and try compiling again, or were LibRaw files installed elsewhere that need to be removed?
- In the future, what folder do you recommend I clone the LibRaw repo into?
No, it indicates that you haven't installed some optional libraries before running cmake, and haven't selected some options. You can ask at rawpy if they use those options.
Thank you for the reply. I followed the instructions (below) provided by rawpy (which uses LibRaw), as suggested by Iliah Borg (see further up for this discussion). Should I instead follow the LibRaw provided instructions?
Hi - I just wanted to confirm I installed from source correctly. Below is the terminal output resulting from my cmake command. As you'll note, it indicates a few files were not found. Additionally, can I remove the ~/Desktop/libraw folder I created to clone the libraw repo?
cmake .
-- CMake version: 3.18.4
-- LibRaw string version: 0.20.0
-- LibRaw ID version: 0x0200
-- LibRaw SO version: 20.0.0
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for LCMS2 availability...
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'lcms2'
-- No package 'lcms2' found
-- lcms2 NOT found
-- Check for LCMS availability instead LCMS2...
-- Checking for module 'lcms'
-- No package 'lcms' found
-- Could NOT find LCMS (missing: LCMS_LIBRARIES LCMS_INCLUDE_DIR)
-- Found ZLIB: /usr/lib/arm-linux-gnueabihf/libz.so (found version "1.2.11")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR JPEG_LIBRARIES)
--
-- ----------------------------------------------------------------------------------
-- Libraw 0.20.0 configuration
--
-- Libraw will be compiled with OpenMP support .................. YES
-- Libraw will be compiled with LCMS support .................... NO
-- Libraw will be compiled with example command-line programs ... YES
-- Libraw will be compiled with RedCine codec support ........... NO
-- Libraw will be compiled with DNG deflate codec support ....... YES
-- Libraw will be compiled with DNG lossy codec support ......... NO
-- Libraw will be compiled with RawSpeed support ................ NO
-- Libraw will be compiled with debug message from dcraw ........ NO
-- Libraw will be compiled with Foveon X3F support .............. NO
-- Libraw will be compiled with Raspberry Pi RAW support ........ NO
-- Libraw will be compiled as a shared library
-- ----------------------------------------------------------------------------------
--
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/Desktop/libraw/libraw
RPi is indeed ARM-based, and we never performed extensive LibRaw testing on RPi. Based on my quick test, based on the fact that LibRaw is among Raspberry Pi libs packages (can be installed using apt), and based on experience of many RPi users, it does work.
Yep, no problem! One final question about all this for my own edification - my initial confusion about whether LibRaw could be installed on an RPi stemmed from here, which states "LibRaw has been tested on 32- and 64-bit Unix systems working on x86- (and AMD64-) compatible processors.". I am admittedly inexperienced with this, but I believe the RPi is ARM-based, so I wasn't sure if it was included on that list of tested systems. Please let me know if I've misunderstood. Thank you!
Why "seems", I checked with my RPi before posting.
Which method of installation to use depends on your needs.
Generally if you want a package (rawpy in your case), it's a good idea to follow the instructions accompanying the package, especially when those instructions refer to a particular (not the latest) version of a library. You will need to install git and cmake,
My apologies re. "seems" - I did not intend to cast doubt on your reply. Thank you very much for all the helpful information, and for checking these installation instructions on your own RPi - that is greatly appreciated! I am looking forward to using LibRaw.
Thank you for the helpful information! So it seems LibRaw can be installed on an RPi - this is great!
Just to clarify, in the case where both options are available (apt install or compiling), is there a reason why I would choose one over the other (e.g. will the compiling option give me a newer version)?
Additionally, re. compiling, I found these instructions on rawpy's website (a package I'm hoping to use), which look similar to the instructions you provided above, but there are some differences - will either set of instructions work?
Yes, you need to link with libraw_r on Mac/Linux (and, yes, Windows build is thread-safe)
Also, thread stack may be too small for on stack allocation (LibRaw rawProcessor), so dynamic allocation is preferred (LibRaw *rawProcessor = new LibRaw;)
Thank you for your help.
Than I there is another issue related to the Java wrapper - Sorry for that. The output_color=0 was already commented out therefore was never active (leading slashes).
I have now removed the options and use the lib with the default options. After JDK18 I have to generate the sources from the header file again and will see if that helps.
Nevertheless under windows I had troubles with ljpeg-8d which is not compiling. For now I have removed libjpeg from all builds because it is not so important for the users.
samples/raw-identify.cpp sample: removed lot of extra output used only by development team
I'm not sure this was a good change. It was great to be able to get more info about the files. Please add it back.
See also the patches Cygwin itself used to carry for LibRaw 0.18, (they're probably out of date since codebase was significantly changed since), but swab is also mentioned: https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/libraw.git...
I think this comes from here: https://github.com/LibRaw/LibRaw/blob/b31fa58eea272c4ba67ccdbd527f329a5a...
_WIN32 is defined even on Cygwin, but I guess one shouldn't set LIBRAW_WIN32_CALLS on Cygwin; as a consequence, unistd.h is not included from internal/defines.h: https://github.com/LibRaw/LibRaw/blob/master/internal/defines.h#L50-L65
Any reason you're building for Cygwin, and not native MinGW instead?
According to quick googling, swab function is present in cygwin C runtime.
Sorry, do not have cygwin installed, so no additional help (e.g. what include file should be added)
Hi support,
More details, I am using the GNU compiler Collection c++ gcc-g++ version 11.2.0-1.
Whatever i try, the swab function causes the problem: not declared in this scope.
Thanks,
Mabula
Please direct Affinity team to our 'extended support options' page: https://www.libraw.org/extended-support
They currently use the public version, which is updated according to the announced schedule (update policy section on our homepage)
Hello Alex,
I use Capture One 21 (I am aware that 22 should support the Sony A7IV).
And I use Affinity Photo 1.10.4.1198 (Photoshop replacement). Affinity support says their software depends on LibRAW for camera support... Yet, FastRawViewer 2.0 already seems to support the camera already.
And I use darktable 3.8.0 (both Windows and Linux).
Thanks, Eric.
What software do you use?
Hello, any idea when the Sony A7IV will be added to the library?
It turns out some of the editing software I use, used LibRAW to read the raw files. Until that is updated, I can't edit my raw files in those...
Thank you!
Dear Sir:
Since your goal is to make rawpy work, please follow suggestions from rawpy folks.
RPi raw support is for Raspberry cameras only.
Thanks - the rawpy folks mentioned the terminal output all looks fine, but that perhaps I should try again and enable the RPi RAW support. When compiling LibRaw I made the folder ~/Desktop/libraw into which I cloned the LibRaw repo.
- Can I remove that folder and try compiling again, or were LibRaw files installed elsewhere that need to be removed?
- In the future, what folder do you recommend I clone the LibRaw repo into?
> it indicates a few files were not found.
No, it indicates that you haven't installed some optional libraries before running cmake, and haven't selected some options. You can ask at rawpy if they use those options.
Thank you for the reply. I followed the instructions (below) provided by rawpy (which uses LibRaw), as suggested by Iliah Borg (see further up for this discussion). Should I instead follow the LibRaw provided instructions?
We dropped Cmake support in LibRaw in 2014, so we do not know what cmake scripts you use and what they do and whether it is correct or not.
Supported build methods are ./configure && make and also just make -f Makefile.dist
Hi - I just wanted to confirm I installed from source correctly. Below is the terminal output resulting from my cmake command. As you'll note, it indicates a few files were not found. Additionally, can I remove the ~/Desktop/libraw folder I created to clone the libraw repo?
cmake .
-- CMake version: 3.18.4
-- LibRaw string version: 0.20.0
-- LibRaw ID version: 0x0200
-- LibRaw SO version: 20.0.0
-- The CXX compiler identification is GNU 10.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for LCMS2 availability...
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'lcms2'
-- No package 'lcms2' found
-- lcms2 NOT found
-- Check for LCMS availability instead LCMS2...
-- Checking for module 'lcms'
-- No package 'lcms' found
-- Could NOT find LCMS (missing: LCMS_LIBRARIES LCMS_INCLUDE_DIR)
-- Found ZLIB: /usr/lib/arm-linux-gnueabihf/libz.so (found version "1.2.11")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR)
-- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR JPEG_LIBRARIES)
--
-- ----------------------------------------------------------------------------------
-- Libraw 0.20.0 configuration
--
-- Libraw will be compiled with OpenMP support .................. YES
-- Libraw will be compiled with LCMS support .................... NO
-- Libraw will be compiled with example command-line programs ... YES
-- Libraw will be compiled with RedCine codec support ........... NO
-- Libraw will be compiled with DNG deflate codec support ....... YES
-- Libraw will be compiled with DNG lossy codec support ......... NO
-- Libraw will be compiled with RawSpeed support ................ NO
-- Libraw will be compiled with debug message from dcraw ........ NO
-- Libraw will be compiled with Foveon X3F support .............. NO
-- Libraw will be compiled with Raspberry Pi RAW support ........ NO
-- Libraw will be compiled as a shared library
-- ----------------------------------------------------------------------------------
--
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/Desktop/libraw/libraw
RPi is indeed ARM-based, and we never performed extensive LibRaw testing on RPi. Based on my quick test, based on the fact that LibRaw is among Raspberry Pi libs packages (can be installed using apt), and based on experience of many RPi users, it does work.
LibRaw works fine on Apple M1 ARM chip
Yep, no problem! One final question about all this for my own edification - my initial confusion about whether LibRaw could be installed on an RPi stemmed from here, which states "LibRaw has been tested on 32- and 64-bit Unix systems working on x86- (and AMD64-) compatible processors.". I am admittedly inexperienced with this, but I believe the RPi is ARM-based, so I wasn't sure if it was included on that list of tested systems. Please let me know if I've misunderstood. Thank you!
> it seems LibRaw can be installed on an RPi
Why "seems", I checked with my RPi before posting.
Which method of installation to use depends on your needs.
Generally if you want a package (rawpy in your case), it's a good idea to follow the instructions accompanying the package, especially when those instructions refer to a particular (not the latest) version of a library. You will need to install git and cmake,
After LibRaw is installed the way rawpi instructions suggest, check
If it's empty, and you want to use LibRaw independently / check the installation:
Re "seems" - I was half-joking, I got your meaning, but wanted to make it clear to readers that I checked the things.
Good luck!
My apologies re. "seems" - I did not intend to cast doubt on your reply. Thank you very much for all the helpful information, and for checking these installation instructions on your own RPi - that is greatly appreciated! I am looking forward to using LibRaw.
The easy way to install is:
To compile, install git, and after that:
To check,
Thank you for the helpful information! So it seems LibRaw can be installed on an RPi - this is great!
Just to clarify, in the case where both options are available (apt install or compiling), is there a reason why I would choose one over the other (e.g. will the compiling option give me a newer version)?
Additionally, re. compiling, I found these instructions on rawpy's website (a package I'm hoping to use), which look similar to the instructions you provided above, but there are some differences - will either set of instructions work?
Yes, you need to link with libraw_r on Mac/Linux (and, yes, Windows build is thread-safe)
Also, thread stack may be too small for on stack allocation (LibRaw rawProcessor), so dynamic allocation is preferred (LibRaw *rawProcessor = new LibRaw;)
Thank you for your help.
Than I there is another issue related to the Java wrapper - Sorry for that. The output_color=0 was already commented out therefore was never active (leading slashes).
I have now removed the options and use the lib with the default options. After JDK18 I have to generate the sources from the header file again and will see if that helps.
Nevertheless under windows I had troubles with ljpeg-8d which is not compiling. For now I have removed libjpeg from all builds because it is not so important for the users.
samples/raw-identify.cpp sample: removed lot of extra output used only by development team
I'm not sure this was a good change. It was great to be able to get more info about the files. Please add it back.
Pages