[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Patch: Many composite/blend modes mostly compatible to Adobe
From: David REVOY <davidrevoy () gmail ! com>
Date: 2011-01-29 15:30:58
Message-ID: 4D4432B2.2060103 () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
> @Boud :what is your problem when trying to compile?
Just the problem is I don't know a lot of things about "how to do it" ;
I was just a script user of the SVN version. Animtim was nice and sent
me keys code lines to do it, but I spent hours without results because
folders in 'calligra' are really different than in 'koinstall'. It
surely sounds stupid for you :) I will surely try again. If I update
using old script of SVN, it will be 2.3.1 ? Thanks for your replies.
> @Silvio Heinrich : if gimp really uses just HSV then it is not really
> superior.
Oh, I really don't know nothing about how and why color modes prefer use
HSV or HSL luma , I'm just a digital painter user. The only feedback I
can give are with pictures like the previous mail :-)
Btw, you are right , my use of 'superior' word needs to be explain : the
color mode in Photoshop ( I used it for years too) don't work nicely
with yellow/orange tones painting over gray. You obtain only a muddy
green/yellowish tones. That's why I called the Gimp one 'superior' ;
because if you use it as a painter to recolor a part and like to use
yellow or orange ; the Gimp one will be more efficient for this case.
That's why I always prefered the way Gimp handle it than Photoshop.
Just to defend that the two way are usefull :) and I agree and like if
you planed to support more then one color model. Good way ! and thanks
for the link.
--David
On 01/29/2011 01:30 PM, Silvio Heinrich wrote:
> Hmm.. ok. I don't know what color model gimp exactly uses for this but
> i thought gimp uses HSV.
> It would be nice if you could tell me more about the way how gimp does
> it (of course only if you know).
> But if gimp really uses just HSV then it is not really superior. It's
> just a matter what you want to do in which way.
> I paint myself (and i'm not too bad i would say :D) and for me the
> photoshop way is working much better.
> It was not my intend to simply remove something. The other color mode
> is still there it's just not in the list.
> I actually planed to support more then one color model so krita is
> compatible to photoshop and gimp (i also included the "Grain Merge"
> and "Grain Extract" modes for this reason).
> If you want to know the advantages and disatvantages of HSL and HSV
> please read this:
> http://en.wikipedia.org/wiki/HSL_and_HSV#Disadvantages
> Photoshop uses the HSL luma variant.
> And as far as i know gimp uses HSV (but please correct me if i'm wrong
> and give me some feedback how gimp2.6 is doing it :D)
> On 01/29/2011 10:41 AM, David REVOY wrote:
>> Hi,
>>
>> Just to react on this :
>>> and "Color" modes work exactly as in Photoshop
>> Just to inform the way 'color mode' works in Gimp 2.6 is superior to
>> the 'color mode' of Photoshop ( till Cs2 for sure ).
>> This can be tested & seen with comparing the same file open like this :
>> http://www.davidrevoy.com/XYZ/color-mode_test_GIMP-net.jpg
>> http://www.davidrevoy.com/XYZ/color-mode_test_TOSHOP-net.jpg
>> useless to say that Gimp color mode is far superior for artist than
>> Photoshop. I understand the photoshop one should be proposed for
>> compatibility, but for efficiency ; please don't omit one like Gimp.
>> I couldn't try it with Krita , btw*
>>
>> The PSD file if you need to test ( this file can be considered as
>> 'public domain' if you need it ) :
>> http://www.davidrevoy.com/XYZ/color-mode_test.psd.zip
>> ;-)
>>
>> -David
>> ( PS : can't compile since Git or install 2.3 threw PPA , as i'm
>> Lucid Lynx LTS user not Maverick ...so I wait kubuntu backport to
>> post the bin for Lucid 64bit )
>>
>> On 01/28/2011 10:52 PM, Sven Langkamp wrote:
>>> On Wed, Jan 12, 2011 at 11:17 PM, Silvio Heinrich <plassy@web.de
>>> <mailto:plassy@web.de>> wrote:
>>>
>>> Phew... I think I've gone a bit mad with the blending modes :D.
>>> I added a few. When counting everything together there should be
>>> nearly 40 compositing modes now.
>>> All modes should trait partly transparent layers as Photoshop is
>>> doing it and all modes should
>>> respect the channel flags.
>>> But there are two problems with this patch:
>>>
>>> 1. I used a pretty generic approach. So it relies on the
>>> compiler to do proper inlining. And i didn't use the optimized
>>> multiply functions. I had a few problems with those functions,
>>> because it seems the give no correct results but approximations.
>>> So I still need to check out which composite modes will work
>>> with the optimized functions. I just want to say that it could
>>> be that this is a bit/much slower then the current
>>> implementation (i don't know how much time you spend in
>>> optimizing this).
>>> I personally haven't noticed any speed impact but I've got a
>>> 3GHz quad core, so i think i will be the last
>>> who will notice this.
>>>
>>> 2. The "Hue" and "Saturation" modes are not working correctly
>>> but the "Luminosity" and "Color" modes work exactly as in
>>> Photoshop. I coded the algorithms after the ISO 3200-1 spec.
>>> Adobe released the texts they gave to the ISO committee for
>>> specification. You can find them here:
>>> http://www.adobe.com/devnet/pdf.html
>>> http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf
>>> (direct link)
>>>
>>> go to the category "Transparency" -> "Basic Composition
>>> Computations". This spec is of course for PDFs but it seems that
>>> Photoshop uses the same formulas.
>>> Since "Luminosity" and "Color" modes are working i think i made
>>> some mistake in implementing the
>>> "setSat" function (on page 327). Maybe someone else has an
>>> enlightenment, because I'm working in the dark right now :D.
>>>
>>> But apart from this two problems everything else should work
>>> fine (hopefully).
>>>
>>>
>>>
>>> I tried to build the branch but I get this error:
>>> Linking CXX shared library ../../lib/libpigmentcms.so
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In function
>>> `unsigned short cfVividLight<unsigned short>(unsigned short,
>>> unsigned short)':
>>> KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
>>> short cfVividLight<unsigned short>(unsigned short, unsigned
>>> short)]+0x31): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::unitValue'
>>> KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
>>> short cfVividLight<unsigned short>(unsigned short, unsigned
>>> short)]+0x3d): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::zeroValue'
>>> KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
>>> short cfVividLight<unsigned short>(unsigned short, unsigned
>>> short)]+0xb3): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::zeroValue'
>>> KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
>>> short cfVividLight<unsigned short>(unsigned short, unsigned
>>> short)]+0xbf): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::unitValue'
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In function
>>> `unsigned short cfDivide<unsigned short>(unsigned short, unsigned
>>> short)':
>>> KoLabColorSpace.cpp:(.text._Z8cfDivideItET_S0_S0_[unsigned short
>>> cfDivide<unsigned short>(unsigned short, unsigned short)]+0x25):
>>> undefined reference to `KoColorSpaceMathsTraits<unsigned
>>> short>::zeroValue'
>>> KoLabColorSpace.cpp:(.text._Z8cfDivideItET_S0_S0_[unsigned short
>>> cfDivide<unsigned short>(unsigned short, unsigned short)]+0x31):
>>> undefined reference to `KoColorSpaceMathsTraits<unsigned
>>> short>::unitValue'
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In function
>>> `unsigned short cfArcTangent<unsigned short>(unsigned short,
>>> unsigned short)':
>>> KoLabColorSpace.cpp:(.text._Z12cfArcTangentItET_S0_S0_[unsigned
>>> short cfArcTangent<unsigned short>(unsigned short, unsigned
>>> short)]+0x25): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::zeroValue'
>>> KoLabColorSpace.cpp:(.text._Z12cfArcTangentItET_S0_S0_[unsigned
>>> short cfArcTangent<unsigned short>(unsigned short, unsigned
>>> short)]+0x31): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned short>::unitValue'
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
>>> function `unsigned char cfVividLight<unsigned char>(unsigned char,
>>> unsigned char)':
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
>>> char cfVividLight<unsigned char>(unsigned char, unsigned
>>> char)]+0x27): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::unitValue'
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
>>> char cfVividLight<unsigned char>(unsigned char, unsigned
>>> char)]+0x33): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::zeroValue'
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
>>> char cfVividLight<unsigned char>(unsigned char, unsigned
>>> char)]+0x97): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::zeroValue'
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
>>> char cfVividLight<unsigned char>(unsigned char, unsigned
>>> char)]+0xa3): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::unitValue'
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
>>> function `unsigned char cfDivide<unsigned char>(unsigned char,
>>> unsigned char)':
>>> KoRgbU8ColorSpace.cpp:(.text._Z8cfDivideIhET_S0_S0_[unsigned char
>>> cfDivide<unsigned char>(unsigned char, unsigned char)]+0x21):
>>> undefined reference to `KoColorSpaceMathsTraits<unsigned
>>> char>::zeroValue'
>>> KoRgbU8ColorSpace.cpp:(.text._Z8cfDivideIhET_S0_S0_[unsigned char
>>> cfDivide<unsigned char>(unsigned char, unsigned char)]+0x2d):
>>> undefined reference to `KoColorSpaceMathsTraits<unsigned
>>> char>::unitValue'
>>> CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
>>> function `unsigned char cfArcTangent<unsigned char>(unsigned char,
>>> unsigned char)':
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfArcTangentIhET_S0_S0_[unsigned
>>> char cfArcTangent<unsigned char>(unsigned char, unsigned
>>> char)]+0x21): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::zeroValue'
>>> KoRgbU8ColorSpace.cpp:(.text._Z12cfArcTangentIhET_S0_S0_[unsigned
>>> char cfArcTangent<unsigned char>(unsigned char, unsigned
>>> char)]+0x2d): undefined reference to
>>> `KoColorSpaceMathsTraits<unsigned char>::unitValue'
>>> collect2: ld returned 1 exit status
>>> make[2]: *** [lib/libpigmentcms.so.8.0.0] Fehler 1
>>> make[1]: *** [libs/pigment/CMakeFiles/pigmentcms.dir/all] Fehler 2
>>> make: *** [all] Fehler 2
>>>
>>>
>>> _______________________________________________
>>> kimageshop mailing list
>>> kimageshop@kde.org
>>> https://mail.kde.org/mailman/listinfo/kimageshop
>>
>>
>> _______________________________________________
>> kimageshop mailing list
>> kimageshop@kde.org
>> https://mail.kde.org/mailman/listinfo/kimageshop
>
>
> _______________________________________________
> kimageshop mailing list
> kimageshop@kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote type="cite">
<pre wrap="">@Boud :what is your problem when trying to compile?</pre>
</blockquote>
Just the problem is I don't know a lot of things about "how to do
it" ; I was just a script user of the SVN version. Animtim was nice
and sent me keys code lines to do it, but I spent hours without
results because folders in 'calligra' are really different than in
'koinstall'. It surely sounds stupid for you :) I will surely try
again. If I update using old script of SVN, it will be 2.3.1 ?
Thanks for your replies. <br>
<br>
<blockquote type="cite"> @Silvio Heinrich : if gimp really uses just
HSV then it is not really superior.</blockquote>
Oh, I really don't know nothing about how and why color modes prefer
use HSV or HSL luma , I'm just a digital painter user. The only
feedback I can give are with pictures like the previous mail :-)<br>
Btw, you are right , my use of 'superior' word needs to be explain :
the color mode in Photoshop ( I used it for years too) don't work
nicely with yellow/orange tones painting over gray. You obtain only
a muddy green/yellowish tones. That's why I called the Gimp one
'superior' ; because if you use it as a painter to recolor a part
and like to use yellow or orange ; the Gimp one will be more
efficient for this case. That's why I always prefered the way Gimp
handle it than Photoshop.<br>
Just to defend that the two way are usefull :) and I agree and like
if you planed to support more then one color model. Good way ! and
thanks for the link.<br>
<br>
<br>
--David<br>
<br>
On 01/29/2011 01:30 PM, Silvio Heinrich wrote:
<blockquote cite="mid:4D440858.6030908@web.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Hmm.. ok. I don't know what color model gimp exactly uses for this
but i thought gimp uses HSV.<br>
It would be nice if you could tell me more about the way how gimp
does it (of course only if you know).<br>
But if gimp really uses just HSV then it is not really superior.
It's just a matter what you want to do in which way.<br>
I paint myself (and i'm not too bad i would say :D) and for me the
photoshop way is working much better.<br>
It was not my intend to simply remove something. The other color
mode is still there it's just not in the list.<br>
I actually planed to support more then one color model so krita is
compatible to photoshop and gimp (i also included the "Grain
Merge" and "Grain Extract" modes for this reason).<br>
If you want to know the advantages and disatvantages of HSL and
HSV please read this:<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://en.wikipedia.org/wiki/HSL_and_HSV#Disadvantages">http://en.wikipedia.org/wiki/HSL_and_HSV#Disadvantages</a><br>
Photoshop uses the HSL luma variant.<br>
And as far as i know gimp uses HSV (but please correct me if i'm
wrong and give me some feedback how gimp2.6 is doing it :D)<br>
On 01/29/2011 10:41 AM, David REVOY wrote:
<blockquote cite="mid:4D43E0CE.6020001@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
Hi,<br>
<br>
Just to react on this :<br>
<blockquote type="cite">and "Color" modes work exactly as in
Photoshop</blockquote>
Just to inform the way 'color mode' works in Gimp 2.6 is
superior to the 'color mode' of Photoshop ( till Cs2 for sure ).<br>
This can be tested & seen with comparing the same file open
like this :<br>
<a moz-do-not-send="true"
href="http://www.davidrevoy.com/XYZ/color-mode_test_GIMP-net.jpg">http://www.davidrevoy.com/XYZ/color-mode_test_GIMP-net.jpg</a><br>
<a moz-do-not-send="true"
href="http://www.davidrevoy.com/XYZ/color-mode_test_TOSHOP-net.jpg">http://www.davidrevoy.com/XYZ/color-mode_test_TOSHOP-net.jpg</a><br>
useless to say that Gimp color mode is far superior for artist
than Photoshop. I understand the photoshop one should be
proposed for compatibility, but for efficiency ; please don't
omit one like Gimp. I couldn't try it with Krita , btw*<br>
<br>
The PSD file if you need to test ( this file can be considered
as 'public domain' if you need it ) :<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.davidrevoy.com/XYZ/color-mode_test.psd.zip">http://www.davidrevoy.com/XYZ/color-mode_test.psd.zip</a><br>
;-)<br>
<br>
-David<br>
( PS : can't compile since Git or install 2.3 threw PPA , as i'm
Lucid Lynx LTS user not Maverick ...so I wait kubuntu backport
to post the bin for Lucid 64bit )<br>
<br>
On 01/28/2011 10:52 PM, Sven Langkamp wrote:
<blockquote
cite="mid:AANLkTimV1y2uESivXC-PBHcX_9+zpSpC=w2wBYKe1Z8Z@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Wed, Jan 12, 2011 at 11:17 PM,
Silvio Heinrich <span dir="ltr"><<a
moz-do-not-send="true" \
href="mailto:plassy@web.de">plassy@web.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Phew... I think
I've gone a bit mad with the blending modes :D.<br>
I added a few. When counting everything together there
should be nearly 40 compositing modes now.<br>
All modes should trait partly transparent layers as
Photoshop is doing it and all modes should<br>
respect the channel flags.<br>
But there are two problems with this patch:<br>
<br>
1. I used a pretty generic approach. So it relies on the
compiler to do proper inlining. And i didn't use the
optimized multiply functions. I had a few problems with
those functions, because it seems the give no correct
results but approximations. So I still need to check out
which composite modes will work with the optimized
functions. I just want to say that it could be that this
is a bit/much slower then the current implementation (i
don't know how much time you spend in optimizing this).<br>
I personally haven't noticed any speed impact but I've
got a 3GHz quad core, so i think i will be the last<br>
who will notice this.<br>
<br>
2. The "Hue" and "Saturation" modes are not working
correctly but the "Luminosity" and "Color" modes work
exactly as in Photoshop. I coded the algorithms after
the ISO 3200-1 spec. Adobe released the texts they gave
to the ISO committee for specification. You can find
them here:<br>
<a moz-do-not-send="true"
href="http://www.adobe.com/devnet/pdf.html"
target="_blank">http://www.adobe.com/devnet/pdf.html</a><br>
<a moz-do-not-send="true"
href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf"
target="_blank">http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDF32000_2008.pdf</a>
(direct link)<br>
<br>
go to the category "Transparency" -> "Basic
Composition Computations". This spec is of course for
PDFs but it seems that Photoshop uses the same formulas.<br>
Since "Luminosity" and "Color" modes are working i think
i made some mistake in implementing the<br>
"setSat" function (on page 327). Maybe someone else has
an enlightenment, because I'm working in the dark right
now :D.<br>
<br>
But apart from this two problems everything else should
work fine (hopefully).<span style="border-collapse:
separate; color: rgb(0, 0, 0); font-family: Ubuntu;
font-size: 16px; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; text-indent: 0px; text-transform:
none; white-space: normal; word-spacing: 0px;"><span
style="color: rgb(51, 51, 51); font-family:
myriad-pro-1,myriad-pro-2,Helvetica,Arial,sans-serif;
font-size: 12px; line-height: 16px;"></span></span>
</div>
<br>
<br>
</blockquote>
</div>
<br>
I tried to build the branch but I get this error:<br>
Linking CXX shared library
../../lib/libpigmentcms.so &n \
bsp; &nbs \
p; \
&n \
bsp; &nbs \
p; \
&n \
bsp; &nbs \
p; \
<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In
function `unsigned short cfVividLight<unsigned
short>(unsigned short, unsigned
short)': &n \
bsp; &nbs \
p; \
<br> KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
short cfVividLight<unsigned short>(unsigned short,
unsigned short)]+0x31): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::unitValue'<br>
KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
short cfVividLight<unsigned short>(unsigned short,
unsigned short)]+0x3d): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::zeroValue'<br>
KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
short cfVividLight<unsigned short>(unsigned short,
unsigned short)]+0xb3): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::zeroValue'<br>
KoLabColorSpace.cpp:(.text._Z12cfVividLightItET_S0_S0_[unsigned
short cfVividLight<unsigned short>(unsigned short,
unsigned short)]+0xbf): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::unitValue'<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In
function `unsigned short cfDivide<unsigned
short>(unsigned short, unsigned short)':<br>
KoLabColorSpace.cpp:(.text._Z8cfDivideItET_S0_S0_[unsigned
short cfDivide<unsigned short>(unsigned short, unsigned
short)]+0x25): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::zeroValue'<br>
KoLabColorSpace.cpp:(.text._Z8cfDivideItET_S0_S0_[unsigned
short cfDivide<unsigned short>(unsigned short, unsigned
short)]+0x31): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::unitValue'<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoLabColorSpace.o: In
function `unsigned short cfArcTangent<unsigned
short>(unsigned short, unsigned short)':<br>
KoLabColorSpace.cpp:(.text._Z12cfArcTangentItET_S0_S0_[unsigned
short cfArcTangent<unsigned short>(unsigned short,
unsigned short)]+0x25): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::zeroValue'<br>
KoLabColorSpace.cpp:(.text._Z12cfArcTangentItET_S0_S0_[unsigned
short cfArcTangent<unsigned short>(unsigned short,
unsigned short)]+0x31): undefined reference to
`KoColorSpaceMathsTraits<unsigned short>::unitValue'<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
function `unsigned char cfVividLight<unsigned
char>(unsigned char, unsigned char)':<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
char cfVividLight<unsigned char>(unsigned char, unsigned
char)]+0x27): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::unitValue'<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
char cfVividLight<unsigned char>(unsigned char, unsigned
char)]+0x33): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::zeroValue'<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
char cfVividLight<unsigned char>(unsigned char, unsigned
char)]+0x97): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::zeroValue'<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfVividLightIhET_S0_S0_[unsigned
char cfVividLight<unsigned char>(unsigned char, unsigned
char)]+0xa3): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::unitValue'<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
function `unsigned char cfDivide<unsigned char>(unsigned
char, unsigned char)':<br>
KoRgbU8ColorSpace.cpp:(.text._Z8cfDivideIhET_S0_S0_[unsigned
char cfDivide<unsigned char>(unsigned char, unsigned
char)]+0x21): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::zeroValue'<br>
KoRgbU8ColorSpace.cpp:(.text._Z8cfDivideIhET_S0_S0_[unsigned
char cfDivide<unsigned char>(unsigned char, unsigned
char)]+0x2d): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::unitValue'<br>
CMakeFiles/pigmentcms.dir/colorspaces/KoRgbU8ColorSpace.o: In
function `unsigned char cfArcTangent<unsigned
char>(unsigned char, unsigned char)':<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfArcTangentIhET_S0_S0_[unsigned
char cfArcTangent<unsigned char>(unsigned char, unsigned
char)]+0x21): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::zeroValue'<br>
KoRgbU8ColorSpace.cpp:(.text._Z12cfArcTangentIhET_S0_S0_[unsigned
char cfArcTangent<unsigned char>(unsigned char, unsigned
char)]+0x2d): undefined reference to
`KoColorSpaceMathsTraits<unsigned char>::unitValue'<br>
collect2: ld returned 1 exit status<br>
make[2]: *** [lib/libpigmentcms.so.8.0.0] Fehler 1<br>
make[1]: *** [libs/pigment/CMakeFiles/pigmentcms.dir/all]
Fehler 2<br>
make: *** [all] Fehler 2<br>
<br>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
kimageshop mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" \
href="mailto:kimageshop@kde.org">kimageshop@kde.org</a> <a moz-do-not-send="true" \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kimageshop">https://mail.kde.org/mailman/listinfo/kimageshop</a>
</pre>
</blockquote>
<pre wrap=""><fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
kimageshop mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" \
href="mailto:kimageshop@kde.org">kimageshop@kde.org</a> <a moz-do-not-send="true" \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kimageshop">https://mail.kde.org/mailman/listinfo/kimageshop</a>
</pre>
</blockquote>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
kimageshop mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:kimageshop@kde.org">kimageshop@kde.org</a> <a \
class="moz-txt-link-freetext" \
href="https://mail.kde.org/mailman/listinfo/kimageshop">https://mail.kde.org/mailman/listinfo/kimageshop</a>
</pre>
</blockquote>
</body>
</html>
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic