DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lance Richardson <lance.richardson@broadcom.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] build: support i686 target on x86 64-bit hosts
Date: Thu, 24 Sep 2020 12:37:42 -0400	[thread overview]
Message-ID: <20200924163742.321600-1-lance.richardson@broadcom.com> (raw)

Add meson cross files for building i686 targets using gcc on x86_64
linux hosts.

Uusage example:

    meson --cross-file config/x86/cross-i686-linux-gcc build-i686
    ninja -C build-i686

Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
---
Red Hat distros use a different name for the 32-bit pkg-config
command from most other distros, maybe there is a better way
to handle this than using separate files.

Others will probably have better naming suggestions for the files.

 config/x86/cross-i686_linux_gcc  | 15 +++++++++++++++
 config/x86/cross-i686_redhat_gcc | 15 +++++++++++++++
 2 files changed, 30 insertions(+)
 create mode 100644 config/x86/cross-i686_linux_gcc
 create mode 100644 config/x86/cross-i686_redhat_gcc

diff --git a/config/x86/cross-i686_linux_gcc b/config/x86/cross-i686_linux_gcc
new file mode 100644
index 000000000..a4169f969
--- /dev/null
+++ b/config/x86/cross-i686_linux_gcc
@@ -0,0 +1,15 @@
+[binaries]
+c = 'gcc'
+ar = 'gcc-ar'
+strip = 'strip'
+pkgconfig = 'i686-linux-gnu-pkg-config'
+
+[properties]
+c_args = ['-m32']
+c_link_args = ['-m32']
+
+[host_machine]
+system = 'linux'
+cpu_family = 'x86'
+cpu = 'i686'
+endian = 'little'
diff --git a/config/x86/cross-i686_redhat_gcc b/config/x86/cross-i686_redhat_gcc
new file mode 100644
index 000000000..2ae8b33dd
--- /dev/null
+++ b/config/x86/cross-i686_redhat_gcc
@@ -0,0 +1,15 @@
+[binaries]
+c = 'gcc'
+ar = 'gcc-ar'
+strip = 'strip'
+pkgconfig = 'i686-redhat-linux-gnu-pkg-config'
+
+[properties]
+c_args = ['-m32']
+c_link_args = ['-m32']
+
+[host_machine]
+system = 'linux'
+cpu_family = 'x86'
+cpu = 'i686'
+endian = 'little'
-- 
2.25.1


             reply	other threads:[~2020-09-24 16:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 16:37 Lance Richardson [this message]
2020-09-25  9:13 ` Bruce Richardson
2020-09-25 13:27   ` Lance Richardson
2020-09-25 13:44     ` Bruce Richardson
2020-09-25 14:08       ` Lance Richardson
2020-09-25 14:28         ` Bruce Richardson
2020-09-25 14:48           ` Ferruh Yigit
2020-10-06  8:30     ` Thomas Monjalon
2020-10-06 14:35       ` Lance Richardson
2020-11-06 17:54         ` Thomas Monjalon
2020-11-06 18:02           ` Lance Richardson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200924163742.321600-1-lance.richardson@broadcom.com \
    --to=lance.richardson@broadcom.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).