 | | Re: Library use in LegOS
|
| Jakob "Fepp" Engblom <fepp@ieee.org> wrote in message news:GAr7Gr.2v3@lugnet.com... (...) handled (...) Each program gets it's own copy (...) Hmmmm. Not sure. Wish I knew more about compiler internals... (...) have (...) It's all custom written - (...) (24 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: Library use in LegOS
|
| (...) OK. How are the calls to the kernel resolved? By the makelx program, or by some magical stuff in the linking. I can imagine compiling the kernel, getting a symbol table out, and then when compiling user programs, you use a linker DEFINE or (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: Library use in LegOS
|
| (...) Not sure of the details, but the linker takes the .o file, and the symbol file LegOS.lds, created during the kernel compile, and produces two files; .ds1 & .ds2, which are then passed to makelx to produce the lx file. So it seems the linker (...) (24 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)
| | | | | Re: Library use in LegOS
|
| (...) of (...) For the IAR compiler, this should not a problem. The libraries are optimized for minimal size, so we can probably use the standard libraires. And give our students the benefit of a full C lib. /jakob (24 years ago, 28-Mar-01, to lugnet.robotics.rcx.legos)
| |
