Moin Moin, after I had a detailed look into cgo and libdarktable yesterday, we decided to continue using darktable-cli as this doesn't interfere with our build process on other operating systems and leaves the option open to use alternative raw converters, should darktable not be available (sips, Photivo, RawTherapee, digiKam,...):
https://github.com/photoprism/photoprism/wiki/Converting-RAW-to-JPEG We are grateful for every little piece of advice concerning XMP sidecar files and you are welcome to write in our wiki. I still don't understand how compatible Darktable is with Adobe Lightroom and other applications supporting XMP. Would you always get a similar JPEG file with the same XMP file? I guess it depends on which filters are supported/used and if they have the same name? You've probably seen this before, but for us it was quite impressive to see Darktable running in a browser using the broadway display server (couldn't resist to experiment after cloning your repo): https://twitter.com/browseyourlife/status/1061673399741759489 The exit code for darktable-cli --version is already fixed, pull request was accepted quickly. Thank you! Michael On Sat, Nov 10, 2018 at 4:17 PM, Michael Mayer <mich...@liquidbytes.net> wrote: > Thank you! > > Some users were asking for a single binary they can download and run. > I already figured that's going to be complicated after I checked the > dependencies of libdarktable.so, also there is no statically linkable > version of libtensorflow.so yet. > > At least we want to provide a small docker image with only the files > that are actually needed - are there parts of a default darktable > installation we can safely delete? > > Michael > > On Sat, Nov 10, 2018 at 3:16 PM, johannes hanika <hana...@gmail.com> wrote: >> hi! >> >> looks like an interesting project you're working on. >> >> if you have a look at the source of darktable-cli, it's really short: >> >> https://github.com/darktable-org/darktable/blob/master/src/cli/main.c >> >> you could probably link your code directly to libdarktable.so the same >> way. i don't understand your build constraints or why you'd prefer >> static linkage. i guess linking against some form of libdarktable.a >> statically might be doable, but we heavily depend on loadable modules >> which are dlopen()ed by us manually (that includes our image >> operations but also the system's opencl libraries). i doubt linking >> all that statically is possible without major changes to the codebase >> (or a good idea, for that matter). >> >> cheers, >> jo >> On Sat, Nov 10, 2018 at 11:16 AM Michael Mayer <mich...@liquidbytes.net> >> wrote: >>> >>> Hello everyone, >>> >>> I'm the maintainer of https://photoprism.org/, a server-based photo >>> management application based on Go and TensorFlow. >>> >>> We use darktable-cli to convert RAW files to JPEG: >>> >>> https://github.com/photoprism/photoprism/blob/develop/internal/photoprism/converter.go#L87 >>> >>> While this works, it would be amazing if we could (statically?) link >>> against darktable using cgo. I'm wondering if anyone has experience >>> with that or if you recommend to continue using darktable-cli? >>> >>> Also it seems like I found a bug (which I haven't found out how to >>> report properly yet): >>> >>> # darktable-cli --version >>> this is darktable-cli 2.4.4 >>> # echo $? >>> 1 >>> >>> -> Should be 0 >>> >>> Thank you for the hard work you put into darktable! >>> >>> Michael >>> ___________________________________________________________________________ >>> darktable developer mailing list >>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org >>> ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
