0.17 is latest public code.
We do not push 'work in progress' code to github, but use own private repo for it. Only big pieces, known to work (in our RawDigger/FastRawViewer) are pushed.
Thank you for clarification, that makes sense now. I'm using LibRaw under Mac with Xcode/clang and have lots of warnings (>150), so I'm considering to fix them or not. It is worth doing only if fixes are mainlined somehow.
LibRaw's internal/* files are generated from (patched) dcraw.c source.
If the warnings are from this code (dcraw_common.cpp, dcraw_fileio.cpp), your changes will *not* be merged into main LibRaw source because changing of these files will broke dcraw auto-import.
0.17 is latest public code.
0.17 is latest public code.
We do not push 'work in progress' code to github, but use own private repo for it. Only big pieces, known to work (in our RawDigger/FastRawViewer) are pushed.
Expect big github update in 2-3 weeks or so.
-- Alex Tutubalin @LibRaw LLC
Thank you for clarification,
Thank you for clarification, that makes sense now. I'm using LibRaw under Mac with Xcode/clang and have lots of warnings (>150), so I'm considering to fix them or not. It is worth doing only if fixes are mainlined somehow.
LibRaw's internal/* files are
LibRaw's internal/* files are generated from (patched) dcraw.c source.
If the warnings are from this code (dcraw_common.cpp, dcraw_fileio.cpp), your changes will *not* be merged into main LibRaw source because changing of these files will broke dcraw auto-import.
-- Alex Tutubalin @LibRaw LLC
Then I think it's not worth
Then I think it's not worth it :)