Understanding color management better has been on my todo list, and while I haven't really gotten to it, I want to say thank you for all your work and happy anniversary.
I am currently the maintainer of the pkgsrc entry for lmcs (as graphics/lcms). pkgsrc is used on NetBSD and Dragonfly, and people also use it on other systems, perhaps most notably Solaris. On the web page you could add a link to www.pkgsrc.org with "(graphics/lcms)" after it. (I've done very little real work, so please don't credit me.) http://www.littlecms.com/lcms-2.0preview-11-2-2008.zip This is an early preview, no documentation, just a couple of utilities, no build system, bugs, etc. *but*: the library code is complete. There is a extensive testbed too. I don't know what you are thinking about build system. The way lcms 1.17 builds seems good to me -- autoconf is very portable, even if people think it's a bit crufty -- with windows on the side. More importantly, packaging systems support it, and I think ease of use by packaging systems is an important consideration, since most people run most software via packaging systems of some kind. There have been a number of build systems du jour, such as scons and cmake, and over the years I've come to believe that most of these are in practice less desirable because they don't have builtin support in all packaging systems. (Of course this is a difficult situation for improving build systems in general.) I consider myself competent autoconf/automake and will try to help out if you go that route and have issues. You didn't say if the published API and ABI will change. If the API changes, I'd strongly encourage you to use new names, perhaps liblcms2, so that old lcms and new lcms can both be installed. There will be a long period, perhaps a few years, over which depending programs change to lcms2, release new versions with the switch, and then those versions make it into packaging systems. Having both with different names means these switches can happen one at a time without needing synchronization, and that both versions can end up linked in the same program (for example if ufraw switches before gimp). FYI, here is the control file for pkgsrc, which is pleasingly small (a huge part of this is omitted because GNU_CONFIGURE=yes tells pkgsrc to call configure with the right options and that make/make install works as expected). I should reconsider the zlib situation (pkgsrc has a rule that packages should only depend on other things explicitly, so that binary packages work on other systems). ---------------------------------------- # $NetBSD: Makefile,v 1.26 2008/11/01 13:40:34 gdt Exp $ DISTNAME= lcms-1.17 PKGREVISION= 1 CATEGORIES= graphics MASTER_SITES= http://www.littlecms.com/ MAINTAINER= [EMAIL PROTECTED] HOMEPAGE= http://www.littlecms.com/ COMMENT= Little Color Management System -- a color management library PKG_INSTALLATION_TYPES= overwrite pkgviews PKG_DESTDIR_SUPPORT= user-destdir GNU_CONFIGURE= yes USE_LIBTOOL= yes TEST_TARGET= check # This is very MIT-like, but perhaps not the exact text. #LICENSE= lcms-license # lcms does not need zlib, but will look for it and link it to tifficc # if present. Therefore, we don't enjoin lcms from finding zlib, but # don't include it via bl3. # Avoid an ICE in gcc2 on sparc64 CONFIGURE_ENV+= F77=${FALSE:Q} PKGCONFIG_OVERRIDE= lcms.pc.in INSTALLATION_DIRS+= share/doc/lcms post-install: .for _f_ in LCMSAPI.TXT TUTORIAL.TXT ${INSTALL_DATA} ${WRKSRC}/doc/${_f_} ${DESTDIR}${PREFIX}/share/doc/lcms/${_f_} .endfor .include "../../graphics/jpeg/buildlink3.mk" .include "../../graphics/tiff/buildlink3.mk" .include "../../mk/bsd.pkg.mk"
pgpZSECq8ziOM.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
