[yocto] GCC on ARM
Khem Raj
raj.khem at gmail.com
Thu Mar 30 22:07:27 PDT 2017
On 3/30/17 9:07 PM, Gary Thomas wrote:
> [slightly off-topic]
>
> I work with a number of embedded ARM devices, all with different
> processors, hence somewhat different tuning and build directories:
> Raspberry-Pi (1,2,3 - mostly 3):
> TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
> callconvention-hard cortexa7"
> build dirs:
> tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi
> BeagleBoneBlack:
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
> build dirs:
> tmp/work/armv7ahf-neon-poky-linux-gnueabi
> i.MX6:
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
> cortexa9"
> build dirs:
> tmp/work/cortexa9hf-neon-poky-linux-gnueabi
> tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi
> tmp/work/cortexa9t2hf-neon-mx6qdl-poky-linux-gnueabi
>
> What I'm wondering is, except for the obvious programs that use SoC
> specific
> functions like the IPU/GPU on the i.MX6, how different are these
> really? So
> much so that they have to all have unique binaries? Surely I could build
> busybox or python and run the same binary on all three?
>
You can chose a least common denominator and use that as DEFAULTTUNE for
all your machines. May be like armv7at2-neon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: OpenPGP digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170330/9a62551c/attachment.pgp>
More information about the yocto
mailing list