Re: compiling

On Wed, 2 Jul 2003, Steve Dekorte wrote:
>
> I don't see what's missing. My programming language project
> (http://www.iolanguage.com) recursively builds jpeg, tiff, etc libs and
> links them with the main executable without any problems. I also

There is quite a bit missing.  In order to build a shared
GraphicsMagick, which is required for modules, and the Perl, Ruby,
Java, Python, etc., extensions, all libraries must be built as shared
libraries.  The libpng package includes dedicated build scripts for 54
environments, the majority of which are Unixish.  Does your scheme
build shared libraries for all those environments?

Another issue is that systems which uses packages may want to use a
package manager rather than building the support libraries from
sources.

> include their source in the release so people don't have to hunt down
> compatible versions (if they're still available) and spend time
> figuring out how to get things to work. I strongly recommend this as
> extra download time is trivial when compared to the human time spent on
> these things.

We do this already for Windows.  The GraphicsMagick Windows source
package would almost work as a set of sources for the delegate
libraries except that some of the headers have been modified to die if
the target is not WIN32.

Bob
======================================
Bob Friesenhahn
[email protected]
http://www.simplesystems.org/users/bfriesen



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01