Dependency to unreleased versions
Gilles Caulier
caulier.gilles at gmail.com
Mon Oct 21 18:10:49 BST 2013
Problem already reported here :
https://bugs.kde.org/show_bug.cgi?id=326368
It's completly different issue. Sound like client libraw code (as
libkdcraw) need to be linked to libgomp when libraw OpenMP support is
enabled. As libraw has already resolved OpenMP symbols at packaging
time, why libkdcraw need again to resolve these ?
OpenMP support is internal to libraw. Client code as libkdcraw do not
use OpenMP API. I suspect something wrong in libraw packaging. Under
Mageia, i cannot reproduce the problem...
Gilles Caulier
2013/10/21 Albert Astals Cid <aacid at kde.org>:
> El Dilluns, 21 d'octubre de 2013, a les 09:14:54, Gilles Caulier va escriure:
>> Fixed with this commit :
>>
>> http://commits.kde.org/libkdcraw/6c91e18cedfe5ef37d202f6d0cf4fde1a607a9a9
>>
>> I just tested with official Libraw 0.14.7 from my Mageia Linux box,
>> and all digiKam & co compile fine. It must be the same for the rest of
>> KDE.
>
> Still red on build.kde.org
>
> Can you have a look? http://build.kde.org/view/All/job/libkdcraw_master/
>
> Cheers,
> Albert
>
>>
>> But, as i explain in commit log, in case of Libraw version is <
>> 0.16.0, not all features from Libraw can be used in client
>> applications due to missing libraw-config.h which has be introduced by
>> me in 0.16.
>>
>> Typically, it's not a too much important regression. All default
>> features will work in most of case to demosaic RAW file. Only speed
>> optimization will miss in client applications.
>>
>> I will check under OSX and Windows today, but i'm sure that all will
>> work perfectly...
>>
>> Gilles Caulier
>>
>> 2013/10/21 Gilles Caulier <caulier.gilles at gmail.com>:
>> > 2013/10/21 Albert Astals Cid <aacid at kde.org>:
>> >> El Diumenge, 20 d'octubre de 2013, a les 22:53:22, Gilles Caulier va
> escriure:
>> >>> Soon will be few days. But it will be just a beta release, not a stable.
>> >>>
>> >>> I will try to find a way next week to check libraw < 0.16 with cmake
>> >>> to solve this issue.
>> >>
>> >> Does that mean that:
>> >> * libkdcraw for the 4.12 release will only compile with a beta release
>> >> of
>> >>
>> >> libraw
>> >> or
>> >>
>> >> * libkdcraw for the 4.12 release will compile with both libraw 0.15 and
>> >> a
>> >>
>> >> beta release of libraw?
>> >
>> > I will find a way to support both version, 0.15. and 0.16
>> >
>> > Gilles
>
More information about the kde-core-devel
mailing list