Thanks for doing this, Christian. I created the original chicken
packages for cygwin years ago, but rarely use it rarely interact with
cygwin on a development level anymore. I use mostly linux at home now,
and scheme is just an occasional hobby for me. Hopefully the community
will benefit
On 12/4/2014 1:16 PM, Mario Domenech Goulart wrote:
Despite being initially cryptic, I'd strongly recommend learning Emacs.
It's a valuable and flexible tool that can be useful in many situations,
not only for editing CHICKEN code. If you are familiar with Lisp
languages (and I assume you are),
Hi Yasuro,
I just verified that the chicken package in the cygwin repo (of which
I am the maintainer) exhibits the same behavior. I haven't had time to
look into it.
For me, the eggs just work. I have yet to even try to make one
myself, so I don't know how far I will get when I get around to
Hey Chicken users,
Chicken is now an official cygwin package!
I am the POC and maintainer for the package. Everything seems to work
well, but I haven't really stressed the system yet. Comments/critiques
welcome.
regards,
Nate T
-- Forwarded message --
From: Nathan Thern [EMAIL
Hello all -
I have been building and using chicken on my cygwin system(s) since
about version 2.3. From reading the users' and hackers' list archives
it seems that John Cowan is the man most responsible for how cleanly
chicken builds on cygwin ... thanks John!
I have packaged chicken as a cygwin
On Mon, Jun 2, 2008 at 3:36 PM, felix winkelmann [EMAIL PROTECTED] wrote:
On Sat, May 31, 2008 at 8:00 PM, Nathan Thern [EMAIL PROTECTED] wrote:
Hi!
I guess this is a bug in our build - thanks for reporting it. BTW, we don't
use
CMake anymore, so this has nothing to do with CMake itself
Hi all-
I just built chicken-3.2.0 on cygwin. The build went just fine, but the
install put the runtime dlls (cygchicken-0.dll and cyguchicken-0.dll) in
/usr/lib rather than /usr/bin. The installation did not work until I moved
the dlls to /usr/bin.
A quick inspection of the makefiles revealed
