On 2014-03-18 12:32 +0100, Daniel Macks wrote:
On Tue, 18 Mar 2014 00:35:48 -0700, Bryce Harrington <bryce@...961...> wrote:
Identify any critical OSX/Win32 packaging issuesconfigure.ac still only accepts lcms (not lcms2) on OS X, with embedded comment "lcms 2.2 & 2.3 have problems on OSX". Upstream now has lcms 2.4; is the problem still present? I don't see a link to a bug report or discussion to be able to know what the problem is.
Discussed in the comments of these reports: - https://bugs.launchpad.net/inkscape/+bug/1133014 - https://bugs.launchpad.net/inkscape/+bug/1239370
Request to migrate OS X port to lcms2 tracked in: - https://bugs.launchpad.net/inkscape/+bug/1024344
AFAICT building with lcms1 or with lcms2 on OS X seems ok (personally tested on OS X 10.7.5, with trunk only), as long as there are not both libraries loaded at runtime (pulled in by another shared library, or due to overlinking (e.g. in earlier MacPorts versions)).
Regards, V