From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: migrating from old to new alsa-api Date: Thu, 22 Apr 2004 16:11:57 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: barat@medien.uni-weimar.de Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Thu, 22 Apr 2004 15:57:13 +0200 (CEST), barat@medien.uni-weimar.de wrote: > > Hi, > i need some clarifying about how the defines ALSA_PCM_OLD_HW_PARAMS_API > etc. behaves. > for alsa-1.x its clear that if the app uses the new api i have to define > ALSA_PCM_NEW_HW_PARAMS_API, no, with ALSA 1.x, the new API is chosen as default. > but what is for the case if i have an app with > the new api and the user uses only alsa9? if user recompiles the code with the old API, he has to add ALSA_PCM_OLD_* defines. > is alsa1.x then backwards > compatible? yes. the alsa-lib contains the versioned symbols for the backward comptibility. Takashi ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click