From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Building local package out of tree
Date: Thu, 29 Jan 2015 12:27:44 +0100 [thread overview]
Message-ID: <CABDcavZioDc-AWZiVuhBqobt1uAX-w4qZgLvd1JBf__861-qow@mail.gmail.com> (raw)
In-Reply-To: <54CA0EA3.5040706@pengutronix.de>
Hi Markus,
2015-01-29 11:42 GMT+01:00 Marc Kleine-Budde <mkl@pengutronix.de>:
>
> On 01/29/2015 09:45 AM, Guillermo Rodriguez Garcia wrote:
> > Hello,
> >
> > 2015-01-28 21:29 GMT+01:00 Alexander Dahl <post@lespocky.de
> > <mailto:post@lespocky.de>>:
> >
> > Hei,
> >
> > On 28.01.2015 16:25, Alexander Stein wrote:
> > > For building out of tree; I would suggest using cmake. This makes
> > > building OOT quite an easy task. As you only have a simple makefile
> > > setting up CMakeLists.txt is not that hard. If the build process is
> > > more complicated you anyway want to use a build system like cmake.
> >
> > +1
> >
> >
> > I appreciate the suggestions :) but this is not what I am looking for.
> > Specially since ptxdist already knows how to do what I want to do. In
> > fact it does exactly that when you create a "src-linux-driver" package:
> > The sources are copied from local_src/<pkg> to a directory
> > platform/build-target/<pkg> and built there. I just need to figure out
> > how to make ptxdist do the same for a regular "src-make-prog" package.
>
> Try using
>
> FOO_URL := lndir://$(PTXDIST_WORKSPACE)/local_src
> ^^^^^
Works perfect! This is exactly what I was looking for.
Thank you,
Guillermo
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-01-29 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 15:19 Guillermo Rodriguez Garcia
2015-01-28 15:25 ` Alexander Stein
2015-01-28 15:34 ` Guillermo Rodriguez Garcia
2015-01-28 20:29 ` Alexander Dahl
2015-01-29 8:45 ` Guillermo Rodriguez Garcia
2015-01-29 10:42 ` Marc Kleine-Budde
2015-01-29 11:27 ` Guillermo Rodriguez Garcia [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=CABDcavZioDc-AWZiVuhBqobt1uAX-w4qZgLvd1JBf__861-qow@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--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