Check your version of autoconf and compare to AC_PREREQ in aclocal.m4. Try re-installing autotools if something doesn't work.
On my focal 20.04 LTS, following https://www.libraw.org/docs/Install-LibRaw.html
$ apt-cache policy pkg-config
pkg-config:
Installed: 0.29.1-0ubuntu4...
$ apt-cache policy automake
automake:
Installed: 1:1.16.1-4ubuntu6...
$apt-cache policy libtool
libtool:
Installed: 2.4.6-14...
$ autoconf -V
autoconf (GNU Autoconf) 2.69....
$ cd
$ git clone https://github.com/LibRaw/LibRaw.git
$ cd LibRaw
$ autoreconf --install
$ ./configure
$ make
$ bin/raw-identify
Usage: /home/ib/LibRaw/bin/.libs/raw-identify [options] inputfiles
Options:
-v verbose output
-w print white balance
-u print unpack function
-f print frame size (only w/ -u)
-s print output image size
-h force half-size mode (only for -s)
-M disable use of raw-embedded color data
+M force use of raw-embedded color data
-L filename read input files list from filename
-o filename output to filename
Sorry, I was confused. Repeated it so many times that I got a bit lost. Here is what happens:
./configure seems to work
make produces some warnings and errors:
configure.ac:16: error: possibly undefined macro: AC_SUBST
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:41: error: possibly undefined macro: AC_MSG_WARN
make: *** [Makefile:651: configure] Fehler 1
ignoring these, sudo make install produces the aforementioned error:
configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
make: *** [Makefile:648: config.status] Fehler 2
checking for jas_init in -ljasper... no
configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
Your file has data corruption, so processing result may depend on how such corruption is handled in the calling code, please contact your library developers for details.
C-API is just a thin layer over C++ API, so no difference here.
Based on your source code (w/ built-in filename) I assume you use normal/unaltered bayer-pattern Sony-produced image.
For such images, decoded data is in libRaw->rawdata.raw_image
Dear sir or madam,
I am an enthusiastic user of all of your products. I use it for my Sony and Canon cameras successfully. I also Use a 360 VR Insta360 X3 and older One X2 cameras and I would be delighted if your package would support the RAW DNG files captured by these two cameras.
Best regards,
Frank Tornyai
No cameras produces floating-point data raw images (yet?), one may use (different) HDR-convertor software to create floating point images.
Regarding color3/color4:
- full-color images unpacked by LibRaw itself are (mostly) color4_image, you may use any full-color (not bayer) RAW file for that, for example Canon sRAW/mRAW CR2
- full-color images unpacked by 3rd-party decoders (Adobe DNG SDK, RawSpeed) are usually color3_image images. You may use the same sRAW/mRAW CR2 and RawSpeed decoder (via LibRaw)
Thanks I don't as yet have one, looking into what might be problems in getting one with Black Friday savings! I have been told as it uses DNG it should be OK though.
Libraw uses DNG SDK only for data decoding. Metadata decoding is performed by LibRaw's code.
So, if you do not provide ZLIB and/or JPEG support to LibRaw it will refuse ZLIB and/or JPEG compressed DNG files at parse stage.
Hi, I hope you're doing fine. Can you please add support for Xiaomi mi 10t. I've captured insane astrophotographs using this phone and it also has burst long exposure mode but deep sky stacking isn't possible without you. the outcome i can either do is trailing OR timelapse of milky way. This phone also has astrophotography mode in builtin camera.
Thanks.
To get working autotools suite you need autoconf, automake, libtool and pkg-config installed.
Based on error message you provided, pkg-config is probably missing on your system
Check your version of autoconf and compare to AC_PREREQ in aclocal.m4. Try re-installing autotools if something doesn't work.
On my focal 20.04 LTS, following https://www.libraw.org/docs/Install-LibRaw.html
FYI: I did not really solve it, but the 0.19 version works without problems!
Thanks again, Jan
Yes, I checked that: automake-1.15
I will try to reinstall.
Thank you anyway for your quick reply!
It looks like you have incomplete automake/pkg-config suite installed, see comments above.
You may use make -f Makefile.dist
Sorry, I was confused. Repeated it so many times that I got a bit lost. Here is what happens:
./configure seems to work
make produces some warnings and errors:
configure.ac:16: error: possibly undefined macro: AC_SUBST
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:41: error: possibly undefined macro: AC_MSG_WARN
make: *** [Makefile:651: configure] Fehler 1
ignoring these, sudo make install produces the aforementioned error:
configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
make: *** [Makefile:648: config.status] Fehler 2
Thanks! Jan
I do not see the PKG_CHECK_MODULES substring in the provided ./configure script
Hi, just ./configure.
Do you use ./configure provided with LibRaw distiibution or generate own configure script?
Hi, same problem here, but different line:
checking for jas_init in -ljasper... no
configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
any ideas? Thanks very much, Jan
Your file has data corruption, so processing result may depend on how such corruption is handled in the calling code, please contact your library developers for details.
Here are processing results using LibRaw's dcraw_emu -w -T: https://www.dropbox.com/s/d7g25khy96nw4z8/20221010163318528158294_ori_00...
Thank you for the clarification, I was confused by the documentation, but now I understand.
raw_image is also an '*_image' field
From the documentation (which can be sometimes confusing, I agree): "After call to unpack() only one of *_image fields is non-NULL."
C-API is just a thin layer over C++ API, so no difference here.
Based on your source code (w/ built-in filename) I assume you use normal/unaltered bayer-pattern Sony-produced image.
For such images, decoded data is in libRaw->rawdata.raw_image
LibRaw supports most DNG files (all DNG files if compiled w/ DNG SDK)
Dear sir or madam,
I am an enthusiastic user of all of your products. I use it for my Sony and Canon cameras successfully. I also Use a 360 VR Insta360 X3 and older One X2 cameras and I would be delighted if your package would support the RAW DNG files captured by these two cameras.
Best regards,
Frank Tornyai
No cameras produces floating-point data raw images (yet?), one may use (different) HDR-convertor software to create floating point images.
Regarding color3/color4:
- full-color images unpacked by LibRaw itself are (mostly) color4_image, you may use any full-color (not bayer) RAW file for that, for example Canon sRAW/mRAW CR2
- full-color images unpacked by 3rd-party decoders (Adobe DNG SDK, RawSpeed) are usually color3_image images. You may use the same sRAW/mRAW CR2 and RawSpeed decoder (via LibRaw)
Thanks I don't as yet have one, looking into what might be problems in getting one with Black Friday savings! I have been told as it uses DNG it should be OK though.
Please share some example file(s)
Libraw uses DNG SDK only for data decoding. Metadata decoding is performed by LibRaw's code.
So, if you do not provide ZLIB and/or JPEG support to LibRaw it will refuse ZLIB and/or JPEG compressed DNG files at parse stage.
USE_ZLIB USE_JPEG must be used together when using DNG_SDK
AFAIK, Xiaomi smartphones record RAW in DNG format, it is supported.
Hi, I hope you're doing fine. Can you please add support for Xiaomi mi 10t. I've captured insane astrophotographs using this phone and it also has burst long exposure mode but deep sky stacking isn't possible without you. the outcome i can either do is trailing OR timelapse of milky way. This phone also has astrophotography mode in builtin camera.
Thanks.
Yes I'm using C code only. I understand why I won't work the way I do, however I'm not familiar at all with this.
Do you mind explaining me in more details the steps? Thanks.
Pages