RE: How to get GCC to compile to binary, but in raw format NOT ob ject

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for your help, but what I need goes beyond even a DSO, I want to be
able to compile, link execute a C program, later on compile a C function to
binary, load this into memory using a malloc/fread combination into the
original program and then execute it from there.  With a DSO, you need to
know the function name, parameters etc in advance, so you link a stub which
then call the DSO code itself.

Steve

-----Original Message-----
From: John Love-Jensen [mailto:eljay@xxxxxxxxx]
Sent: 15 September 2003 16:51
To: DAWE,STEVE (HP-UnitedKingdom,ex2); 'gcc-help@xxxxxxxxxxx'
Subject: Re: How to get GCC to compile to binary, but in raw format NOT
object


Hi Steve,

You want a DSO (dynamic shared object).

Generate your code into a shared object (a .so in Unix-land, a .dll in
Windows-land, a .library in Amiga-land), and -- in Unix-land -- use dlopen
and the other dlxxxx functions when you want to access your routine
dynamically.  Windows and Amiga have equivalent mechanisms.

--Eljay


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux