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

[Adam Y. <ay...@fo...>]

Well, I'm still stuck in the config stage, although I am learning a
hellofalot about how CVS, autogen, and gnome development are organized.  

So to try to summarize:

pre) in ~/.bashrc

export CERTIFIED_GNOMIE="Getting There"


1) Log in to Gnome CVS.
2) checkout (or update) glib and ORbit
3) autogen, make and install glib into development directory (I chose
/usr/local/devel/  side question does a trailing slash have any effect
on autogen/ configure)
cd glib
./autogen.sh -prefix /usr/local/devel/
make
make install

4)autogen, make and install ORBit into development directory  

cd ../ORBit
./autogen.sh -prefix /usr/local/devel/
make
make install

5)Get orbitt cpp from CVS

6)and finally for orbitcpp

cd ../orbitcpp
./autogen.sh -prefix /usr/local/devel/
make

This is the step thaht fails for me.  I get a build error in
orbitcpp_tools looking MemHow.  I know this is in 
PREFIX/include/orb/allocators.h

But I don't see a -I/usr/local/devel/include in the compile command.

Note that I also tried it with 
--with-orbit-prefix=/usr/local/devel


Possily related question:

IN the configure output I found this snippet:
*** Your copy of orbit-idl doesn't support --backenddir
*** This means that you will have to install the C++ idl compiler
back-end
*** (with 'make install') before you can build the tests.

Is this indicitave of it not finding the right ORBit code?

THanks to all of you for your patience.

Adam


> 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)?