Recent comments

Reply to: Build problem   1 year 1 week ago

Undefined symbols: LibRaw::open_file means "You've forgot to link with libraw library"

The second group of errors means: you've build libraw with JPEG decompression support but forgot to add libjpeg to your linker input.

Reply to: Build problem   1 year 1 week ago

Thanks again. I could solve the compile problems. Now, I'm getting a lot of undefined symbols when trying to link the library against my app. Most of them sound like the optional packages have been compiled into the library, now missing their references when linking against the static library for branch "LibRaw 0.21-stable", which sounds weird.

ld: Undefined symbols:
  LibRaw::open_file(char const*), referenced from:
      _Java_net_bwmc_libraw_LibRawImageLoader_loadRawImage in LibRawImageLoader.o

I tried to resolve this, by rolling back to version 0.20 and rebuild the library for this version, which previously worked. However, the list of undefined references I get while linking is even longer. Now, it sounds like optional libraries haven't been detected as optional when switching to branch "LibRaw 0.20-stable" and rebuilding after 'make clean'.

ld: Undefined symbols:
  LibRaw::open_file(char const*), referenced from:
      _Java_net_bwmc_libraw_LibRawImageLoader_loadRawImage in LibRawImageLoader.o
  _jpeg_CreateDecompress, referenced from:
      LibRaw::lossy_dng_load_raw() in libraw.a[9](dng.o)
      LibRaw::kodak_jpeg_load_raw() in libraw.a[13](kodak_decoders.o)
  _jpeg_abort_decompress, referenced from:
      LibRaw::lossy_dng_load_raw() in libraw.a[9](dng.o)
  _jpeg_destroy_decompress, referenced from:
      LibRaw::lossy_dng_load_raw() in libraw.a[9](dng.o)
      LibRaw::lossy_dng_load_raw() in libraw.a[9](dng.o)
      LibRaw::lossy_dng_load_raw() in libraw.a[9](dng.o)
      LibRaw::kodak_jpeg_load_raw() in libraw.a[13](kodak_decoders.o)
      LibRaw::kodak_jpeg_load_raw() in libraw.a[13](kodak_decoders.o)
  _jpeg_finish_decompress, referenced from:
      LibRaw::kodak_jpeg_load_raw() in libraw.a[13](kodak_decoders.o)
      LibRaw::kodak_jpeg_load_raw() in libraw.a[13](kodak_decoders.o)
  ...

I followed the instructions how to compile by executing these commands:

autoreconf --install
./configure
make

Also I tried 'make clean' and rebuild from scratch and removed many files manually, with no success.

Any suggestion how to solve this?

Reply to: Build problem   1 year 1 week ago

With default/unchanged Makefile.dist LibRaw requires zlib only (present in base macOS).

All additional dependencies (libjpeg, RawSpeed, Adobe DNG SDK) are optional and disabled by default.

Reply to: Build problem   1 year 1 week ago

Hi Alex,

Again, thanks for your quick support. I realized, that I had to update the whole brew installation on my mac and also install and upgrade a lot more tools and libraries, like automake or pkg-config, which is mentioned in an earlier post.

Also I had to install libraries, like jasper, or zlib. From a perspective of such an upgraded full fledged development machine, it is hard to judge, what libraries need to be provided with libraw bundled with an app on a plain macos end-user installation.

All dependencies (additional libraries) that are now compiled with libraw obviously do not exist on a barebone macos installation, esp. without additional development tools like XCode and additional add-ons installed using homebrew installation manager.

Is there a list of libraries (DLLs, share libs) that need to be provided together with any application that relies on libraw and not running in a full fledged development machine environment?

It would be a nightmare for a developer of collecting complaints from end-users that quickly refuse to use your app because its not running on a real world mac. :-)

Thanks,

Thilo

Reply to: Build problem   1 year 1 week ago

You need to either install autotools or just use make -f Makefile.dist
(adjust makefile to meet your needs: JPEG comression support, etc)

Reply to: Problem when emulating dcraw document mode   1 year 1 week ago

Thanks for your suggestions! I've decided to directly use the data in rawdata.raw_image. I've realized that the 1 discrepancy might just be a coincidence after testing different raw formats.

Reply to: Problem when emulating dcraw document mode   1 year 1 week ago

And specific followup: there is no document mode in LibRaw::dcraw_process (and dcraw_emu), if you want to get something close, then an exact match of values ​​is not guaranteed with parameters your specified or any other parameter values (in addition to the fact that the black level may differ in some cases)

Reply to: Problem when emulating dcraw document mode   1 year 1 week ago

dcraw -D is 'totally RAW, no scaling'

Just skip processing and use raw data from imgdata.rawdata.raw_image (or color3_image,color4_image).

samples/unprocessed_raw.cpp sample is probably what you're looking for.

Reply to: Add simplest debayer support (superpixel)   1 year 1 month ago

Followup: could you please share some file sample(s) to check if metadata extracted correctly or not

Reply to: Add simplest debayer support (superpixel)   1 year 1 month ago

LibRaw is about RAW data and metadata extraction.

Existing postprocessing code is intended mostly for testing purposes, there is no plans to improve it.

This is clearly stated on this site main page.

Reply to: open_file return -100009 : when path contains french e accent   1 year 1 month ago

Hello Alex !
Thank you for your help.

To make my project LibRaw work (QT / Windows 10) with last release Libraw 0.21.2 and Unicode,
i added these 3 lines in the file libraw.h before compiling Librairy.

# define LIBRAW_WIN32_CALLS
# define __INTEL_COMPILER
# define LIBRAW_WIN32_UNICODEPATHS

May be one or two #define are required for my computer.
So i can open Raw file with a filename QString (16bits)

const wchar_t *array = (const wchar_t*)filename.utf16();
int ret = this->processor->open_file( array) ;
if( ret != LIBRAW_SUCCESS )
return false ;

Best regards,

Luciano

Reply to: open_file return -100009 : when path contains french e accent   1 year 1 month ago

>> I tried various conversions

The wchar_t* string is passed directly to Win32/CreateFileW

So, if you're able to use other Win32 file API calls, it should work for LibRaw too.

UPD: on modern windows, all interfaces are unicode already, starting from wmain/_tmain program 1st function, so there is no need to convert anything from/to 8-bit strings.

Reply to: r5 mark II support   1 year 1 month ago

Our update/release schedule policy is provided on this site homepage: https://www.libraw.org/#updatepolicy

We know nothing about darktable update schedule.

Reply to: Do I need to use dcraw_* api ?   1 year 2 months ago

LibRaw's goal is to read RAW data and metadata, as explained on this site 1st page: https://www.libraw.org/

Postprocessing is indeed imported from dcraw, there is no other postprocessing in LibRaw.
If one want to process RAW data in own code: LibRaw::open_file()/unpack() is enough for that.

Reply to: Do I need to use dcraw_* api ?   1 year 2 months ago

Just looking for a quick comment on what is gained using the non-dcraw API. I have read through most of the documentation and it seems to me that they can achieve similar functionality. I get the impression that the libraw dcraw API was meant to ease migration efforts from the original dcraw.

I don't see an inherent benefit between the two methods reading the the documentation, which is why I'm curious.
I suspect if I were using more of libraw's processing tools it would make sense to use the non-dcraw api, but I'd like to confirm that.

Reply to: Do I need to use dcraw_* api ?   1 year 2 months ago

Do you have a specific question or do you asking to re-tell the entire documentation in other words?

Reply to: Do I need to use dcraw_* api ?   1 year 2 months ago

I wasn't sure if the other methods are perhaps faster or have better support. I just want to make sure I understand what options exist and why I would use one over the other.

Reply to: Do I need to use dcraw_* api ?   1 year 2 months ago

If everything works for you and you are happy with the result, what else do you want to improve?

Reply to: If I have bayer data, how to process it to get the image?   1 year 4 months ago

and, also, samples/unprocessed_raw sample

Reply to: If I have bayer data, how to process it to get the image?   1 year 4 months ago

Thanks for the info.

I've another question which is the other way around:

Can I decompress a compressed Fuji RAF file and get the uncompressed X-Trans sensor data buffer from LibRaw?

Do I call unpack() and then get the uncompressed sensor data from somewhere?

Is it in rawProcessor.imgdata.rawdata?

Reply to: LibRaw with Adobe DNG SDK 1.7   1 year 4 months ago

I've tried all the options that could make a difference, but there are not that many options in the Librarian when compiling LibRaw as a static lib.

I've settled to compile LibRaw with Ox instead O2 and that works just fine. Maybe it's a tick slower than it could, but I think it's fine.

Do you have a big spam problem? The post form always tells me to take more time filling the form. Maybe I type too fast ;-)

Reply to: LibRaw with Adobe DNG SDK 1.7   1 year 4 months ago

This is not string pooling, this should be linker identical code folding (designed to merge same methods of different classes, e.g. templates)
So, two originally different function pointers are the same in the optimized code.

We'll return to this but not immediately

Reply to: LibRaw with Adobe DNG SDK 1.7   1 year 4 months ago

Tried the linker option. No change.
This is not available for libraries (I link LibRaw as a static lib). But setting the options in my DLL which links to LibRaw made no change.

I've also played with string pooling and the other options that differ (https://learn.microsoft.com/en-us/cpp/build/reference/o1-o2-minimize-siz...) between Optimization (Speed) which works and Maximize Optimization (Speed) which does not work. Without any success.

I'll stick to /Ox /Ob2 /Oi /Ot for now.

Reply to: LibRaw with Adobe DNG SDK 1.7   1 year 4 months ago

Looks like this is linker option, not compiler: https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-...(v=vs.110)?redirectedfrom=MSDN

/OPT:NOICF should help.

We'll try to address this issue in some way, but not immediately (will try to use #pragma comment(linker...)

Pages