[omniORB] compiling omniorb with cygwin

Kevin Williams KWilliams@visionael.com
Mon, 7 Jan 2002 08:10:25 -0800


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C19795.D1124000
Content-Type: text/plain;
	charset="iso-8859-1"

> There is no reason why you couldn't use the existing 
> NT configuration of omni_thread, but compiled with 
> cygwin. This would avoid relying on the unstable 
> cygwin pthreads implementation.

What changes to the NT configuration would be needed for this?  I fear they
would be rather non-trivial (and rather difficult for someone like myself
who can't even begin to understand Omni's current build process ;).  Please
tell me I'm wrong! <smile>

-- Kevin Williams
   Visionael Corporation
   kwilliams@visionael.com

------_=_NextPart_001_01C19795.D1124000
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [omniORB] compiling omniorb with cygwin </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&gt; There is no reason why you couldn't use the =
existing </FONT>
<BR><FONT SIZE=3D2>&gt; NT configuration of omni_thread, but compiled =
with </FONT>
<BR><FONT SIZE=3D2>&gt; cygwin. This would avoid relying on the =
unstable </FONT>
<BR><FONT SIZE=3D2>&gt; cygwin pthreads implementation.</FONT>
</P>

<P><FONT SIZE=3D2>What changes to the NT configuration would be needed =
for this?&nbsp; I fear they would be rather non-trivial (and rather =
difficult for someone like myself who can't even begin to understand =
Omni's current build process ;).&nbsp; Please tell me I'm wrong! =
&lt;smile&gt;</FONT></P>

<P><FONT SIZE=3D2>-- Kevin Williams</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Visionael Corporation</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; kwilliams@visionael.com</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C19795.D1124000--