This is the mail archive of the
mailing list for the GCC project.
Re: embedded c
- From: Clifford Wolf <clifford at clifford dot at>
- To: "Schuster, Joel (N-Compaq)" <joel dot schuster at lmco dot com>
- Cc: "Gcc (E-mail)" <gcc at gcc dot gnu dot org>
- Date: Tue, 28 Oct 2003 13:37:37 +0100 (CET)
- Subject: Re: embedded c
- References: <3C5AF3DA12E4B44790EE93DB9FA11FF5E2B3E1@EMSS02M13.us.lmco.com>
On Fri, 24 Oct 2003, Schuster, Joel (N-Compaq) wrote:
> Just interested if anyone has tried creating a version of gcc and the
> linker that would be shared objects that would allow in-memory
> compilation and linking at runtime? I'm thinking of this in terms of
> using C/C++ as a embedded scripting language within an application where
> the 'script' would have access to all the resources that the main
> application would.
If performance isn't an issue, you might just call gcc as external program
and build your 'script' as shared object file. After building it you could
simply dlopen() that shared object ..
| Clifford Wolf /-----=[ www.clifford.at ]==[ Tel: +43-699-10063494 ]=-\
|--------------/ diestartseite.at vocat.cc =[ Fax: +43-2235-42788-4 ]=-|
|-=[ EDEN Creations -- www.edenevents.at ]==[ IRC: www.freenode.net ]=-|
\==[ www.rocklinux.org ]===[ www.rocklinux.net ]===[ www.linbit.com ]==/
2B OR (NOT 2B) That is the question. The answer is FF.