From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 745DB1B05 for ; Tue, 22 May 2018 21:23:52 +0200 (CEST) Received: by mail-wm0-f48.google.com with SMTP id m129-v6so2772842wmb.3 for ; Tue, 22 May 2018 12:23:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xvDwFccsqsg21g4lAZZZXYRoQfgr3Ee08qmouXwlTZQ=; b=ZBnQ/7GQuN3Lf6MBG5/WtlNfXqgYKILVWt7RNbRA3yve3aGfKxN00E4jbAsepjodK9 VVabkU7aP0/aAAn4Zaa8qWhjlCer8SD9DzYay+Mrbellg2vcjPNGye171VQZyABva8pA Y5WDuB2UzrCQiXRLgMZQA0TSvJca0pRmg5xEF/H54uzDD9icBBqtrFsGem1JgJjGVSlm +MK8b8YeLa3kt9qP6Ar9j4wIUDqBjlusoUqE73CY4D276rV1pEFondAJ3W3vi+debyLO VEQawefD7x9ueTjkqgspxZH2ptyvTkKfWg03RJey0pKRbk+fwJ8+p4xMWWLtLADdnfYv FZtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xvDwFccsqsg21g4lAZZZXYRoQfgr3Ee08qmouXwlTZQ=; b=PLRX6D/rgqYMUhMzvmhv3DuV3HBTWoItM5U5sUAV96bS5r7qyZNO8flwfDZJzqLzts fw2kj28vLmHeKrjVW57KmE28UagXCGdyWGW9dJei6aaPeRzmIZypIJrnOfDV09zR3CM2 jm89uV1YuuFtxKWFNs3sWvQ7T72HbbAQMJ3P0BurW7wftSZLrAZzMJ75YCvhxkwef8Tl U11DUurXtga+pypDjHzIJdcNnSxUvqb0E2hJ4u2DnoLaEveQMHWguG4UB8fsPzUKc51Y clTxHAxCUV7LihH5iuHtqCOiKCBGHdPzPdlUes9adKGpr5psxaSdNyAs2w7vUolMRcqQ b/3g== X-Gm-Message-State: ALKqPwf9ry9qdBBPBvJqCfPy0So3UfUOfTdDBYFciMkEpJ8lJE6V+jPi wumbRK4j8ejr1RKuNLIxocyrXrSDST2Xea7Co+O33B2w X-Google-Smtp-Source: AB8JxZqIrpVgzpxkVFJnb9+tsC/avYXS6d7O0jeMZTimINOEcsmeJ1806RJFONgonax69FtLBgpq0Q9NwJtC5WI/XSM= X-Received: by 2002:a50:9fc1:: with SMTP id c59-v6mr3695534edf.277.1527017031559; Tue, 22 May 2018 12:23:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:ad50:0:0:0:0:0 with HTTP; Tue, 22 May 2018 12:23:50 -0700 (PDT) From: Alexandru Ciobotaru Date: Tue, 22 May 2018 22:23:50 +0300 Message-ID: To: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Question about adding a new EAL X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2018 19:23:52 -0000 Greetings, I'm currently checking on how to add new EAL "app" to the DPDK so I started by adding a new "xyzapp" next to "linuxapp" and "bsdapp". Now, I would probably expect to make this new EAL mainline compliant on day, and to avoid future headaches, the plan is to avoid modifying things outside of my "xyzapp". And thus, the first adaptation issue has arrived: EAL is designed so that I can re-implement the "common" source files into my "xyzapp" but how would I override the "include/rte_xyz.h" headers from the "common" part of the EAL library (e.g. librte_eal/common/include/rte_eal.h)? Some of the includes in these headers are currently N/A to my toolchain (via CROSS=) or to my executive environment. For example I do not have or which are currently included in some EAL API headers. Should more work into making the "common" part truly generic be put into this? Is the current EAL API frozen for compatibility reasons? Any "next" branch where such modifications are accepted? Or, is there a straight method of enforcing my "xyzapp" symlinked EAL headers in the build directory without modifying the "common" Makefile? Thank you, Alex