From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Juan A. Rubio" <jarubio2001@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Same 32-bit image for 64-bit and 32-bit platforms
Date: Mon, 27 Dec 2021 09:59:56 +0100 [thread overview]
Message-ID: <20211227095956.120b796e@windsurf> (raw)
In-Reply-To: <CAE58QoPWoZdZq=cOpo0MRJXgZDfa5Ad07HtYooT9LKho5KRS8A@mail.gmail.com>
Hello Juan,
On Mon, 27 Dec 2021 09:40:00 +0100
"Juan A. Rubio" <jarubio2001@gmail.com> wrote:
> I'm looking for information on whether it's possible to produce and
> use the same Buildroot image and associated sdk for two different
> boards, one based on an imx6 and the other on imx8. Is this something
> that Buildroot supports at all? do I need two separate Buildroot
> environments/builds, one for the 32-bit imx6 and another for the
> 64-bit imx8?
You will need different Buildroot builds yes, but you can use a single
Buildroot source tree. Basically, your i.MX6 system will need one
Buildroot configuration (.config file / defconfig file) and your i.MX8
system will need another Buildroot configuration (another .config file
/ defconfig file).
You can build both configurations in parallel based on the same
Buildroot source tree using "out of tree" build, see
https://buildroot.org/downloads/manual/manual.html#_building_out_of_tree.
Hope this helps,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-12-27 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 8:40 [Buildroot] Same 32-bit image for 64-bit and 32-bit platforms Juan A. Rubio
2021-12-27 8:59 ` Thomas Petazzoni [this message]
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=20211227095956.120b796e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=jarubio2001@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.