[omniORB] omniORB 4.1(CVS) and MinGW experiences

[Pablo Bleyer Kocik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


 Hello group.

 I want to congratulate the omniORB team for maintaining and improving omniORB.

 It's been a couple of years since I used omniORB for the last time. For one of
my projects needing CORBA again, yesterday I compiled 4.1 from CVS using MinGW
(gcc version 3.4.2) with very little trouble, and it has been running swiftly
with my old programs and services (dynamically compiled).

 I was afraid that I would need to start heavily patching omniORB to work with
MinGW or Cygwin as it used to be. I tried 4.0.5 but I did have problems, first
with the 'types.py' clobbered file and then crashes at runtime. 4.1 only needed
the following 'tweaks':

 - I had to put the full path of the Python.h file in idlpython.cc. The python
path information 'discovered' by the configuration process used the
Windows-backslashed style, which make/gcc didn't like.

 - I had to install the 'rebase' Cygwin package, since it wasn't installed by
default.

 Well, many thanks again. I will let you know if I find more issues. Keep up the
good work.

 Cheers.

- --
PabloBleyerKocik /"I believed that people would become programmers
 pablo          / and not need companies as much. You can see how
  @bleyer.org  / laughable that was." -- Steve Wozniak
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCNW7JF5qpHYMA2a0RAvlPAJ9rP5YQuGKdR0tFbHg/9uUKl6Yv4ACbBBhs
zV3CcPonKCxF4p2Pufy1D1g=
=xuJ1
-----END PGP SIGNATURE-----