To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 1795
1794  |  1796
Subject: 
Re: Library use in LegOS
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Tue, 27 Mar 2001 07:18:01 GMT
Viewed: 
1249 times
  
Each program gets it's own copy

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 such to tell the
code that yes, there is such a function, at this absolute address.  However,
getting this to work automatically seems like a lot of work.

If I would use a different compiler, with a different set of libraries for
the program and the kernel, is there the potential for namn clashes?

Hmmmm. Not sure. Wish I knew more about compiler internals...

Well, if each program uses its own libraries, there is no risk.  The linked
binary from my compiler will call LegOS via some mechanism, and its own
libraries internally in the binary.  No problem.

How much of the LegOS-gcc standard libraires come from gcc and how much • have
been hacked specifically for legos?

It's all custom written - doesn't use the standard gcc libraries at all. In
fact when building the cross compiler, you have to tell it to forget about
the standard libraries.

Why is that?  For the IAR compiler we are going to use, the libraries are
completely operating-system neutral (strlen, memcpy, math libs, etc have
nothing to do with the operating system).

Lots of questions, but I am trying what apparently nobody has tried before,
since I only have seen gcc discussed here in the legOS forum.

/jakob



Message has 1 Reply:
  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 (...) (23 years ago, 27-Mar-01, to lugnet.robotics.rcx.legos)

Message is in Reply To:
  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 - (...) (23 years ago, 26-Mar-01, to lugnet.robotics.rcx.legos)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR