Re: [Chicken-users] porting eggs experiences and questions
Jörg F. Wittenberger wrote: > Apparently chicken-install passes the -n switch down to the dependencies it > need to install. I reported the same thing on IRC today. I think it makes sense and would like to have a switch that instructs chicken-install to *only* build, and install if -n is not present, the egg’s dependencies. I had to resort to some trickery when making an easy build script for Ensemble, and would have liked such a command flag. https://www.upyum.com/cgit.cgi/ensemble/tree/build.sh?id=78d4597062984bcaa81279fe79d1be0c90a8970a See extract_dependencies() and build_normal_deps() ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] functor support (C5)
Hi all, I tried to package an egg exporting a functor. for reference here: https://github.com/0-8-15/ldif-sexpr `include` is literally copied to the .import.scm file The actual code of the functor is in its own file, which is included here https://github.com/0-8-15/ldif-sexpr/blob/master/ldif-core.scm around line 33. This results in the include directive ending up compiled into the import library. Importing and instancing the functor will work if, and only if, the named file is found. Along whatever search path whatever content is found. Intuitively I'd say this defeats the idea of compiling the import library in the first place. BTW: Did anything change about the line number information with Chicken 5? If so, I would have to re-check. Last time, maybe about a year ago when I tried Chicken 4 functor instances where a pain in the butt when it comes to error messages. Line numbers pertaining to errors within functors where always be given as the line of the functor instantiation. Best /Jörg ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] porting eggs experiences and questions
Hi all, in the meantime I understood why chicken-install would not install dependencies: chicken-install -n While messing around I did not want the egg in the current directory to be installed. Just the dependencies. Apparently chicken-install passes the -n switch down to the dependencies it need to install. Those are then not installed, which makes chicken-install barf at the depending eggs. Maybe it makes more sense to have the -n switch only in effect for the egg in the current directory while still installing dependencies. Best /Jörg On Aug 17 2018, Jörg F. Wittenberger wrote: * Observation: chicken-install does not install dependencies This is just odd: The .egg file contains (dependencies srfi-18); chicken-install did the download but not install it. So compilation failed until I manually did chicken-install srfi-18 That's weird. We don't observe this behavior on any of the automated tests (http://tests.call-cc.org). It is. But it seems consistent in my setup. I tried: `chicken-install srfi-13`: this did the download for srfi-14 compiled and failed to install srfi-13. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Like 'include', but different?
Mark Carter wrote: > I have code where I 'include' other files. Suppose I compile that file. > As part of execution, it will try to load those other files, which isn't > what I want. > > Is there a way of telling chicken that during the interpretation or > compilation, the file should be loaded, but during execution, don't load > the files? > The `include` form should be what you need here. I don’t really understand the problem you’re having. Could you post a little example of it? Here is how (include "file.scm") should behave: - when compiled, the include form will be rewritten with the content of the specified file - when interpreted, it will behave like (load "file.scm") ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
