From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Question about adding a new EAL Date: Tue, 22 May 2018 23:04:21 +0200 Message-ID: <1899920.NzqdMBxxeb@xps> References: <1943193.bOZbQYoKI2@xps> <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, "Wiles, Keith" To: Alex Ciobotaru Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 34C8C1D9E for ; Tue, 22 May 2018 23:04:24 +0200 (CEST) In-Reply-To: <9d7c6bbf-4c14-d68e-3b17-87ef73a71303@gmail.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 22/05/2018 22:56, Alex Ciobotaru: > Guys, thank you for the info so far (sorry about the HTML thing). > I will put some further insight/closure into this thread. > So, my query started from the fact that when developing a new EAL > in DPDK using an external toolchain and/or for a new OS, > the "common" (generic) part of the EAL is actually Linux/BSD bound: > > ...// START OF EXCERPT > dpdk/build/include/rte_eal.h:15:19: fatal error: > sched.h: No such file or directory So you want to port DPDK to a non-POSIX OS? If it is considered an interesting OS, we could move some POSIX parts out of the common files.