This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

linking possibilities


  I'm trying to do a thing that I don't know if gcc is capable of doing
so I use this list to ask if it does.
  I'm programmig for ARM with arm-elf-gcc.
  I use eCos (Embedded Configurable Operating System) which is capable
of running threads.
  The normal way of working with eCos is first compile in a library all
eCos functionality, then prepare an application that defines some
threads (their functions and memory) and puts them to run, then link it
against the eCos library and download it to the target platform.

  What I would want to do is to download the threads individually, not
the whole operating system. I have thought that I could do this if I
could download first all the image of the operating system, linked with
an application capable of receiving an object file and make it to run.

  The problem is that I'd want that the new thread use the functions of
the OS. I have the prototipes, I have the elf version of the downloaded
image in my PC and I think that it would be enough to link the thread
code knowing where on memory are allocated the different functions (I
can see this information with arm-elf-nm).

  The final questions are:
  Can I compile somehow an application using the information of the
locations of the routines of another one (not an obect file but an
executable)?
  Is there a way to include in an executable all the functions of a
library even if they are not referenced in the application (in order to
have them in case any of the new downloaded threads needs them)?






--
Rafael Rodríguez Velilla        rrv@tid.es
Telefónica I+D          http://www.tid.es
Telf: +34 - 91 337 4270




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]