From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Overwriting rules
Date: Thu, 31 Jul 2014 14:23:21 +0200 [thread overview]
Message-ID: <20140731122321.GJ29377@pengutronix.de> (raw)
In-Reply-To: <CAMyOCn_Go6zJ6odHW6BtYj92YgLbrhOvS=xpkSEyY+HMkhyb1g@mail.gmail.com>
On Thu, Jul 31, 2014 at 01:38:44PM +0200, Wim Vinckier wrote:
> On Thu, Jul 31, 2014 at 12:10 PM, Michael Olbrich <m.olbrich@pengutronix.de>
> wrote:
> > On Thu, Jul 31, 2014 at 12:02:25PM +0200, Wim Vinckier wrote:
> > > I thought I could overwrite an existing rule by adding a rule with the
> > same
> > > name in my rules directory but ptxdist doesn't seem to pick up the .make
> > > file. Running 'ptxdist menuconfig' I see it uses new 'inadyn.in' but my
> > > modified 'inadyn.make' isn't used.
> > >
> > > Did I think wrong or what I can do wrong?
> >
> > Check platform-<something>/state/ptx_dgen_rulesfiles.make
> > All used makefiles are included there and you should see which version is
> > used.
> >
> > Michael
> >
> >
> Thanks for the hint. When checking the file, I found he never picked up a
> make-file from my rules directory. My rules directory is a link to
> repository I checked out elsewhere. I copied the directory as a test and
> that way it works. Is there anyway I can use a link there?
I've fixed this in ptxdist master. Until you can use that, the only
solution I see is to create the directory and link the individual files.
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:[~2014-07-31 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 10:02 Wim Vinckier
2014-07-31 10:10 ` Michael Olbrich
2014-07-31 10:57 ` wim vinckier
2014-07-31 11:38 ` Wim Vinckier
2014-07-31 12:23 ` Michael Olbrich [this message]
2014-07-31 12:38 ` Wim Vinckier
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=20140731122321.GJ29377@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