Re: [Chicken-users] New egg: hopefully

Am 18.12.2015 um 23:37 schrieb Sudarshan S Chawathe: > Thanks for the updated pointer to the source. > > I installed the egg in the usual way ('chicken-install' in the directory > with the source files) but could not run the included test > (test/run.scm) successfully, although csc compiles it

[Chicken-users] Emacs Geiser trouble

I looked into the archives and found the announcement of Geiser now working with Chicken. However, I'm not getting it to work. I open a .scm file, M-x geiser, choose Chicken. But with every C-x-e, Emacs says No Geiser REPL for this buffer (try M-x run-geiser) Odd because there's the Chicken

Re: [Chicken-users] Emacs Geiser trouble

It probably thinks it's a Guile file and not a Chicken file. When that happens it is looking for a Guile REPL and ignoring your Chicken REPL. To see if this is happening look for the word "Guile" or "Chicken" in the modeline; if you see Guile and not Chicken then things are misconfigured. You

Re: [Chicken-users] New egg: hopefully

Thanks for the update. I see the same behavior with tests/run.scm as before: Compilation with csc is fine, but executing the resulting file 'run' gives exactly the same error as before: Error: assertion failed: (= (obox-v b1) 455) (Detailed error message is same as in my earlier message.) The

[Chicken-users] [ANN] sdl2 and sdl2-image 0.1

Version 0.1 of the sdl2 and sdl2-image eggs are now ready! The sdl2 egg provides bindings to Simple DirectMedia Layer 2 (SDL2), a popular library used in games and other media-rich software. The sdl2-image egg provides bindings to SDL2_image, a library for loading various types of image files

Re: [Chicken-users] [ANN] sdl2 and sdl2-image 0.1

On 2015-12-19 21:19, John Croisant wrote: > Version 0.1 of the sdl2 and sdl2-image eggs are now ready! These look great, and fantastically thorough. Very nice work. FWIW, the sdl2 egg fails to build with gcc-4.6: In file included from sdl2-internals.c:14:0:

Re: [Chicken-users] [ANN] sdl2 and sdl2-image 0.1

Evan Hanson scripsit: > Building with gcc-5 instead worked fine. That's because the default for GCC 5.x is --std=c11 instead of --std=c89. The safest approach is to insert --std=c89 into the build commands. -- weirdo:When is R7RS coming out? Riastradh: As soon as the top is a beautiful

Re: [Chicken-users] How do you compile multiple modules into a single executable?

Hi Josh, I think the following is what you're after. $ cat foo.scm (module foo * (import scheme) (define (foo) 1)) $ cat bar.scm (import foo) (print (foo)) $ csc -c -unit foo -emit-import-library foo foo.scm $ csc -uses

Re: [Chicken-users] How do you compile multiple modules into a single executable?

The `compiling` feature specifier is only expanded when compiling, so something like `(cond-expand (compiling (import foo)) (else (use foo)))` ought to work. To be totally honest, in this specific situation you can actually get away with using just `(use foo)` since the "-uses foo" flag tells csc

Re: [Chicken-users] How do you compile multiple modules into a single executable?

Is there any way to use (cond-expand) to decide whether to (use) or (import) depending on if the program's compiled or not? On Sat, Dec 19, 2015, 20:57 Evan Hanson wrote: > Hi Josh, > > I think the following is what you're after. > > $ cat foo.scm > (module foo *

[Chicken-users] How do you compile multiple modules into a single executable?

So I have file foo.scm, which contains module foo, and file bar.scm which calls (use foo). My question is, how do I compile these both down to a single executable, as opposed to having executable bar, which uses foo.so? I've tried several approaches but I always get errors at compilation, as both

Re: [Chicken-users] [ANN] sdl2 and sdl2-image 0.1

On 12/19/15 11:11 PM, Evan Hanson wrote: FWIW, the sdl2 egg fails to build with gcc-4.6: In file included from sdl2-internals.c:14:0: lib/sdl2-internals/custom-functions.c: In function ‘chickenSDL2_RotateSurface90’: lib/sdl2-internals/custom-functions.c:212:3: error: ‘for’ loop