All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Austin <jonathan.austin@arm.com>
To: yocto@yoctoproject.org
Subject: ADT: understanding YOCTOADT_TARGET_MACHINE_arch
Date: Wed, 12 Mar 2014 18:08:07 +0000	[thread overview]
Message-ID: <5320A287.80608@arm.com> (raw)

Hi list,

I've been looking at the ADT, and specifically building a custom SDK/ADT 
for a particular board...

This is an ARM board, so I thought I'd set:
YOCTOADT_TARGET_MACHINE_arm="myboard"

Sadly, that doesn't work. I'm trying to understand why.

Despite changing YOCTOADT_REPO in my adt_installer.conf, the 
adt_installer fails to find the cross canadian package group for my board...

Unknown package 'packagegroup-cross-canadian-myboard

Looking at the log, I see that the installer is still looking on the 
yocto servers for (nativesdk) files. I can see that the nativesdk 
locations are hard-coded in opkg/conf/opkg-sdk-i686.conf - so I guess it 
isn't surprising that it can't find the right board, the Yocto servers 
know nothing of myboard at this stage!

Seeing those hardcoded paths made me wonder if I was using the 
YOCTOADT_TARGET_MACHINE_arm variable wrong...

Would it be 'right' to specify just 'arm' here? This is an imx6 board, 
and TARGET_SYS = "arm-poky-linux-gnueabi". By my understanding, this 
will affect which toolchain I get, among other things. I'd defintiely 
like a machine specific sysroot, for example[1]

So - what's the meaning/point of this TARGET_MACHINE_arch option? I see 
that there exists:
packagegroup-cross-canadian-imx53qsb_1.0-r0_all.ipk

  - so clearly someone's felt the need to use something other than just 
'arm' here in the past!

Has anyone else done an ADT for a custom board that uses the ADT 
infrastructure?

Do you create a detailed overlay to the adt-installer recipe and change 
config, etc?

It feels a little like I'm missing a step when generating the ADT that 
tells it more important details about what I'm creating - if so, sorry 
for the questions, but please could you point me there?

Thanks

Jonny

[1] I think that my images currently have to be called 'core-image-xxx' 
to work with existing ADT scripts, unless I'm missing some config 
somewhere, but that's a different issue that I'll dig into shortly




             reply	other threads:[~2014-03-12 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 18:08 Jonathan Austin [this message]
2014-05-03 15:47 ` ADT: understanding YOCTOADT_TARGET_MACHINE_arch Andrea Galbusera

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=5320A287.80608@arm.com \
    --to=jonathan.austin@arm.com \
    --cc=yocto@yoctoproject.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 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.