<?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>fa23714e - examples/ethtool: convert to pkg-config-based build</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#fa23714e</link>
        <description>examples/ethtool: convert to pkg-config-based buildRemove references to the old DPDK build system from the makefiles, and usepkg-config provided flags instead.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Thu, 03 Sep 2020 15:26:48 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@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/ethtool/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/ethtool/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/ethtool/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/ethtool/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/ethtool/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/ethtool/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>ed3077c1 - examples: make Linux environment check consistent</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#ed3077c1</link>
        <description>examples: make Linux environment check consistentSome Makefiles are using CONFIG_RTE_EXEC_ENV and othersare using CONFIG_RTE_EXEC_ENV_LINUXAPP.Use the latter one for consistency.We could remove CONFIG_RTE_EXEC_ENV later if considered useless.Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Wed, 06 Jun 2018 13:50:27 +0000</pubDate>
        <dc:creator>Thomas Monjalon &lt;thomas@monjalon.net&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/ethtool/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/ethtool/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>cbc12b0a - mk: do not generate LDLIBS from directory dependencies</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#cbc12b0a</link>
        <description>mk: do not generate LDLIBS from directory dependenciesThe list of libraries in LDLIBS was generated from the DEPDIRS-xyzvariable. This is valid when the subdirectory name match the libraryname, but it&apos;s not always the case, especially for PMDs.The patches removes this feature and explicitly adds the properlibraries in LDLIBS.Some DEPDIRS-xyz variables become useless, remove them.Reported-by: Gage Eads &lt;gage.eads@intel.com&gt;Signed-off-by: Olivier Matz &lt;olivier.matz@6wind.com&gt;Reviewed-by: Gage Eads &lt;gage.eads@intel.com&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Thu, 12 Oct 2017 16:04:21 +0000</pubDate>
        <dc:creator>Olivier Matz &lt;olivier.matz@6wind.com&gt;</dc:creator>
    </item>
<item>
        <title>feb9f680 - mk: optimize directory dependencies</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#feb9f680</link>
        <description>mk: optimize directory dependenciesBefore this patch, the management of dependencies between directorieshad several issues:- the generation of .depdirs, done at configuration is slow: it can take  more than one minute on some slow targets (usually ~10s on a standard  PC without -j).- for instance, it is possible to express a dependency like:  - app/foo depends on lib/librte_foo  - and lib/librte_foo depends on app/bar  But this won&apos;t work because the directories are traversed with a  depth-first algorithm, so we have to choose between doing &apos;app&apos; before  or after &apos;lib&apos;.- the script depdirs-rule.sh is too complex.- we cannot use &quot;make -d&quot; for debug, because the output of make is used for  the generation of .depdirs.This patch moves the DEPDIRS-* variables in the upper Makefile, makingthe dependencies much easier to calculate. A DEPDIRS variable is stillused to process library dependencies in LDLIBS.After this commit, &quot;make config&quot; is almost immediate.Signed-off-by: Olivier Matz &lt;olivier.matz@6wind.com&gt;Tested-by: Robin Jarry &lt;robin.jarry@6wind.com&gt;Tested-by: Jerin Jacob &lt;jerin.jacob@caviumnetworks.com&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Fri, 24 Mar 2017 13:21:31 +0000</pubDate>
        <dc:creator>Olivier Matz &lt;olivier.matz@6wind.com&gt;</dc:creator>
    </item>
<item>
        <title>20dcb28f - examples: skip unsupported ethtool and l3fwd-power on FreeBSD</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#20dcb28f</link>
        <description>examples: skip unsupported ethtool and l3fwd-power on FreeBSDUserspace ethtool and l3fwd-power not support FreeBSD.So skip them when build samples.Signed-off-by: Marvin Liu &lt;yong.liu@intel.com&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Mon, 14 Dec 2015 02:32:52 +0000</pubDate>
        <dc:creator>Yong Liu &lt;yong.liu@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>bda68ab9 - examples/ethtool: add user-space ethtool sample application</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/ethtool/Makefile#bda68ab9</link>
        <description>examples/ethtool: add user-space ethtool sample applicationFurther enhancements to the userspace ethtool implementation that wassubmitted in 2.1 and packaged as a self-contained sample application.Implements an rte_ethtool shim layer based on rte_ethdev API, alongwith a command prompt driven demonstration application.Signed-off-by: Remy Horton &lt;remy.horton@intel.com&gt;

            List of files:
            /dpdk/examples/ethtool/Makefile</description>
        <pubDate>Mon, 07 Dec 2015 13:48:59 +0000</pubDate>
        <dc:creator>Remy Horton &lt;remy.horton@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
