From: Gavin Schenk <gavin.schenk@gmx.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Makefile in subfolder of rules directory?
Date: Mon, 10 Oct 2011 23:53:14 +0200 [thread overview]
Message-ID: <4E93694A.2070807@gmx.de> (raw)
In-Reply-To: <20111010212110.GJ18273@pengutronix.de>
> On Mon, Oct 10, 2011 at 06:31:41PM +0200, Gavin Schenk wrote:
>> Today we reviewed your hints and had a close look to the result of
>> ptxdist newpackage src-make-prog, but still have issues with it.
>> Maybe my question was too imprecise.
>>
>> It is possible to put the in-files into subdirectories e.g.
>> project/rules/somedir/test.in!
>> But in this example the corresponding makefile in
>> project/rules/somedir/test.make is not recognized by ptxdist.
>>
>> It seems to me, that ptxdist only scans project/rules but not any
>> subdirs for makefiles.
>
> Right, and this is by design.
>
> Why do you want to use a sub directory? The strategy is usually to put
> any project-local .in and .make files into rules/. Any file put there
> should be generic enough to be used in any config/platform to be used
> with the project, so I cannot imagine a good reason for splitting up
> into sub directories.
>
> rsc
The only reason is that I want to share the .in and .make files using
subversion, by checking out a common rules-folder as external into the
project. Changes to this external are visible to all colleagues
immediately, the external can be sticked to a version, switched to
trunk, tag, branch or whatever one need.
My solution is to check out the common_rules beside the projects
rules-folder and copy the common_rules content, using lndir, into the
rules-folder. That meets all requirements, I only have to update the
symbolic links after an update from subversion.
Thanks and Regards,
Gavin
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2011-10-10 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 12:35 Gavin Schenk
2011-10-07 13:08 ` Juergen Beisert
2011-10-10 16:31 ` Gavin Schenk
2011-10-10 21:21 ` Robert Schwebel
2011-10-10 21:53 ` Gavin Schenk [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=4E93694A.2070807@gmx.de \
--to=gavin.schenk@gmx.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