Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 19 Feb 2002 12:57:58 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Updating the DLL build instructions
Message-ID: <20020219175758.GH1233@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6EB31774D39507408D04392F40A10B2BC1FF40 AT FDYEXC202 DOT mgroupnet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6EB31774D39507408D04392F40A10B2BC1FF40@FDYEXC202.mgroupnet.com>
User-Agent: Mutt/1.3.23.1i

On Tue, Feb 19, 2002 at 10:38:29AM -0500, Roth, Kevin P. wrote:
>If you will use a piece of code as an "example" for your DLL building
>docs, I have a suggestion: use tftp...
>
>I'd like to obtain TFTP code in the form of a .DLL instead of an .EXE. I
>need to ultimately give it COM interfaces for use from within Visual
>Basic 6. It's already part of inetutils, and there aren't a lot of
>files, so I'm assuming it would be pretty straightforward.

Sure.  Send your words + example here for review.  That would be best.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/