view content/Coding/013-omniorbpy-virtualenv.rst @ 10:6c03ca07a16d

Renamed my tools directory to "tools". I named it __bgn because I was worried it would clash with a future Pelican updaet. But it seems like this would only happen if I re-ran the quickstart script. "tools" is a better name. :)
author Brian Neal <bgneal@gmail.com>
date Sun, 02 Feb 2014 11:32:13 -0600
parents 7ce6393e6d30
children
line wrap: on
line source
Installing omniORBpy in a virtualenv
####################################

:date: 2012-03-27 20:30
:tags: Python, omniORB, virtualenv
:slug: installing-omniorbpy-in-a-virtualenv
:author: Brian Neal

I came across an interesting question on Stackoverflow_, which was essentially
`How to install omniORBpy in a virtualenv`_? I've had a lot of experience with
omniORB_, a high quality, open-source CORBA ORB, at work. omniORB is a C++ ORB,
but it also includes omniORBpy, a thin Python_ wrapper around the C++ core.
Despite using omniORBpy extensively, I had never used it in a virtualenv_.

So I got curious, and gave it a shot. You can read `my answer`_, which the
questioner accepted. I'd love to hear of any better ways of doing it. I worked
it out for Ubuntu, but a Windows solution would be nice to see also.

.. _Stackoverflow: http://stackoverflow.com/
.. _How to install omniORBpy in a virtualenv: http://stackoverflow.com/questions/9716611/install-omniorb-python-in-a-virtualenv
.. _omniORB: http://omniorb.sourceforge.net/
.. _Python: http://www.python.org/
.. _virtualenv: http://www.virtualenv.org/
.. _my answer: http://stackoverflow.com/a/9881882/63485