<div dir="ltr"><br><div>Hi there, I'm a new omniORBpy user.</div><div><br></div><div>Recently I was trying to install omniORBpy on a mac. Downloading, configuring and building the omniORB and omniORBpy packages as mentioned on the installation page worked like a charm. 'sudo make install' omniORB went well, too.</div>
<div><br></div><div>But 'sudo make install' omniORBpy only _seemed_ to work: it put it's .so files and .py files in the site-packages folder of the 'default' python lib location, while when running python on the mac, packages are searched in /Libraries/Python2.7/libs/site-packages.</div>
<div><br></div><div>I hand-fixed it by adding a symlink to the relevant files in /Libaries..., but I believe that the configure or installation script should have accounted for that.</div><div><br></div><div style>Now I have two questions:</div>
<div><br></div><div><div>A. The configure script has, of course, the --prefix argument. Can I use that to indicate where the site-packages are going to be put? </div></div><div><br></div>
<div>B. Anyhow, I would assume that the configure script intends to be cross-platform. Not being an autotools-guru myself, I post the question to the mailing list: why did this go wrong, and how should this be fixed?</div>
<div><br></div><div><br></div><div>Many thanks,</div><div>
<br></div><div>Kristoffel</div><div><br></div><div><br></div></div>