[Chicken-users] Chicken module and application project source structure

[David Christensen]

chicken-users:

For a noob first project, I would like to write a command-line utility 
in Chicken Scheme:

  Usage: update [options] [src] dst

  Copy file src to file dst if contents are different.
  Read STDIN if src is '-' or if src is omitted.

  Options:
  --create      Create dst if it does not exist (default)
  --nocreate    Exit with error if dst does not exist


I would like to put the functionality into a library source file and put 
the command-line interface into a program source file that includes or 
uses the library.


Is there an convention for Chicken project source directory and file 
structure?


What about toolchain conventions? (E.g. Makefile?)


Is there anything analogous to Perl's h2xs, module-starter, 
ExtUtils::MakeMaker, Module::Build, etc?


David