<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>25d3438c - examples/server_node_efd: convert to pkg-config-based build</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#25d3438c</link>
        <description>examples/server_node_efd: convert to pkg-config-based buildRemove references to the old make build system and use pkg-config forbuilding these examples.Signed-off-by: Kevin Laatz &lt;kevin.laatz@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Thu, 03 Sep 2020 15:26:43 +0000</pubDate>
        <dc:creator>Kevin Laatz &lt;kevin.laatz@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e9c65942 - examples: detect default build directory</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#e9c65942</link>
        <description>examples: detect default build directoryMost examples have in their makefiles a default RTE_TARGET directory to beused in case RTE_TARGET is not set. Rather than just using a hard-codeddefault, we can instead detect what the build directory is relative toRTE_SDK directory.This fixes a potential issue for anyone who continues to build using&quot;make install T=x86_64-native-linuxapp-gcc&quot; and skips setting RTE_TARGETexplicitly, instead relying on the fact that they were building in adirectory which corresponded to the example default path - which waschanged to &quot;x86_64-native-linux-gcc&quot; by commit 218c4e68c1d9 (&quot;mk: uselinux and freebsd in config names&quot;).Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Wed, 27 Mar 2019 13:58:05 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>218c4e68 - mk: use linux and freebsd in config names</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#218c4e68</link>
        <description>mk: use linux and freebsd in config namesRather than using linuxapp and bsdapp everywhere, we can change things touse the, more readable, terms &quot;linux&quot; and &quot;freebsd&quot; in our build configs.Rather than renaming the configs we can just duplicate the existing oneswith the new names using symlinks, and use the new names exclusivelyinternally. [&quot;make showconfigs&quot; also only shows the new names to keep thelist short] The result is that backward compatibility is kept fully but anynew builds or development can be done using the newer names, i.e.  both&quot;make config T=x86_64-native-linuxapp-gcc&quot; and &quot;T=x86_64-native-linux-gcc&quot;work.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Wed, 06 Mar 2019 16:22:42 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>742bde12 - build/linux: rename macro from LINUXAPP to LINUX</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#742bde12</link>
        <description>build/linux: rename macro from LINUXAPP to LINUXRename the macro to make things shorter and more comprehensible. Forboth meson and make builds, keep the old macro around for backwardcompatibility.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Wed, 06 Mar 2019 16:22:39 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3998e2a0 - examples: use SPDX tag for Intel copyright files</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#3998e2a0</link>
        <description>examples: use SPDX tag for Intel copyright filesReplace the BSD license header with the SPDX tag for fileswith only an Intel copyright on them.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Tue, 19 Dec 2017 15:49:02 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ed2a80fd - examples/server_node_efd: renamed from flow_distributor</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/server_node_efd/Makefile#ed2a80fd</link>
        <description>examples/server_node_efd: renamed from flow_distributorTo avoid confusion with distributor app, this commitrenames the flow-distributor sample app to server_node_efd,since it shows how to use the EFD library and it is basedon a server/nodes model.Signed-off-by: Pablo de Lara &lt;pablo.de.lara.guarch@intel.com&gt;

            List of files:
            /dpdk/examples/server_node_efd/Makefile</description>
        <pubDate>Tue, 24 Jan 2017 09:06:14 +0000</pubDate>
        <dc:creator>Pablo de Lara &lt;pablo.de.lara.guarch@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
