<?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 test_pdump.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a9de470c - test: move to app directory</title>
        <link>http://172.16.0.5:8080/history/dpdk/app/test/test_pdump.h#a9de470c</link>
        <description>test: move to app directorySince all other apps have been moved to the &quot;app&quot; folder, the autotest appremains alone in the test folder. Rather than having an entire top-levelfolder for this, we can move it back to where it all started in earlyversions of DPDK - the &quot;app/&quot; folder.This move has a couple of advantages:* This reduces clutter at the top level of the project, due to one less  folder.* It eliminates the separate build task necessary for building the  autotests using make &quot;make test-build&quot; which means that developers are  less likely to miss something in their own compilation tests* It re-aligns the final location of the test binary in the app folder when  building with make with it&apos;s location in the source tree.For meson builds, the autotest app is different from the other apps in thatit needs a series of different test cases defined for it for use by &quot;mesontest&quot;. Therefore, it does not get built as part of the main loop in theapp folder, but gets built separately at the end.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/app/test/test_pdump.h</description>
        <pubDate>Tue, 26 Feb 2019 12:19:03 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
