From: Javier Fileiv <javier.fileiv@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Different Scenario: how to solve it?
Date: Wed, 23 Oct 2013 09:52:43 +0200 [thread overview]
Message-ID: <CABvwO2DuA-icpsh4nbCOceuPra-0L_Wgdq=Vh3w7cdcBMjWvjA@mail.gmail.com> (raw)
In-Reply-To: <526700F2.30808@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
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
>
Thank you so much!
> Marc
>
> --
> Pengutronix e.K. | Marc Kleine-Budde |
> Industrial Linux Solutions | Phone: +49-231-2826-924 |
> Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
>
>
[-- Attachment #1.2: Type: text/html, Size: 1878 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-10-23 7:52 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
2013-10-25 8:11 ` Javier Fileiv
2013-10-23 7:52 ` Javier Fileiv [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='CABvwO2DuA-icpsh4nbCOceuPra-0L_Wgdq=Vh3w7cdcBMjWvjA@mail.gmail.com' \
--to=javier.fileiv@gmail.com \
--cc=mkl@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