[vrjuggler-devel] [ vrjuggler-Bugs-1108774 ] Dependency package omniOrb incorrect

[SourceForge.net <no...@so...>]

Bugs item #1108774, was opened at 2005-01-24 19:01
Message generated for change (Comment added) made by patrickh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108041&aid=1108774&group_id=8041

Category: Build System
>Group: v1.1
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Patrick Hartling (patrickh)
Summary: Dependency package omniOrb incorrect

Initial Comment:
Detailed Description:
-----------------------------
The dependency packages contain the package omniOrb.
The lib directory in the deps package (at least with
Fedora Core 1)
does not contain the directory
./python2.2/site-packages, which is
what the build system is looking for (it crashes, of
course).  If you download omniORB-4.0.2, which appears
to be the correct version, the directory
"python2.2/site-packages" is created after you "make"
and "make install".  

Suggested Solutions:
-------------------------------
In order to prevent having someone d/l the omniOrb
package separately and taking advantage of the
dependency package (which is their intent), do the
following:

1) d/l omniOrb-4.0.2, configure, build and install
locally and copy the dirs "lib", "include" and "bin"
into the dependencies.  Replace old omniOrb stuff and
./lib/python dir.   I am sure that a developer was
probably trying to shortcut that link
(python2.2/site-packages), but didn't update the build
system to handle it.  That would be Option 2

2) Modify build of Juggler to handle the dependency
path lib/python instead of lib/python2.2/site-packages.
 But obviously I don't recommend - best to follow how
the source package does things for consistency if
someone wants to compile their own version of omniOrb.

Just FYI, I again compiled and found this build bug
under RHEL (Red Hat Enterprise Linux WS release 3
(Taroon Update 4)).
I will also be testing it on Fedora Core 3 soon, but
this is OS dependent.

Greg Schmidt
Virtual Reality Laboratory
Naval Research Laboratory
gre...@nr...


 

----------------------------------------------------------------------

>Comment By: Patrick Hartling (patrickh)
Date: 2005-01-24 21:28

Message:
Logged In: YES 
user_id=49856

As far as I can tell, this way of installing the omniORB
Python pieces works just fine.  That is, when I test it, it
works just as it should.

The dependency bundling of omniORB is done this way
specifically to avoid requiring that users set $PYTHONPATH
so that omniidl and friends can find the Python extension
modules that they need.  At run time, the omniORB Python
scripts search for the modules, and one of the places that
they search is relative to the directory containing the
script in ../lib/python.  For example, look at the script
omniidl.  It extends the Python library search path using
that directory.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108041&aid=1108774&group_id=8041