AW: [omniORB] egcs with enable threads required for building omni idl2?

[Schmidmeier, Arno]

	What I want to do is, create a new backendend to the
omniidl-compilers, (preferable in python)
	which will generate me some adaptor and helping code for specific
idl-constructs. Which will be in the beginning=20
	by some other orbs, till we also support omniORB.

	However I have another question. If I create a new backendend for
omniidl, must this backendend be published under the GPL or can I =
assume
that the omniorb frontend is or will be under the LGPL?

	Thanks
	Arno Schmidmeier

************************************************************************=
*
************************************************************************=
*
Arno Schmidmeier

Sirius
Simplicity out of complexity

Arno.Schmidmeier@sirius-eos.com
Phone +49/89/ 61 36 76-37
Fax +49/89/ 61 36 76-33





> -----Urspr=FCngliche Nachricht-----
> Von:	Duncan Grisby [SMTP:dgrisby@uk.research.att.com]
> Gesendet am:	Mittwoch, 17. November 1999 12:47
> An:	Schmidmeier, Arno
> Cc:	OmniOrb-List (E-Mail)
> Betreff:	Re: [omniORB] egcs with enable threads required for building
> omniidl2?=20
>=20
> On Tuesday 16 November, "Schmidmeier, Arno" wrote:
>=20
> > I know I needto have a thread enabled egcs compiler to be able to
> generate
> > omniOrb client or server applications.
> > But what I want to know is, do I need also the thread enabled =
compiler
> to
> > create the omniidl2 application=20
> > and the omnipy application? And successfully running these =
applications?
>=20
>=20
> Do you mean omniORBpy and the new omniidl?  If so, you need a
> thread-enabled compiler for omniORBpy, but you'd get away without for
> omniidl. I don't see how it would do you any good to be able to run
> the idl compiler but not run an ORB, though.
>=20
> I'd recommend using GCC 2.95 rather than egcs.
>=20
> Cheers,
>=20
> Duncan.
>=20
> --=20
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --