From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com
 [209.85.212.176]) by dpdk.org (Postfix) with ESMTP id 81BFB2A58
 for <dev@dpdk.org>; Mon,  6 Jul 2015 15:20:01 +0200 (CEST)
Received: by wiga1 with SMTP id a1so228668688wig.0
 for <dev@dpdk.org>; Mon, 06 Jul 2015 06:20:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=5V7YXDrOmVW151uwnLVOvuaasOJ/Ky74uWRXao8CHHA=;
 b=Cly2/7WARtAcFASMdL2mFYMVJxXgHw1umI+LF0JwnoieMnH7xXoc3OR2MNo+QPsIEV
 UrTRaU2pOZGH4Vf22bvb86WfYxyuYSJRo2UMztB5qgfX484dTQoDKmX1Mvc/G+tr4LuF
 YWKch5w/PHw6ovwSy1NrnyIYfOwlIrgRzsMF67JtKKI3NYsmKmfTYsFCKfR52cbEhv9y
 u2UVPu8r2uu/pKx9tAZWCMF1RGfDBtfhJuUWZCb54m/A69yl2zFRFJwHPDpURZJOt/Be
 7ZdvNWwDhPW6/n3MSBJyLnTpqxsvsM1YpM0MhoTt6hcRhJaiL+/tgCHxY6DvmUUWsRDW
 zfzQ==
X-Gm-Message-State: ALoCoQlUT1bEEPlw/QuqncbgUnnsisjeeVfrkj9q8gVZVesABH4YWU25d5/NDTCBHAuMbTVunpqt
X-Received: by 10.194.78.175 with SMTP id c15mr92601649wjx.136.1436188801401; 
 Mon, 06 Jul 2015 06:20:01 -0700 (PDT)
Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136])
 by mx.google.com with ESMTPSA id z9sm47228516wiv.9.2015.07.06.06.19.59
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 06 Jul 2015 06:20:00 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Date: Mon, 06 Jul 2015 15:18:51 +0200
Message-ID: <10048439.cxXN29b43P@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <1435874746-32095-1-git-send-email-thomas.monjalon@6wind.com>
References: <1435874746-32095-1-git-send-email-thomas.monjalon@6wind.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH] mk: enable next abi in static libs
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2015 13:20:01 -0000

Any comment or ack?

2015-07-03 00:05, Thomas Monjalon:
> When a change makes really hard to keep ABI compatibility,
> instead of waiting next release to break the ABI, it is smoother
> to introduce the new code and enable it only for static libraries.
> The flag RTE_NEXT_ABI may be used to "ifdef" the new code.
> When the release is out, a dynamically linked application can use
> the new shared libraries without rebuild while developpers can prepare
> their application for the next ABI by reading the deprecation notice
> and easily testing the new code.
> When starting the next release cycle, the "ifdefs" will be removed
> and the ABI break will be marked by incrementing LIBABIVER.
> 
> The new option CONFIG_RTE_NEXT_ABI is not defined in the configuration
> templates because it is deduced from CONFIG_RTE_BUILD_SHARED_LIB.
> It is automatically enabled for static libraries and disabled for
> shared libraries.
> It can be forced to another value by editing the generated .config file.
> It shouldn't be enabled for shared libraries because it would break the
> ABI without changing the version number LIBABIVER. That's why a warning
> is printed in this case.
> 
> The guideline is also updated to integrate this new possibility.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>