From: "Dörfler Florian" <Florian.Doerfler@scs.ch>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Using CMake/CPack install info in targetinstall step
Date: Wed, 8 Apr 2015 11:08:54 +0200 [thread overview]
Message-ID: <E0CB834DD9BF7546A8B709A96E2ECAC301551235CA73@Exchange.scs-ad.scs.ch> (raw)
Hello All
I wonder if I can simplify the install step for a CMake based target package and need a sanity check and a pointer to some info:
If I have understood, then the flow of the compiled packet's output is the following:
1) the "make install" step of the build of a packet copies the relevant files binaries/headers to the platform-<xyz>/sysroot-target/ directory
2) $(call install_copy, ...) and friends copy the files needed in the root FS to platform-<xyz>/root and create a packet
I could like to try and get rid of one of these lists of file to copy: If I use CMake to build the packet in step 1), I have already described the installation directions pretty detailed. I wonder if I can reuse that info for step 2).
The way I would go about it is this: I put a little more info into the CMakeLists.txt file and use CPack to create the .ipkg packet. Then I smuggle this package into the install flow.
Does this sound reasonable?
If yes: Can anybody point me to some info on how I can make the targetinstall step use an existing ipkg?
I use ptxdist 2015.02.0
Cheers
Florian
--
Florian Dörfler, Development Engineer
Direct +41 (0)43 456 16 01 . Phone +41 (0)43 456 16 00 . www.scs.ch
Supercomputing Systems AG . Technoparkstrasse 1 . CH-8005 Zürich
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-04-08 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 9:08 Dörfler Florian [this message]
2015-04-09 8:50 ` Michael Olbrich
2015-04-09 9:36 ` Dörfler Florian
2015-04-09 9:46 ` Michael Olbrich
2015-06-02 11:42 ` Dörfler Florian
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=E0CB834DD9BF7546A8B709A96E2ECAC301551235CA73@Exchange.scs-ad.scs.ch \
--to=florian.doerfler@scs.ch \
--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