[omniORB] omniORB and Cygwin

Thu Dec 18 17:00:53 GMT 2003

It sounds like something is wrong with your python installation. Can you
confirm the existence of the file /usr/include/python2.3/Python.h? Can you
run a simple python program?

Also, what messages about python did you receive when you ran configure? If
you didn't receive anything useful, I would suggest adding:

  set -x

to the configure file (somewhere after the initial comment section works
well), and re-running configure and capture the output to a file. If you
still can't see anything strange, send me the file separately. Also, capture
make's out put to a file and send me that too:

  make > /tmp/make.out 2>&1

That will help me figure out where things are breaking.

Also, just for sanity's sake, please verify:

1) You are not talking about using Cygwin with Visual C++
2) You have the full cygwin installation and it works (see the cygcheck
command; if something is wrong, send me the output of 'cygcheck -s', too).
3) You have applied the patch I supplied to a clean omniORB 4.0.3
installation
4) You have not modified any files in ./config or ./mk (i.e., you didn't
manually try to specify an architecture)
5) You have run ../configure from the ./build directory

The patch I provided should just work out of the box, but cygwin is a
complicated environment to get setup right.

If you have further questions, you can contact me directly.

Doug

-----Original Message-----
From: Scott Robertson [mailto:srobertson at codeit.com] 
Sent: Thursday, December 18, 2003 4:23 PM
To: Doug.Brown at shadysoft.com
Cc: omniORB List
Subject: RE: [omniORB] omniORB and Cygwin

Does python need to be installed in a special way in order for this to
work? I get the following error while trying to compile idlpython.cc

python2.3/Python.H/: No such file or directory

On Mon, 2003-12-15 at 17:49, Douglas Brown wrote:
> Here's an updated version of the OmniORB/Cygwin patch. It should be used
> instead of the previous one. Let me know if you'd prefer a cumulative
patch
> instead of a complete replacement patch.
> 
> The reasons for the new patch are as follows:
> 
> 1) This patch uses standard cygwin file naming conventions
> 2) This version puts both standard libs and import libs in the lib
> directory. The bin directory is only for DLLs and executables
> 3) This patch corrects a few installation problems in the previous patch.
> 4) This version adds a few link flags that reduce the number of auto
import
> warnings
> 
> As before, the example programs still work, and the patch does not affect
> non-cygwin platforms.
> 
> 
> Doug
> 
> -----Original Message-----
> From: omniorb-list-bounces at omniorb-support.com
> [mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Douglas
Brown
> Sent: Monday, December 08, 2003 9:13 PM
> To: omniorb-list at omniorb-support.com
> Subject: [omniORB] omniORB and Cygwin
> 
> Hi folks,
> 
> I am including a patch for omniORB-4.0.3 that permits it to be used in a
> Cygwin environment. To apply the patch:
> 
> 1) install the complete Cygwin tool set; verify that it works correctly.
See
> http://www.cygwin.com for details.
> 2) extract the patch from this mail message and install it in the Cygwin
> /tmp directory. This usually maps to c:\cygwin\tmp if you have installed
> Cygwin in a standard way on your Windows box.
> 3) start a Cygwin bash shell. All of the following steps and commands
should
> be executed within bash:
> a) install omniOrb source code as normal (e.g., mkdir /dvl; cd /dvl; tar
> xzvf omniORB-4.0.3.tar.gz)
> b) cd into the omniORB-4.0.3 directory (e.g., cd /dvl/omniORB-4.0.3)
> c) apply the patch (e.g., patch -p1 < /tmp/omni.cygwin.patch)
> d) configure and make omniORB as normal for a Unix environment (i.e.,
mkdir
> build; cd build; ../configure <your options>; make)
> 
> Note, do not try to build on a SAMBA share, since the file permission
> mapping will probably be incorrect. This could make the build fail when
DLLs
> used in linking are not readable or the scripts are not executable.
Compile
> on a standard windows share to avoid this problem.
> 
> This patch also assumes that you have installed the *complete* Cygwin tool
> chain, not just the minimal tool chain needed to compile omniORB with
> Microsoft Visual C++. It also assumes that your Cygwin environment is
> completely current: g++ v3.3.1, bash v2.05b.0(1)-release, patch v2.5.8,
make
> v3.8.0, ld v 2.14.90 20030901, python v2.3.2, etc. The patch might work
with
> some previous versions of Cygwin tools, but I have not tested it and can't
> be sure. You can update your Cygwin installation using the setup.exe tool
> from their website. You should not need any other tools or compilers
beyond
> what is included in Cygwin.
> 
> Most of the included changes are just minor tweaks to the build system.
For
> example, I added the generation of import libraries to the builds. I also
> changed the output directories where products are installed to match up
with
> Windows a little better. For example, all DLLs and import libraries are
> installed in ${BUILD_DIR}/bin, while static libraries are installed in
> ${BUILD_DIR}/lib. Other than that, I've kept the structure the same as
> before. Also, the patch shouldn't effect non-Cygwin environments. I tested
> this on Linux just to be sure; even after applying the patch, omniORB on
> Linux builds and executes just as before.
> 
> I have built and successfully run every example except for partcl. Also,
all
> of the utilities seem to work correctly: catior, nameclt, omniNames, etc.
> Although I generated both static and dynamic libs, all of the executable
> tools, utilities, and examples use dynamic libs only in order to keep the
> file sizes down. Make sure the bin directory with all of the DLLS is in
the
> path when you execute any of those tools. Run cygcheck if you are not
sure.
> 
> If someone at omniORB would review these changes, clean them up if needed,
> and incorporate them into the code base, I'd appreciate it. If you're
happy
> with the results, my next step would be to add omniORB as a maintained
> package to Cygwin itself.
> 
> 
> Doug
> 
> ______________________________________________________________________
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list