OSDev.org

Hi all,

I've managed to make my 64-bit kernel able to load user-mode executables and to run them in multitasking. So far I'm using flat binaries, but I plan to shift to ELF sooner or later.

Even if I've developed it in C, I'd want to write user-space applications in C++. I've searched the wiki, but I've found only kernel-specific info.
What I'm supposed to do in order to use C++ in his full power for writing my programs? Even a simple list of the requirements would be appreciated.

You'll need the C++ equivalent of stdlib, to start with. STL, ATL, whatnot.


JAL

Hi,

The first thing to start with is the standard library. Suppose this is newlib (see Porting Newlib), you will have to provide the same glue functions as if you were providing a C library for kernel space, except your glue functions will wrap system calls, rather than directly calling kernel functions.

Once you have a C library, porting the C++ stuff (such as libstdc++) should be relatively easy (coming from someone who hasn't actually done it... ).

Cheers,
Adam

So I need full support to C, before anything else.
Thank you.

andreaorru wrote:So I need full support to C, before anything else.

That's effectively true for most languages, as the majority of language support runtimes / libraries is written in C. (Or C++, at which point the snake bites its own tail.)

Luckily, C doesn't require much in the way of "support". (Which is why other languages are so often implemented in it. )

jal wrote:You'll need the C++ equivalent of stdlib, to start with. STL, ATL, whatnot.


JAL

ATL? The ActiveX Template Library?!

You need libstdc++, as has already been mentioned, but you also need to have code to run the global static constructors where present and you may also need to provide a "crti" and "crtn".

So I need full support to C, before anything else.

I'd say once you can load and run an application such as bash you are ready to get libstdc++ running with some test C++ applications.

Owen wrote:ATL? The ActiveX Template Library?!

Without the X, actually. But you are right, I was incorrect in mentioning it.


JAL