chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-users] Re: cygchicken


From: Brandon J. Van Every
Subject: [Chicken-users] Re: cygchicken
Date: Fri, 14 Jul 2006 12:35:53 -0700
User-agent: Thunderbird 1.5.0.4 (Windows/20060516)

Brandon J. Van Every wrote:
felix winkelmann wrote:


Here a patch for parameters.scm:

79,80c79,80
< (define-constant cygwin-default-dynamic-load-libraries '("cygchicken-0")) < (define-constant mingw-default-dynamic-load-libraries '("libchicken-0"))
---
(define-constant cygwin-default-dynamic-load-libraries '("cygchicken"))
(define-constant mingw-default-dynamic-load-libraries '("libchicken"))


I've pulled this and the other stuff from Darcs. I've built with CMake using Cygwin, and the resulting filenames are called "libchicken". Probably for the excellent reason that I force that name on all platforms. :-) Is "cyg" instead of "lib" some kind of common Cygwin convention I'm unaware of, with tools automatically performing it or some such. Otherwise, the name "cygchicken" strikes me as an incorrect convention. It assumes that Cygwin should be treated differently than the rest of the universe as far as nomenclature. I can imagine historical motives, but are there any currently valid technical motives? There are now 2 ways to build on Cygwin and I don't want to special-case the CMake code unless there's a good reason.

If "cygchicken" is expunged, I assume changes to the ./configure build will be necessary.


The Cygwin CMake build of csi, does "csi -R srfi-1" just fine. So it seems that either cygwin-default-dynamic-load-libraries is not being utilized, or that something somewhere is happy enough to use / convert to "lib" as the prefix.

I do not know who should take responsibility for DLL Hell. I think most Windows developers deal with this by being careful to keep their own "known good" DLLs in their own application directories. Renaming libraries isn't typically the Windows way, but then, Cygwin isn't Windows. Since my motive was just to ensure the Cygwin CMake build works, and it appears to do so, perhaps it's best to let sleeping dogs lie. At least until a Cygwin culturalist is on hand to make a decision and do the work for Cygwin.


Cheers,
Brandon Van Every





reply via email to

[Prev in Thread] Current Thread [Next in Thread]