DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Pm9MmayKuROLnRxndoSl0R/E3Vwk9mzgMMxiJoVohHZ/apsVjhHWY
	nKTPj5mbq1uYEPdg4dNb0gdlS2lLaPq6/1RCRId5N/rbNDN1U/1V48gFvuC0x9zK
	DCcVeUrZA9/cNkYq/Br4FiBPDXPfzpqlCMMGLYVQiWKGs/Ur5g8huM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 4 Apr 2013 10:40:50 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: But it is cygwin related.
Message-ID: <20130404144050.GA779@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20130404170527.3708@binki> <20130404085538.GE25170@calimero.vinschen.de> <515D78B1.60209@farance.com> <CA+sc5mmQ9rJ85rvDbMTvp_+vCx6CQPava5N3-8yxd9soh6zxQg@mail.gmail.com> <20130404230429.3100@binki>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130404230429.3100@binki>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Apr 04, 2013 at 11:04:29PM +0900, wynfield wrote:
>No Earnie.  It wasn't about programming.  Read and try to comprehend.
>cygwin seems to have a missing api in it or one it should have is
>missing.  The cygwin.dll or possibly another cygwin dll shuffles i/o
>betwwen cygwin programs and MSWindows is not open to linkage (or is it)
>by assembly language programs.  This should be a realitive easy thing
>to do.  There are entry points in the dll'S for i/o, which is called
>from the assembled c programs.  It should be even easier for an
>assembly program to directly link to those dlls.  If it can not then it
>is missing.  If it is not missing, where is it and where is it
>documented?  This would be to cygwin and the cygwin community as a
>whole good.

If you're asking how to call cygwin entry points to use Cygwin I/O from
an assembly language program then you are on-topic for the mailing list.
It is possible to write a raw assembly language program which does this
but, given the amount of confusion evident in the above paragraph you
are clearly quite a long way from having the necessary skills to do
anything like this.  And, perhaps most importantly, there are only
a handful of people who would have a clue about how to do this and I'll
go out on a limb and say that none of us is interested in attempting
to teach you.  But even if we were, an assembly program which relied on
a massive DLL doesn't really meet your criteria anyway.

Writing an assembly language program which just uses Windows APIs to
write to the console would likely be much easier but that is off-topic
for this list.

There's no use arguing about this.  This isn't your mailing list and you
don't set the rules.  Further arguing will have undesirable consequences
for you.

>p.s.  If you would like to learn about programming, it is off topic for
>this list, but I'd be happy to help you if you write directly.

Mocking people who could potentially help you is rarely a good idea.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple