Dear all,
I'm developing a software that uses libraw. This software is multi-platform and is able to run on GNU/Linux, OS X, FreeBSD and Windows through MSYS2.
Indeed, libraw is available on MSYS2 and that makes things easy. However there's a small issue that is kind of annoying: I cannot use the function
libraw_open_wfile
as I would like to do. For example with libtiff i use TIFFOpenW.
Hi,
I have an issue with LibRaw 0.19 on macOS. I'm using DigiKam 6beta which now includes LibRaw 0.19 and this is crashing while scanning RAW (NEF) images from a Nikon D5300 12bit.
This is not happening with LibRaw 0.18.11 in an earlier build of DigiKam6beta
How can I help to track this bug down and get it fixed?
I was installing rawtoaces utility on Centos 7 and was facing an issue. I installed the latest LibRaw-0.19.0.tar.gz, and it seems to be giving me an error saying libraw.so is needed. I can't find libraw.so in /usr/lib64/. Could you kindly let me know a workaround? Thanks in advance. PFA the error screenshot.
I'm getting an error as shown in the attached screenshot. I am installing rawtoaces on Centos and its giving
error: id returned 1 exit status. Could you please help me out? Any insight will be helpful. Thank you.
...field was set to a long string of many "O" characters; this seems unlikely, and I am not seeing those in a binary search of the file. Perhaps the field was not set (or cleared) on decode?
I wanna build LibRaw using LibRaw.sln provided in the downloaded source package, instead of the steps using nmake described here: https://www.libraw.org/docs/Install-LibRaw-eng.html. That webpage claims that "Only the thread-safe library is built under Win32", which implies that the output libraw.dll is thread-safe. So my question is: is the library built by LibRaw.sln still thread-safe?
My environment and settings:
- Windows 10 version 1803, 64bit
- Visual Studio 2015 Update 3
- Release x64 build
Recent comments