Marc
> On Nov 30, 2019, at 10:27 AM, John Cowan <[email protected]> wrote: > > On Sat, Nov 30, 2019 at 10:12 AM Marc Feeley <[email protected]> wrote: > > Interesting. I assume the 12K excludes dependent DLLs. Do you know if on > Windows there’s a DLL for the Chicken runtime library and for the C library > (and others), and their size? > > The Chicken DLL is about 3.4MB, of which a good deal will be relocation > tables and such. I'm a Cygwin user, so my C library is included in > cygwin1.dll, which is about the same size (it uses newlib, not glibc, but has > to provide full Posix plus much other Linux stuff). The native Windows C > library, also a DLL, is about 1MB, depending on the OS version; Chicken > provides the same interface on Posix and on Windows, but much of it (fork, > obviously) will throw runtime exceptions on Windows. Of course, Windows > itself is also in DLLs. Chicken does not have a run-on-bare-metal option; > it depends on the presence of either Posix or Windows. Thanks for the information. So the RAM footprint at run time for the executable code (excluding the OS) will be on the order of 12KB + 3.4MB + 3.4MB + 1MB, so about 8MB. I think that is a better measure when estimating the amount of RAM needed to run an application. Of course to this must be added the amount of heap memory used by the program, but that is very application dependent. Marc
