From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] Add CMAKETARGETS infrastructure for CMake packages
Date: Thu, 23 Dec 2010 08:46:44 +0100 [thread overview]
Message-ID: <20101223084644.018fa724@surf> (raw)
In-Reply-To: <AANLkTi=frxyYAzAaApiwAfxairhSKe38qkBgvk633_eF@mail.gmail.com>
Hello,
On Wed, 22 Dec 2010 22:34:17 +0100
Samuel Martin <s.martin49@gmail.com> wrote:
> srctree:
> output/build/cdrkit-1.1.10
> buildtree:
> output/build/cdrkit-1.1.10/build
> Like this, we keep only one directory per package and don't mess up the
> source tree.
> Whatever, both solutions are good. For me, it's not a big deal, but maybe BR
> leaders will prefer one or the other solution to keep it consistent.
I agree.
> > but give CMake CFLAGS/CXXFLAGS on the commandline when building internal
> > packages?
>
> If we need, yes, but i am quite doubtful about the usefulness of these
> flags.
Huh ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-23 7:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 19:29 [Buildroot] [PATCH 0/4] Introducing CMAKETARGETS infrastructure Bjørn Forsman
2010-12-12 19:29 ` [Buildroot] [PATCH 1/4] Add CMAKETARGETS infrastructure for CMake packages Bjørn Forsman
2010-12-13 22:27 ` Samuel Martin
2010-12-14 11:13 ` Bjørn Forsman
2010-12-22 21:34 ` Samuel Martin
2010-12-23 7:46 ` Thomas Petazzoni [this message]
2010-12-23 8:46 ` Bjørn Forsman
2010-12-23 8:54 ` Thomas Petazzoni
2010-12-23 9:14 ` Bjørn Forsman
2011-01-07 17:17 ` Thomas Petazzoni
2011-01-08 23:44 ` Bjørn Forsman
2011-01-10 17:51 ` Thomas Petazzoni
2011-01-10 20:14 ` Bjørn Forsman
2010-12-12 19:29 ` [Buildroot] [PATCH 2/4] doc: add CMAKETARGETS documentation Bjørn Forsman
2010-12-12 19:29 ` [Buildroot] [PATCH 3/4] Makefile: generate CMake toolchain file in $(O) Bjørn Forsman
2010-12-13 22:27 ` Samuel Martin
2010-12-14 12:39 ` Bjørn Forsman
2010-12-22 21:32 ` Samuel Martin
2010-12-23 7:48 ` Thomas Petazzoni
2010-12-24 12:25 ` Samuel Martin
2010-12-23 9:04 ` Bjørn Forsman
2010-12-24 12:26 ` Samuel Martin
2011-01-07 17:15 ` Thomas Petazzoni
2011-01-08 23:42 ` Bjørn Forsman
2011-01-09 12:52 ` Bjørn Forsman
2011-01-09 14:08 ` Thomas Petazzoni
2011-01-10 17:50 ` Thomas Petazzoni
2011-01-10 18:30 ` Bjørn Forsman
2011-01-10 22:28 ` Thomas Petazzoni
2011-01-11 10:22 ` Thomas Petazzoni
2011-01-11 10:27 ` Thomas Petazzoni
2011-01-15 13:50 ` Bjørn Forsman
2010-12-12 19:29 ` [Buildroot] [PATCH 4/4] cdrkit: convert to CMAKETARGETS infrastructure Bjørn Forsman
2010-12-13 22:28 ` Samuel Martin
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=20101223084644.018fa724@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.