From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Different Scenario: how to solve it?
Date: Thu, 24 Oct 2013 10:55:52 +0200 [thread overview]
Message-ID: <20131024085552.GD9225@pengutronix.de> (raw)
In-Reply-To: <CABvwO2BNEknkL3Brp1=NoKK9UnJJBWLM7NMoQUH0BaJwDDNwLg@mail.gmail.com>
On Wed, Oct 23, 2013 at 09:52:05AM +0200, Javier Fileiv wrote:
> 2013/10/23 Marc Kleine-Budde <mkl@pengutronix.de>
> > On 10/22/2013 03:44 PM, Javier Fileiv wrote:
> > > Hello everyone, I have the following scenario.
> > >
> > > My package is in a folder, where there is another folder inside which
> > > contains the Makefile. No autotools is required.
> > >
> > > If I create a newpackge with ptxdist newpackage target, it will create
> > > the .make and .rule file. But how can I tell to the "compile" step that
> > > my Makefile is in ./src an not in ./ ?? I was trying to add a simple
> >
> > define in your .make file
> >
> > <PACKAGE>_SUBDIR := src
> >
> >
> Am I able to add my own bash scripts there?
I don't understand this.
> Also, is it possible to get a package from git instead of from the web? How
> can I do that?
<PACKAGE>_URL := git://git.some-host.net/foo.git;tag=v42
Note: this only works with fix versions you cannot track a branch.
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
next prev parent reply other threads:[~2013-10-24 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 13:44 Javier Fileiv
2013-10-22 22:49 ` Marc Kleine-Budde
2013-10-23 7:52 ` Javier Fileiv
2013-10-24 8:55 ` Michael Olbrich [this message]
2013-10-24 9:51 ` Javier Fileiv
2013-10-24 22:18 ` Michael Olbrich
2013-10-25 7:44 ` Javier Fileiv
2013-10-25 8:11 ` Javier Fileiv
2013-10-23 7:52 ` Javier Fileiv
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=20131024085552.GD9225@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