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

[Phil D. <ph...@us...>]

Adam Young wrote:
> 

[snip...]

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

I don't think so. 


[snip...]

> 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.
> 

Could you mail the compile command? - cheers.


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

Yes! The CVS head version of ORBit definitely has --with-orbit-prefix.

Hmmm... 
<gets off his arse and attempts to build ORBit/orbitcpp from scratch>

I may have the answer: 
I've just attempted to do this on a fresh redhat 6.2 system with helix
gnome, and helix gnome comes with ORBit-0.5.2. The problem is that the
ORBit in CVS head is fixed at 0.5.1 for some god-only-knows reason. This
means that the configure script gets confused (and prints out a verbose
warning msg), but ultimately doesn't stick the correct include and lib
directives into the makefiles.

I fixed this by editing the ORBIT_MICRO_VERSION variable in ORBit
configure.in from 1 to 2, which fixed the problem.

Does this help?

> THanks to all of you for your patience.
> 

You're welcome; - thanks for your perserverance!

Cheers,

Phil.