All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: cmake
Date: Thu, 02 Apr 2009 20:07:54 +0200	[thread overview]
Message-ID: <gr2utq$hj4$2@ger.gmane.org> (raw)
In-Reply-To: <be7a9f3d0904020944h4d4c6d6dgac1a2e75163d8cf3@mail.gmail.com>

On 02-04-09 18:44, Otavio Salvador wrote:
> On Thu, Apr 2, 2009 at 2:30 AM, Jeremy Lainé
> <jeremy.laine@bolloretelecom.eu>  wrote:
>> Shane Dixon wrote:
>>> I'm considering changing my projects over to cmake, but before I do, I
>>> wanted to ask how good the cmake support is in OE.  I saw a recent
>>> proposal to allow out-of-tree builds for cmake, but I'm not sure if that
>>> happened or not.
>>
>> At work we recently switched our projects over to CMake and they are building happily in
>> OE. Out-of-tree builds are indeed supported, see recipes/llvm/llvm.inc for an example.
>
> What do you mean by out-of-tree?

S=work/foo-1.2-r0/foo-1.2/
B=work/foo-1.2-r0/build-foo-1.2

All generated stuff (makefiles, objects, binaries, etc) will end up in B 
so that S stays clean.

I'd like out-of-tree builds to be the default for autotools and cmake, 
but there are way too many broken autofoo and cmake using packages out 
there :(

regards,

Koen





  reply	other threads:[~2009-04-02 18:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 17:35 cmake Shane Dixon
2009-04-02  5:30 ` cmake Jeremy Lainé
2009-04-02 16:44   ` cmake Otavio Salvador
2009-04-02 18:07     ` Koen Kooi [this message]
2009-04-02 17:07 ` cmake Robert Schuster
2015-12-03 22:24 cmake Pete Zaitcev
2015-12-03 22:30 ` cmake Adam C. Emerson
2015-12-04  0:03   ` cmake Pete Zaitcev
2015-12-04  0:26     ` cmake Matt Benjamin
2015-12-04  8:59       ` cmake Pete Zaitcev
2015-12-04 14:15         ` cmake Daniel Gryniewicz
2015-12-03 22:30 ` cmake Matt Benjamin
2015-12-03 22:31   ` cmake Matt Benjamin
2015-12-16 17:33 cmake Sage Weil
2015-12-16 17:53 ` cmake Loic Dachary
2015-12-16 18:28 ` cmake John Spray
2015-12-16 19:36   ` cmake Sage Weil
2015-12-16 18:45 ` cmake Yehuda Sadeh-Weinraub
2015-12-16 19:06   ` cmake Matt Benjamin
2015-12-16 19:38     ` cmake Sage Weil
2015-12-16 23:47       ` cmake Willem Jan Withagen
2015-12-16 23:36   ` cmake Willem Jan Withagen
2016-06-27 17:50 cmake Sage Weil
2016-06-28  7:35 ` cmake Willem Jan Withagen
2016-06-28  8:41   ` cmake Willem Jan Withagen
2016-06-28  8:57     ` cmake Willem Jan Withagen
2016-06-28 13:42   ` cmake Sage Weil
2016-06-28 16:05     ` cmake Willem Jan Withagen
2016-06-29 16:51       ` cmake Willem Jan Withagen
2016-06-30 19:03         ` cmake Willem Jan Withagen
2016-07-05 19:09     ` cmake Willem Jan Withagen
2016-06-28 20:28 ` cmake Casey Bodley
2016-06-28 21:43   ` cmake Mark Nelson
2016-07-04  9:05 ` cmake Willem Jan Withagen
2016-07-04 10:37   ` cmake Brad Hubbard

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='gr2utq$hj4$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.