[omniORB] Problem building omnipy2_develop from CVS

[Duncan Grisby]

On Friday 15 March, Harri Pasanen wrote:

> Ok, fair enough:
> 
> ./configure --with-omniorb /work/harri/omni/omni

That should be --with-omniorb=/work/harri/omni/omni

It thinks you're telling it your platform name is
/work/harri/omni/omni, so it's confused.

Note that the directory you give must be the installation directory
for omniORB, not the build directory. You must build omniORB using the
autoconf set-up and do a make install before omniORBpy will build.

The best thing to do is to configure both omniORB and omniORBpy will
the same prefix. That way, you don't need to tell omniORBpy where to
find omniORB:

  $ cd omni
  $ mkdir build
  $ cd build
  $ ../configure --prefix=/work/harri/omni
  $ make
  $ make install
  $ cd ../../omniORBpy
  $ mkdir build
  $ cd build
  $ ../configure --prefix=/work/harri/omni
  $ make
  $ make install

omniORB and omniORBpy are now installed in /work/harri/omni/bin,
/work/harri/omni/lib, /work/harri/omni/include, and so on.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --