<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anderson Rodrigues on Medium]]></title>
        <description><![CDATA[Stories by Anderson Rodrigues on Medium]]></description>
        <link>https://medium.com/@ansorod?source=rss-2d31f7ea54eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FR_-_9Qlb7clkX0u_zzFzw.jpeg</url>
            <title>Stories by Anderson Rodrigues on Medium</title>
            <link>https://medium.com/@ansorod?source=rss-2d31f7ea54eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:15:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ansorod/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to compile iperf3 for Android]]></title>
            <link>https://medium.com/@ansorod/how-to-compile-iperf3-for-android-4d67c9a7f061?source=rss-2d31f7ea54eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d67c9a7f061</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[iperf]]></category>
            <category><![CDATA[network]]></category>
            <category><![CDATA[android-ndk]]></category>
            <dc:creator><![CDATA[Anderson Rodrigues]]></dc:creator>
            <pubDate>Fri, 02 Oct 2020 19:33:41 GMT</pubDate>
            <atom:updated>2020-10-05T13:18:55.401Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a straightforward guide on how to compile iperf3 for Android</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PyqEpsAA_vSO4bkNRajXdQ.jpeg" /><figcaption>Recife, Pernambuco, Brazil</figcaption></figure><p>After struggling for a couple of hours trying to build an executable for Android using a stable version of iperf3 source code I finally came to a happy ending.</p><p>This article is more like a guide on how to achieve that than anything else, so if you&#39;re having any problems doing so I hope this can help you.</p><h3>First things first</h3><p>In order to get iperf3 compiled for Android you&#39;ll need:</p><ul><li>iperf3 source code — You can find it here: <a href="https://github.com/esnet/iperf">https://github.com/esnet/iperf</a></li><li>Android NDK — Download it here: <a href="https://developer.android.com/ndk/downloads">https://developer.android.com/ndk/downloads</a></li></ul><h3>Android Toolchain</h3><p>Compiling for Android? We&#39;re gonna need an Android Toolchain! That&#39;s why we have just downloaded the Android NDK. So let&#39;s make a toolchain available.</p><p>Go to your Android NDK location and access the folder <em>build/tools</em></p><blockquote>cd PATH_TO_YOUR_NDK/build/tools</blockquote><p>Once there, run the command:</p><blockquote>./make-standalone-toolchain.sh — toolchain=arm-linux-androideabi-4.9 — arch=arm — install-dir=YOUR_OUTPUT_DIR — platform=android-24 — force</blockquote><p>Parameters:</p><ul><li>— toolchain: the name of the toolchain you&#39;re making. Android NDK comes with some toolchains. To check which ones are available go to the folder <em>toolchains</em> under your Android NDK location</li><li>— arch: name of the processor architecture you&#39;re building to, in this case we&#39;re using arm as the majority of Android devices run on this architecture</li><li>— install-dir: this is the directory where the toolchain will be installed</li><li>— platform: as in Android projects, this is the Android API version you&#39;re building to</li><li>— force: this parameter ensure that you&#39;re doing a fresh install. If there&#39;s any file in the install-dir related to the toolchain, it&#39;ll be erased and new ones will be created</li></ul><h3>Getting there!</h3><p>Once you have the toolchain installed it&#39;s time to pay iperf3 some attention.</p><p>Go to your iperf3 source code location and there will be a <em>configure</em> file. This file is the entry point of all configuration you might need to do to compile iperf3 in a no default way.</p><p>Run the following:</p><blockquote>./configure -host=arm-none-eabi CXX=PATH_TO_ANDROID_TOOLCHAIN/bin/arm-linux-androideabi-g++ CXXFLAGS=-static CC=PATH_TO_ANDROID_TOOLCHAIN/bin/arm-linux-androideabi-gcc CFLAGS=-static -C AR=PATH_TO_ANDROID_TOOLCHAIN/bin/arm-linux-androideabi-ar RANLIB=PATH_TO_ANDROID_TOOLCHAIN/bin/arm-linux-androideabi-ranlib — prefix=YOUR_IPERF3_INSTALL_DIRECTORY</blockquote><p>Parameters:</p><ul><li>— host: system we&#39;re compiling to. In this case we&#39;re using arm-none-eabi that abstracts processor vendors and customisation, so it &quot;should run&quot; on any arm based device</li><li>CXX: C++ compiler</li><li>CXXFLAGS: flags for C++ compiler</li><li>CC: C compiler</li><li>CFLAGS: flags for C compiler</li><li>AR: archiver</li><li>RANLIB: indexer</li><li>— prefix: directory where iperf3 will be installed</li></ul><h3><strong>Make it!</strong></h3><p>Final step is to make it:</p><blockquote>make; make install;</blockquote><p>When finished, iperf3 will be available at<em> — prefix </em>specified location<em>. </em>The executable is found under the <em>bin</em> folder.</p><h3>This is it</h3><p>That&#39;s all! After finishing building you can use the iperf3 executable in your Android devices via <em>adb </em>or in your application.</p><p>Thanks <a href="https://medium.com/u/a90dde4db206">Thiago Lopes Silva</a> and <a href="https://medium.com/u/6b46e51641a">Wallace Thierre</a> for your contribution :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d67c9a7f061" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>