Hi, >I have started a configure-based build environment for LCMS. If an >automated build/install is not acceptable for inclusion in LCMS due to >the increased size, then I will simply distribute it seperately since >I believe that normal users (not just programmers) should be able to >benefit from LCMS.
Of course its acceptable, and will be very welcome. Many people has asked for that :-) You are right, the benefits are far evident and the size of package isn't so important today. Thanks for that. Regards, Marti. ----- Original Message ----- From: "Bob Friesenhahn" <[EMAIL PROTECTED]> To: "Marti Maria" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, June 09, 2003 5:32 PM Subject: Re: [Lcms-user] LCMS is a non-portable "portable" package On Mon, 9 Jun 2003, Marti Maria wrote: > > > In order to install LCMS once must hand-edit include/icc34.h to make > > Unfortunately, this is the header file provided by ICC and I have no > control over it. I have done some slight modifications, but there are > still large problems on it. Hopefully next header will solve some of > them. A few more slight modifications will probably get it over the hump. > >By incorporating a simple configure script like other open source > >packages, LCMS can be made much easier to install on many systems. > >LCMS is a trivial package, so it is quite easy to add the > >configure-based build environment which is standard with other open > >source packages. > > In a very old revision I did that. As a result, the tarball growed about > 3 times original size. I'm searching for alternatives to the huge libtool. > But anyway, I never intended to do a portable *enduser* package. > lcms was, and still is, a tool for programmers. The "portable" comes > because it runs in several, not all, platforms. Perhaps I should fix the > spell in the documentation. It doesn't really matter if the lcms tarball is 3X the original size. What does matter is if it can be properly built and installed so the software can be used. If the software can't be built and installed, then it can't be used. Since LCMS uses the LGPL license, it is highly desirable/necessary to install it is an independent library rather than incorporate it into a dependent package's source code. This means that the library needs to be installed on the target system somehow. If the end-user is not using a system which provides LCMS as a binary package, or the available binary package is too old, then they have to build it from source code. This means that non-programmers are required to configure and compile LCMS. Programmers will also benefit from a simple LCMS install since it is currently very difficult to get LCMS built and installed in 15 different target environments in order to support developmental testing. Out of the 13 library packages that the package I maintain depends on, LCMS is by far the most difficult and time-consuming to get installed. I have started a configure-based build environment for LCMS. If an automated build/install is not acceptable for inclusion in LCMS due to the increased size, then I will simply distribute it seperately since I believe that normal users (not just programmers) should be able to benefit from LCMS. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Lcms-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lcms-user
