Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<011401c013a1$556f3df0$f7c723cb@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc:	<cygwin AT sources DOT redhat DOT com>
References:	<20000831194146 DOT 867 DOT qmail AT web120 DOT yahoomail DOT com> <20000831154242 DOT B7880 AT cygnus DOT com> <39AEC3AD DOT 42FE1CB9 AT ece DOT gatech DOT edu> <20000831171339 DOT A15393 AT cygnus DOT com> <39AEDDC9 DOT D4315497 AT ece DOT gatech DOT edu> <00ee01c0139e$3a7572b0$f7c723cb AT lifelesswks> <39AEE158 DOT DB923296 AT ece DOT gatech DOT edu>
Subject:	Re: DLL naming conventions
Date:	Fri, 1 Sep 2000 10:15:18 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime:	31 Aug 2000 23:05:46.0546 (UTC) FILETIME=[FF029120:01C0139F]

That's what  I meant...
I'm not sure how much of .net is dcom, a.k.a. OLE3...

And unfortuneatly I don't know the build details for a com/ole server (which
is what we'd need in binutils). I believe there is v. little to it though
when you are using in-process servers. The big hooha is creating the class
registration in the registry at install time.

Anyway it's in the discussion pot now..
Rob

----- Original Message -----
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: <cygwin AT sources DOT redhat DOT com>
Sent: Friday, September 01, 2000 9:51 AM
Subject: Re: DLL naming conventions


> Robert Collins wrote:
> >
> > I'll probably get shouted at for this but...
> > what about using dcom for shared libraries? It's designed to handle
> > versioning issues transparently, load the library from whatever location
> > desired etc.
>
> No, not shouted at. I don't think cygwin-binutils can do "Distributed
> COM (TM microsoft, copyright microsoft blah blah" builds, though, so
> it's not really applicable to this discussion.
>
> Unless you want to add Distributed COM support to ld?
>
> ("Distributed COM" a.k.a. COM+ a.k.a. .NET a.k.a
> Microsoft's-next-marketing-brainstorm is what you mean by 'dcom',
> right?)
>
> --Chuck
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -