Yes, I read the manual. All of the examples seem to be a linux host with .so files. Windows uses .dll files.
When I try to deploy a static build of the exe, it makes an exe, and the size makes you think it has bundled any dependencies like numbers (from 77kb to 1.6mb), but on MinGW64-32 bit, it hasn't. If you try and run the exe on a different Windows box, or through a non-MinGW command line on the same Windows box, it complains it cannot find the numbers extension. My guess is that it has statically linked and bundled libchicken.dll in the exe, but not the numbers extension that is in a '(use numbers)' statement in the source file.
If I simply compile the file in the MinGW command line, the exe works perfectly. It knows where to find the numbers library it needs, my guess from the CHICKEN install directory. The program works. What I am trying to do is make a static exe with the dependencies all in the exe. This way I can give it to somebody who is not a programmer and does not have CHICKEN installed, to run as is. Later I would like to dynamically compile, so the user only needs the libchicken.dll once, but I would like to statically link any program-specific libs (like numbers). This way the user only needs one copy of libchicken.dll in a directory, and any exe I send them will have the oddball dependencies statically linked right in the exe.
For instance, the same program on a Gambit-C MinGW64-64 bit system is compiled: "gsc -exe "file.scm"" The resulting exe (4 mb) runs to whomever I send it on their Windows box. It includes all of what it needs, i.e. the gambit runtime dll, and any libs (like numbers). I guess they made Gambit-C more Windows friendly, but it alas it does not have the packages CHICKEN has. On the other hand, if the packages (eggs) only work if you have MinGW64-32 bit installed with a CHICKEN dev environment, it sort of defeats the purpose of being able to create stand alone exe files.