using_chicken_on_sdf
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
using_chicken_on_sdf [2021/03/17 20:42] – [Install Eggs] hc9 | using_chicken_on_sdf [2021/03/17 20:52] (current) – [Learn] hc9 | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Learn ===== | ===== Learn ===== | ||
- | To learn Scheme programming, | + | To learn Scheme programming, |
To learn about Chicken, check out the [[http:// | To learn about Chicken, check out the [[http:// | ||
Line 11: | Line 11: | ||
===== Play Around ===== | ===== Play Around ===== | ||
- | To play with Chicken, start the interactive interpreter by running csi. It should look like this: | + | To play with Chicken, start the interactive interpreter by running |
< | < | ||
Line 40: | Line 40: | ||
===== Install Eggs ===== | ===== Install Eggs ===== | ||
- | The Chicken community produces third-party libraries called eggs. (If you're familiar with the Ruby programming language, eggs are like Ruby's gems.) As an example, let's install the [[http:// | + | The Chicken community produces third-party libraries called |
- | Ideally, you could just run chicken-install readline and the egg would be installed. But if you do that, you'll get an error. Since you don't have administrator privileges on SDF, you can't install eggs to the default location (a system directory). You must install the eggs in your home directory, which requires you to do a little configuration beforehand. I'll show you how to do that. | + | Ideally, you could just run '' |
I'll assume you're running Bash as your shell and that you want to keep Chicken-related files in ~/chicken. First create a directory for a Chicken repository: | I'll assume you're running Bash as your shell and that you want to keep Chicken-related files in ~/chicken. First create a directory for a Chicken repository: | ||
+ | < | ||
mkdir -p ~/ | mkdir -p ~/ | ||
+ | </ | ||
Then install the repository: | Then install the repository: | ||
+ | < | ||
chicken-install -init ~/ | chicken-install -init ~/ | ||
+ | </ | ||
Then create some environment variables so Chicken will know to use your new repository for eggs, and will compile against SDF's system libraries when installing eggs: | Then create some environment variables so Chicken will know to use your new repository for eggs, and will compile against SDF's system libraries when installing eggs: | ||
- | export CHICKEN_INCLUDE_PATH=${HOME}/ | + | < |
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
(You may also wish to put the above lines in a shell startup file, like ~/ | (You may also wish to put the above lines in a shell startup file, like ~/ | ||
Line 60: | Line 68: | ||
Now you can install the readline egg: | Now you can install the readline egg: | ||
+ | < | ||
chicken-install readline | chicken-install readline | ||
+ | </ | ||
- | If the install was successful, we can check whether everything' | + | If the install was successful, we can check whether everything' |
'' | '' |
using_chicken_on_sdf.1616013773.txt.gz · Last modified: 2021/03/17 20:42 by hc9