<?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>11e02702 - examples: fix pkg-config override</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#11e02702</link>
        <description>examples: fix pkg-config overrideMove pkg-config override to beginning in the Makefile to allowuse PKGCONF variable to detect the libdpdk availability.Fixes: fda34680eb9a (&quot;examples: remove legacy sections of makefiles&quot;)Cc: stable@dpdk.orgSigned-off-by: Jerin Jacob &lt;jerinj@marvell.com&gt;Acked-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Wed, 05 May 2021 14:25:25 +0000</pubDate>
        <dc:creator>Jerin Jacob &lt;jerinj@marvell.com&gt;</dc:creator>
    </item>
<item>
        <title>5a196330 - examples: warn about broken pkg-config</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#5a196330</link>
        <description>examples: warn about broken pkg-configSince the examples are designed to be built by end-users using Make, wecan detect and warn about broken pkg-config on the user&apos;s system as partof the build process.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Tue, 19 Jan 2021 13:03:24 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>fda34680 - examples: remove legacy sections of makefiles</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#fda34680</link>
        <description>examples: remove legacy sections of makefilesThe example app makefiles contained sections using the legacy method ofcompiling with make. These are no longer needed, and are removed,leaving only the section that uses pkg-config for the make build.Signed-off-by: Ciara Power &lt;ciara.power@intel.com&gt;Acked-by: Nicolas Chautru &lt;nicolas.chautru@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Thu, 03 Sep 2020 15:26:41 +0000</pubDate>
        <dc:creator>Ciara Power &lt;ciara.power@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>8549295d - build/pkg-config: improve static linking flags</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#8549295d</link>
        <description>build/pkg-config: improve static linking flagsRather than setting -Bstatic in the linker flags when doing a static link,and then having to explicitly set -Bdynamic again afterwards, we can updatethe pkg-config file to use -l:libfoo.a syntax to explicitly refer to thestatic library in question. Since this syntax is not supported by meson&apos;spkg-config module directly, we can post-process the .pc files instead toadjust them.Once done, we can simplify the examples&apos; makefiles and the docs by removingthe explicit static flag.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;Acked-by: Sunil Pai G &lt;sunil.pai.g@intel.com&gt;Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Tue, 30 Jun 2020 14:14:32 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>69b1bb49 - examples: hide error for missing pkg-config path flag</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#69b1bb49</link>
        <description>examples: hide error for missing pkg-config path flagSome versions of pkg-config don&apos;t support the --path flag, which is not afatal error when building the apps. Without the flag, the makefile justcannot track the .pc file of DPDK as a dependency of the build. Therefore,we can ignore the error and suppress it by redirecting to /dev/null thestderr from that call to pkg-config.Fixes: 22119c4591a0 (&quot;examples: use pkg-config in makefiles&quot;)Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Tested-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Fri, 15 Nov 2019 15:17:00 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>12a652a0 - examples: fix build with old pkg-config</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#12a652a0</link>
        <description>examples: fix build with old pkg-configNot all versions of pkg-config in distros have support for the--define-prefix flag [1], causing errors when building examples manually orwith test-meson-builds.sh script [2].For the former case, we need to remove the hard-coded use of the flag inthe Makefiles.For the latter case, the flag is necessary for builds to succeed, so weskip the tests when it&apos;s not present, passing it as part of the pkg-configcommand if it is supported.[1]CentOS Linux release 7.7.1908 (Core)pkg-config version 0.27.1[2] ## Building cmdlineUnknown option --define-prefixgmake: Entering directory`...ild-x86-default/install-root/usr/local/share/dpdk/examples/cmdline&apos;rm -f build/cmdline build/cmdline-static build/cmdline-sharedtest -d build &amp;&amp; rmdir -p build || trueUnknown option --define-prefixUnknown option --define-prefixgcc -O3  main.c commands.c parse_obj_list.c -o build/cmdline-sharedmain.c:14:28: fatal error: cmdline_rdline.h: No such file or directoryFixes: ca9268529d2b (&quot;examples: support relocated DPDK install&quot;)Fixes: 7f80a2102bbb (&quot;devtools: test pkg-config file&quot;)Cc: stable@dpdk.orgReported-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Tested-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Fri, 15 Nov 2019 15:16:59 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4131ad5d - examples: fix pkg-config detection with older make</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#4131ad5d</link>
        <description>examples: fix pkg-config detection with older makeMake versions before 4.2 did not have support for the .SHELLSTATUSvariable, so use another method to detect shell success.Fixes: 22119c4591a0 (&quot;examples: use pkg-config in makefiles&quot;)Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Wed, 03 Jul 2019 16:40:00 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ca926852 - examples: support relocated DPDK install</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#ca926852</link>
        <description>examples: support relocated DPDK installFor testing of DPDK, we want to override the prefix given by thepkg-config file, so that we can get correct paths for DPDK installedin an unusual location.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Tue, 02 Jul 2019 14:44:41 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>7e9562a1 - examples: fix make clean when using pkg-config</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#7e9562a1</link>
        <description>examples: fix make clean when using pkg-configThe &quot;make clean&quot; command had a number of issues:- the &quot;--ignore-fail-on-non-empty&quot; flag is not present on BSD- the call to remove the build folder would fail if there was no build  folder present.These are fixed by only removing the build folder if it exists, and byusing -p flag to rmdir in place of --ignore-fail-on-non-emptyFixes: 22119c4591a0 (&quot;examples: use pkg-config in makefiles&quot;)Cc: stable@dpdk.orgSigned-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Fri, 17 May 2019 12:02:31 +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/flow_classify/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/flow_classify/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/flow_classify/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/flow_classify/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>1842d194 - examples: enable linking both static and shared</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#1842d194</link>
        <description>examples: enable linking both static and sharedSince the DPDK build now includes both static and shared libraries, we needa new way to enable building the examples using either method from the oneinstallation. To do this, we add in a default &quot;shared&quot; target, and aseparate &quot;static&quot; target which links in the DPDK static libraries. In bothcases, the final application name is symlinked to the last-built static orshared target, with both binaries able to co-exist in the build directory.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Thu, 07 Dec 2017 15:51:41 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>22119c45 - examples: use pkg-config in makefiles</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#22119c45</link>
        <description>examples: use pkg-config in makefilesChange the example app Makefiles to query if DPDK is installed andregistered using pkg-config. If so, build directly using pkg-config info,otherwise fall back to using the original build system with RTE_SDK andRTE_TARGETThis commit changes the makefiles for the basic examples, i.e. those whichdo not have multiple subdirectories underneath the main examples dir.Examples not covered are:* ethtool* multi_process* performance-thread* quota_watermark* netmap_compat* server_node_efd* vm_power_managerSigned-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Reviewed-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Mon, 09 Oct 2017 13:13:16 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0eba4ade - examples: put app name and sources at top of makefiles</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#0eba4ade</link>
        <description>examples: put app name and sources at top of makefilesReorder the text in the makefiles, so that the app name and the sourcefiles are listed first. This then will allow them to be shared later in acombined makefile building with pkg-config and RTE_SDK-based build system.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Reviewed-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Mon, 25 Sep 2017 16:28:49 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>a6ec3159 - mk: add experimental tag check</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#a6ec3159</link>
        <description>mk: add experimental tag checkAdd checks during build to ensure that all symbols in the EXPERIMENTALversion map section have __experimental tags on their definitions, andenable the warnings needed to announce their use.  Also add anALLOW_EXPERIMENTAL_APIS define to allow individual libraries and filesto declare the acceptability of experimental api usageSigned-off-by: Neil Horman &lt;nhorman@tuxdriver.com&gt;Acked-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Mon, 22 Jan 2018 01:48:05 +0000</pubDate>
        <dc:creator>Neil Horman &lt;nhorman@tuxdriver.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/flow_classify/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/flow_classify/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>bab16dda - examples/flow_classify: add sample application</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/flow_classify/Makefile#bab16dda</link>
        <description>examples/flow_classify: add sample applicationThe flow_classify sample application exercises the followinglibrte_flow_classify API&apos;s:rte_flow_classifier_createrte_flow_classifier_queryrte_flow_classify_table_createrte_flow_classify_table_entry_addrte_flow_classify_table_entry_deleteIt sets up the IPv4 ACL field definitions.It creates table_acl and adds and deletes rules using thelibrte_table API.It uses a file of IPv4 five tuple rules for input.Signed-off-by: Bernard Iremonger &lt;bernard.iremonger@intel.com&gt;Acked-by: Jasvinder Singh &lt;jasvinder.singh@intel.com&gt;

            List of files:
            /dpdk/examples/flow_classify/Makefile</description>
        <pubDate>Tue, 24 Oct 2017 17:28:01 +0000</pubDate>
        <dc:creator>Bernard Iremonger &lt;bernard.iremonger@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
