From mboxrd@z Thu Jan 1 00:00:00 1970 From: Panu Matilainen Subject: Re: [PATCH] mk: crypto pmds can only be built if librte_cryptodev is enabled Date: Fri, 11 Mar 2016 11:38:58 +0200 Message-ID: <56E29232.8070500@redhat.com> References: <9127451bf67ce08532a327cb66aefbcf7ed5b39f.1457687628.git.pmatilai@redhat.com> <7728480.8SZanX4UKp@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id C67FF2BEF for ; Fri, 11 Mar 2016 10:39:00 +0100 (CET) In-Reply-To: <7728480.8SZanX4UKp@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 03/11/2016 11:28 AM, Thomas Monjalon wrote: > 2016-03-11 11:13, Panu Matilainen: >> If the experimental CONFIG_RTE_LIBRTE_CRYPTODEV is disabled, >> build of any crypto pmds will fail because of the missing dependency. >> This has been present for a while now but hidden until the addition >> of null_crypto since all the other crypto pmds have been disabled >> by default. > > Good catch, thanks. > >> +ifeq ($(CONFIG_RTE_LIBRTE_CRYPTODEV),y) >> DIRS-y += crypto >> +endif > > Why not > DIRS-$(CONFIG_RTE_LIBRTE_CRYPTODEV) += crypto ? Just because old habits ... and ... you know :) Should I send a new version or can you fix that up when committing? - Panu -