From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] schedtool: add package
Date: Thu, 4 Oct 2012 14:21:17 +0200 [thread overview]
Message-ID: <20121004122117.GI19651@pengutronix.de> (raw)
In-Reply-To: <84D7328F545A4040B6CE2CB7BE091E937AAA93@exchange.Neuberger.local>
On Mon, Oct 01, 2012 at 09:39:14AM +0200, Wagner Martin wrote:
> > > +
> > > +SCHEDTOOL_CONF_TOOL := NO
> > > +SCHEDTOOL_MAKE_ENV := $(CROSS_ENV)
> >
> > add CPPFLAGS="$(CROSS_CFLAGS) $(CROSS_CPPFLAGS)" here.
> > Otherwise the CROSS_CFLAGS set by ptxdist are missing (e.g.
> > PTXCONF_TARGET_EXTRA_CFLAGS).
>
> Is there a documentation available about those flags, which are avaliable and
> which one to use in which case? In "how to become a PTXdist Guru" there are
> only a few. Looking what other people have done in other packages also didn't
> help me much further as it seems that everyone is doing it a little
> different...
Unfortunately not. Take a look at rules/pre/Rules.make. The flags and tools
defined there should always be used.
> Can you give me a hint which package I can use as a example of how it should
> be done? Or are the packages all this different from each other so that there
> are just no similar ones?
There is no good example, because every Makefile is broken in different
ways. You can look at the packages (grep -l '_CONF_TOOL.*NO' rules/*.make)
with plain Makefiles. It should give you some ideas, but please note, that
some of them are not correct either.
> > I know this is not easy to spot. So for testing things like
> > this I usually
> > have:
> > PTXCONF_TARGET_EXTRA_CPPFLAGS="-Iptx-cppflags"
> > PTXCONF_TARGET_EXTRA_CFLAGS="-Iptx-cflags"
> > PTXCONF_TARGET_EXTRA_CXXFLAGS="-Iptx-cxxflags"
> > PTXCONF_TARGET_EXTRA_LDFLAGS="-Lptx-ldflags"
> >
> > to see which flags are really added to the command line.
>
> What are those variables supposed to do? I've built my package once with
> and once without them, but there is no difference on what is displayed.
These variables are set in the platformconfig. If you use CROSS_CFLAGS etc.
then they should show up as compiler flags.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-10-04 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 13:56 Wolf Erik
2012-09-30 13:01 ` Michael Olbrich
2012-10-01 7:39 ` Wagner Martin
2012-10-04 12:21 ` Michael Olbrich [this message]
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=20121004122117.GI19651@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox