Very nice!

Am 23. Februar 2020 21:57:34 MEZ schrieb parafin:
>This darktable bug will be fixed (hopefully) in next release.
>
>
>On Tue, 21 Jan 2020 13:54:43 +0000
>Matt Maguire wrote:
>
>> You could put a newer libcups.2.dylib in a separate directory, and
>use a script to run darktable that sets LD_LIBRARY_PATH environment to
>include that new directory (putting the new directory earlier in the
>path than /usr/lib). I wouldn't replace the existing file though,
>because that could break things on your system.
>> 
>> I notice from the README that libcups is an optional dependency that
>is only used for the print module. Another option could be to build a
>new version of darktable that doesn't use the print module. You'd then
>have to do your printing using a different application other than
>darktable. 
>> 
>> On 21/1/20, 9:48 pm, "Subhash Fotografie"
>wrote:
>> 
>>     Thank you very much for your help!
>>     Maybe I can get and use a never version of libcups.2.dylib? Or is
>this dangerous for other applications or even the OS?
>>     
>>     
>>     [Matt Maguire schrieb am 21.1.2020 um
>21:38 Uhr:]
>>     
>>     >Ok, so from the error message I see that one of the libraries on
>your
>>     >system "libcups.2" is missing a symbol expected by the newer
>darktable
>>     >(_cupsEnumDests). This is probably because this symbol was added
>in to
>>     >the library in later versions of the operating system, but now
>darktable
>>     >is claiming to depend on it. The devs might be able to tweak the
>code to
>>     >remove this dependency (if it is not really required), otherwise
>it
>>     >looks like the later versions of darktable may not be compatible
>with
>>     >OSX 10.7.x anymore :-(    

-- 
Subhash Fotografie
Schwarzenau
http://fotoblog.subhash.at
Fotografie | Digitales Imaging
Bildbearbeitung | Workshops
• • • • • • • • • • • • • • • • • • • • • • •
Sent from my FairPhone
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to