Re: [orbitcpp-list] Understanding orbit-c++

[Andreas K. <ak...@ix...>]

On Tue, Jul 25, 2000 at 08:22:58PM -0500, Dave Smith wrote:
> 
> Greetings again...
> 
> Well, I managed to get CVS ORBit & CVS ORBit-cpp working in a "safe" directory. IDL compiler seems to work
> and everything is happy. I can run the tests, tho the tests/everything-typedef doesn't want to build for
> some reason. At any rate, most of the stuff appears to work.

Yup, everything-typedef fails for some reason for me, too. I'll look into
this when the next exams are over (Aug 3). 

Important: Did you also install glib into your safe directory (would be 
good), and does ORBit-C++ use -I/your/gnome/directory when compiling 
(would be bad)?

> 
> Now I'm starting to wonder how this binding/wrapper works...are there any documents explaining your approach
> and/or theories?

see the HACKING file.

> I'm a C++ person and would prefer to _not_ try and write bonobo components in C (unlike certain other parties
> on GNOME) :) My next question is this: what are the dependencies of ORBit and how hard will it be to setup
> once bonobo starts getting widespread use? I want to make my code as easy as possible to build, if people
> wish to do so.

ORBit only depends on glib. ORBit-C++ does not add any dependency.
A working STL is only necessary for building the IDL compiler.
ORBit-C++ should not, in its final state, be any harder to set up
than ORBit itself.

> why do I have to run the compiler twice?

because by doing 

orbit-idl -lc++ blah.idl

you generate classes that wrap the stuff you generate by doing

orbit-idl -lc blah.idl.

bye
andy

-- 
Don't innovate, intimidate.