sampleicc-developer Mailing List for SampleIcc
Brought to you by:
maxderhak
You can subscribe to this list here.
2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Kai-Uwe B. <ku...@gm...> - 2011-06-17 05:10:04
|
Sorry for the late reply. Please see my forum answere. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org Am 16.06.11, 14:31 -0400 schrieb Gilbert Soucy: > I am trying to build SampleICC on RedHat but I have a few problems. I posted > a message on the SampleICC forum ( > https://sourceforge.net/projects/sampleicc/forums/forum/437771/topic/4575184 |
From: Gilbert S. <gs...@36...> - 2011-06-16 18:55:40
|
Hello, I am trying to build SampleICC on RedHat but I have a few problems. I posted a message on the SampleICC forum ( https://sourceforge.net/projects/sampleicc/forums/forum/437771/topic/4575184 ) but I see very little activity so I fear that my message will go unnoticed. What it is the preferred way to get help to build the project? Should I post my question here on this email list or does someone actually replies to the questions on the forum (but I dont see much sign of that right now)? Thanks Gilbert |
From: Kai-Uwe B. <ku...@gm...> - 2010-07-31 08:38:58
|
Hello, I started a small pkg-config file to let other projects know about SampleICC in te open source way: -------------------8<----------------------------- Name: sampleicc Description: ICC profiles i/o and manipulating library and CMM Libs: -L${libdir} -lSampleICC -lm Cflags: -I${includedir}/SampleICC -------------------8<----------------------------- I would guess lower letter for the project "sampleicc" is fine. The Cflags point to the subdirectory. This allows to include the headers without a prefix and switch the actual library on compile time by changing the include path. I think thats good practise. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
From: Dan P. <Dan...@ff...> - 2010-02-02 12:01:17
|
In ICCTagLut.cpp rev 189 line 986 there is: delete m_dParam; However it seems to me that m_dParam is always allocated elsewhere with new[] Shouldn't this line be: delete [] m_dParam; Dan ______________________________________________________________________ CONFIDENTIALITY AND DISCLAIMER NOTICE This message and any attachment is confidential and is protected by copyright. If you are not the intended recipient, please email the sender and delete this message and any attachment from your system. Dissemination and or copying of this email is prohibited if you are not the intended recipient. We believe, but do not warrant, that this email and any attachments are virus free. You should take full responsibility for virus checking. No responsibility is accepted by FFEI Ltd for personal emails or emails unconnected with FFEI Limited's business. ______________________________________________________________________ |
From: Kai-Uwe B. <ku...@gm...> - 2007-12-11 22:27:40
|
On non osX I get an error about missing #include <CoreFoundation/CoreFoundation.h>, which is osX specific. A unix patch is provided to the SourceForge facilities: http://sourceforge.net/tracker/index.php?func=detail&aid=1744211&group_id=128792&atid=712818 best regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
From: Kevin W. <hx...@ci...> - 2006-11-24 15:10:09
|
Hi, I just grabbed rev 56 of trunk and ran across an issue when building on a case sensitive system. Is IccTagMPE.h or IccTagMpe.h the preferred form? The file in SVN is uppercased but the include's are mixed. Also the Makefile in Tools/CmdLine/IccV4ToMPE/ is looking for the wrong case iccV4ToMPE.cpp vs iccV4ToMpe.cpp. And a couple of minor warning suppressing updates to IccProfLib/IccMpeACS.h IccProfLib/IccMpeBasic.h IccProfLib/IccMpeFactory.h IccProfLib/IccTagMPE.h Tools/CmdLine/IccToolUtilsLib/CLUT.cpp by adding an end-of-line at the end of the files would clean up the warning status when built under gcc 4.0.2 at least. Thanks Kevin -- | Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this | | Senior Technology | My employer for certain | | And Network Systems Architect | Not even myself | |
From: Dalai F. <dfe...@gm...> - 2006-02-17 19:58:30
|