From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]
	ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <mol@pengutronix.de>) id 1Yg8Ak-0004YL-4S
	for ptxdist@pengutronix.de; Thu, 09 Apr 2015 10:50:50 +0200
Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80)
	(envelope-from <mol@pengutronix.de>) id 1Yg8Ak-0002QR-2i
	for ptxdist@pengutronix.de; Thu, 09 Apr 2015 10:50:50 +0200
Date: Thu, 9 Apr 2015 10:50:50 +0200
From: Michael Olbrich <m.olbrich@pengutronix.de>
Message-ID: <20150409085050.GH21218@pengutronix.de>
References: <E0CB834DD9BF7546A8B709A96E2ECAC301551235CA73@Exchange.scs-ad.scs.ch>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <E0CB834DD9BF7546A8B709A96E2ECAC301551235CA73@Exchange.scs-ad.scs.ch>
Subject: Re: [ptxdist] Using CMake/CPack install info in targetinstall step
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

On Wed, Apr 08, 2015 at 11:08:54AM +0200, D=F6rfler Florian wrote:
> I wonder if I can simplify the install step for a CMake based target pack=
age
> 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 th=
e following:
> 1) the "make install" step of the build of a packet copies the relevant f=
iles
> binaries/headers to the platform-<xyz>/sysroot-target/ directory

rNnot quite: In pkg.install "make install" installs to
platform-<xyz>/packages/<pkg>/ and int pkg.install.post everything there is
copied to sysroot-target/ (with some path fixups).

> 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.

No need for that. platform-<xyz>/packages/<pkg>/ contains all the files
installed by "make install", so just use install_tree in targetinstall:

	@$(call install_tree, <pkg>, 0, 0, -, /)


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