mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Javier Fileiv <javier.fileiv@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Different Scenario: how to solve it?
Date: Fri, 25 Oct 2013 09:44:35 +0200	[thread overview]
Message-ID: <CABvwO2AnpDTFN=LL+4KGei84YkCzHjwiPx2H6-746nOJ+m0PNQ@mail.gmail.com> (raw)
In-Reply-To: <20131024221814.GF9225@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2058 bytes --]

2013/10/25 Michael Olbrich <m.olbrich@pengutronix.de>

> On Thu, Oct 24, 2013 at 11:51:47AM +0200, Javier Fileiv wrote:
> > 2013/10/24 Michael Olbrich <m.olbrich@pengutronix.de>
> >
> > > 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.
> >
> >
> > What I meant with that is if I can add my bash instruction on every
> section
> > to be executed.For example if  I call 'ptxdist prepare MY_PACKAGE' and I
> > write 'echo "MY OWN PREPARE STRING" ' in the .make file, it will write
> out
> > "MY OWN PREPARE STRING" on the console output.
> >
> > Did you get what I try to say? Sorry.. it's my mistake if not.
>
> The stages are just make targets. You can do anything you want there.
> Take a look at e.g. rules/python.make in ptxdist. It does some extra stuff
> before calling world/prepare (which then runs configure).
>
> Michael
>
> I will !! Thank you very much!

> --
> 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
>

[-- Attachment #1.2: Type: text/html, Size: 3418 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-10-25  7:44 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
2013-10-24  9:51       ` Javier Fileiv
2013-10-24 22:18         ` Michael Olbrich
2013-10-25  7:44           ` Javier Fileiv [this message]
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='CABvwO2AnpDTFN=LL+4KGei84YkCzHjwiPx2H6-746nOJ+m0PNQ@mail.gmail.com' \
    --to=javier.fileiv@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