Hei hei,

On Fri, Jun 19, 2020 at 10:08:14AM +0200, Bastian Krause wrote:
> On 6/19/20 9:51 AM, Mircea Ciocan wrote:
> > I have some configuration files that are package independent, but board
> > depended, is there a solution to add them in bulk to the root filesystem.
> > 
> > It seem that configs/platform-XXX/projectroot only holds configuration
> > files that overrides the default ALREADY EXISTING files in the root file
> > system, all other files seem to be ignored.
> > 
> > Is there some "magic" setting that allows a full projectroot copy and
> > overwrite/add the content to the rootfs or is there another way to get a
> > similar effect ?

Create another package for those files. That's what we did at work in
our BSPs.

> Only files that are installed by an enabled package using
> install_alternative(_tree) [1][2] are taken from projectroot.
> 
> Create a new target package with "ptxdist newpackage target", remove
> everything but PACKAGES-$(PTXCONF_YOURPACKAGE), YOURPACKAGE_VERSION,
> YOURPACKAGE_LICENSE and the targetinstall stage. In the targetinstall
> stage you can use install_alternative_tree [2] to install "the whole
> source directory tree with all files" [2].

I would suggest `ptxdist newpackage file` which seems to be the
template for exactly that usecase. Of course you could go with every
other template and adapt it or create a package from scratch, but the
'file' template gives you a very simple .in rule and a .make rule with
just the targetinstall stage active, you don't need more to just
install some files to the target.

Greets
Alex

-- 
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN     | speech censured, the first thought forbidden, the
 X  AGAINST      | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL    | (Jean-Luc Picard, quoting Judge Aaron Satie)

Attachment: signature.asc
Description: PGP signature

_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to 
[email protected]

Reply via email to