All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Jonathan Austin <jonathan.austin@arm.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: ADT/SDK and cmake - generating the toolchain/cmake config
Date: Tue, 01 Apr 2014 17:49:56 -0700	[thread overview]
Message-ID: <533B5EB4.2000703@balister.org> (raw)
In-Reply-To: <533AE7CE.6070708@arm.com>

On 04/01/2014 09:22 AM, Jonathan Austin wrote:
> Hi all,
> 
> The ADT documentation walks you through building an 'app' using
> autoconf/make, and the environment setup script that is created as part
> of the SDK build contains all the necessary autofoo/environment
> variables. This is great, and I've worked through the autotools example
> happily. Thanks :)
> 
> What I can't find, though, is anything that does the equivalent for
> cmake. I'm new to cmake so could be missing something obvious, but after
> seeing the 'environment-setup-TARGET' files (the ones at
> /opt/poky/1.5.1/) I thought there might also be a cmake toolchain file
> (toolchain-TARGET.cmake, for example) or some other cmake-foo.
> 
> I can see that cmake support was merged for Eclipse/ADT, so it seems
> like cmake could be supported 'outside the IDE', but I can't quite see
> how what I ought to twiddle to do this. I found the tantalizingly named
> 'cmake_do_generate_toolchain_file()' and all the other relevant stuff in
> meta/classes/cmake.bbclass, but I don't know what the 'right' way to
> propagate all that stuff into the SDK/ADT would be.
> 
> Any help with getting started would be greatly appreciated.

This toolchain file builds gnuradio from an SDK:

https://github.com/gnuradio/gnuradio/blob/master/cmake/Toolchains/oe-sdk_cross.cmake

Does this help?

Philip

> 
> Thanks
> Jonny
> 


  reply	other threads:[~2014-04-02  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 16:22 ADT/SDK and cmake - generating the toolchain/cmake config Jonathan Austin
2014-04-02  0:49 ` Philip Balister [this message]
2014-04-11 15:23   ` Jonathan Austin

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=533B5EB4.2000703@balister.org \
    --to=philip@balister.org \
    --cc=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.