Message-ID: <003001c9265e$547e6280$4001a8c0@mycomputer>
From: "John Emmas" <johne53@tiscali.co.uk>
To: <cygwin@cygwin.com>
References: <009001c92541$e678fb00$4001a8c0@mycomputer> <48E668F7.7020204@users.sourceforge.net>
Subject: Re: libasound
Date: Sat, 4 Oct 2008 20:18:13 -0000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="Windows-1252"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

----- Original Message ----- 
From: "Yaakov (Cygwin Ports)"
>
> John Emmas wrote:
>> Anyone know if 'libasound' has ever been ported for cygwin? (AFAIK, it's
>> an ALSA sound library).
>
> If you know what the L in ALSA stands for, then you'll understand that
> it's not available on Cygwin.
>
Yaakov - could you please indulge me for a moment here?  I know that
the 'L' stands for 'Linux'.  And I know you aren't suggesting that Linux
library code can't be compiled under Cygwin because that's surely one of its
primary features.  So why should the letter 'L' tell me that something is
wrong?  Is it because ALSA is a sound library and needs direct access to the
sound hardware?  Or does it need kernel support which isn't (or can't be)
emulated by Cygwin?  Or both?  Or is there some other reason that I haven't
spotted?  I'd like to understand this.

Thanks,

John 


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