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

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

THis is the compile command that fails.

c++ -DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -I/usr/local/lib/glib/include
-I/usr/local/include -I/usr/include -g -O0 -Wall
-Wp,-MD,.deps/orbitcpp_tools.pp -c orbitcpp_tools.cc  -fPIC -DPIC -o
.libs/orbitcpp_tools.lo


Is --with-orbit-prefix=/usr/local/devel required?  I'm a little unclear
through all the emails.  Are there other params to configure that are
required (for ORBit to find glib, etc)

BTW 
I'm running:
 gcc --version 
2.95.2

I get a lot of these :
configure.in:93: warning: AC_TRY_RUN called without default to allow
cross compiling


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



Hmm, Well that describes my configuration.  But I tried that too and it
didn't run. (I also tried setting it to 3) SOmething is fooling
configure into not picking up the stuff from the /usr/local/devel
directory. 


I'll also try it with the latest CVS of ORBit.

Adam