X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-Trace:	83964497/mk-filter-4.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.66.94.76/None/johne53 AT tiscali DOT co DOT uk
X-SBRS:	None
X-RemoteIP:	79.66.94.76
X-IP-MAIL-FROM:	johne53 AT tiscali DOT co DOT uk
X-IP-BHB:	Once
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	ArwEAAte50hPQl5M/2dsb2JhbACEDE20XYFo
X-IronPort-AV:	E=Sophos;i="4.33,361,1220223600"; d="scan'208";a="83964497"
Message-ID:	<003001c9265e$547e6280$4001a8c0@mycomputer>
From:	"John Emmas" <johne53 AT tiscali DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<009001c92541$e678fb00$4001a8c0 AT mycomputer> <48E668F7 DOT 7020204 AT users DOT sourceforge DOT net>
Subject:	Re: libasound
Date:	Sat, 4 Oct 2008 20:18:13 -0000
MIME-Version:	1.0
X-Mailer:	Microsoft Outlook Express 6.00.2900.2180
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT 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/

- Raw text -