[Chicken-users] chicken-5

Hi all, I've just begun to port my eggs to chicken-5. It's much simpler than I thought. The reorganisation of the libraries and egg installation system is great. I wish to thank the members of the chicken-team for their excellent job. Well done, guys! One question remains: The .egg file doesn't

[Chicken-users] porting eggs experiences and questions

Hi, I just ported a first egg. (Pigeon-hole, "simple" mailbox with capacity constraint flow control and no timeouts.) * Question: what's about the .release-info This https://wiki.call-cc.org/porting-c4-to-c5 was helpful, but does not mention the release process. How would I mark a release

Re: [Chicken-users] chicken-5

On Aug 17 2018, Juergen Lorenz wrote: Hi all, I've just begun to port my eggs to chicken-5. It's much simpler than I thought. The reorganisation of the libraries and egg installation system is great. I wish to thank the members of the chicken-team for their excellent job. Well done, guys!

Re: [Chicken-users] porting eggs experiences and questions

Hi Jörg, > How would I mark a release for C5? > > Create a new release-info file and let the chicken core team add it to the CHICKEN 5 coop. I both in the same repo, eg nanomsg5.release-info for C5 and nanomsg.release-info for C4. > Any thought on how to have both a C4 and C5 version in the

Re: [Chicken-users] porting eggs experiences and questions

Hi Jörg, On 17 Aug 2018 12:33:28 +0200 Jörg F. Wittenberger wrote: > I just ported a first egg. (Pigeon-hole, "simple" mailbox with > capacity constraint flow control and no timeouts.) > > * Question: what's about the .release-info > > This https://wiki.call-cc.org/porting-c4-to-c5 was

Re: [Chicken-users] porting eggs experiences and questions

Thanks Mario and Kristian for your responses. On Aug 17 2018, Mario Domenech Goulart wrote: I'm maintaining all my eggs in the same repo, same branch, same .release-info file and same versioning scheme for both CHICKEN 4 and 5. That's what I'd want. In my experience, that's not difficult.

[Chicken-users] srfi-34 egg

there is an srfi-34 egg here https://raw.githubusercontent.com/0-8-15/srfi-34/master/srfi-34.release-info https://github.com/0-8-15/srfi-34 which compiles for me with both chicken 4 and chicken 5. Could go to the coop if it is done well. Best /Jörg

[Chicken-users] C5 Type declaration issue

This is an instance of an error I'm getting frequently: /home/u/c5/bin/csc -setup-mode -static -I /home/u/traces/srfi-128 -emit-link-file /home/u/traces/srfi-128/srfi-128.link -host -D compiling-extension -c -unit srfi-128 -D compiling-static-extension -C -I/home/u/traces/srfi-128 -O3 -d2

[Chicken-users] srfi-128 - almost

Let's try an example. I forked the srfi-128 repo here and ported it to chicken 5 https://github.com/0-8-15/srfi-128 The .release-info still points upstream where the pull request went. This appears to install and work. Brings back the question: how would I tell chicken to temporarily consult

[Chicken-users] CHICKEN 5.0.0 release candidate 1 available

Operating system: Ubuntu 18.04 Hardware platform: x86-64 C Compiler: GCC 7.3 Installation works?: yes Tests work?: yes Installation of eggs works?: no. I just tried installing spiffy and some srfi's. No matter what eggs I tried it couldn't find anything. This is a repy to this post:

Re: [Chicken-users] srfi-128 - almost

Hey Joerg, I'm the maintainer for that egg. I'd be happy to review the pull request, but just haven't had time. I can look it over tomorrow if necessary to get things merged in properly. Regards, On August 17, 2018 11:44:17 AM MDT, "Jörg F. Wittenberger" wrote: >Let's try an example. > >I