From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailrelay04.sunrise.ch ([194.158.229.47] helo=smtp-be-02.be08.sunrise.ch) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1Ocgp4-0001JE-1K for openembedded-devel@lists.openembedded.org; Sat, 24 Jul 2010 17:40:57 +0200 Received: from [192.168.26.14] (212-98-43-140.static.adslpremium.ch [212.98.43.140]) by smtp-be-02.be08.sunrise.ch (8.13.1/8.12.10) with ESMTP id o6OFdENT031974; Sat, 24 Jul 2010 17:39:15 +0200 Message-ID: <4C4B0953.602@vollmann.ch> Date: Sat, 24 Jul 2010 17:40:03 +0200 From: Detlef Vollmann User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4C4AE42C.5000306@welchs.me.uk> <4C4B0125.1040304@vollmann.ch> In-Reply-To: X-SA-Exim-Connect-IP: 194.158.229.47 X-SA-Exim-Mail-From: dv@vollmann.ch X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: [RFC] get rid of legacy staging X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2010 15:41:33 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks! Detlef On 07/24/10 17:17, Koen Kooi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 24-07-10 17:05, Detlef Vollmann wrote: >> On 07/24/10 16:35, Frans Meulenbroeks wrote: >>> 2010/7/24 Martyn Welch >>> >>>> Can anyone point me to any documentation that describes what legacy >>>> staging >>>> is and roughly what needs to be done to remove it? >>> There was a post half a year or so ago from Koen, but I can't find it. >>> Basically it boils down to removing do_stage from a recipe in which case >>> do_install is used to install things in staging >>> in some cases do_install need to be modified to deal with >>> peculiarities that >>> were done in do_stage >>> >>> For native recipes NATIVE_INSTALL_WORKS = "1" may need to be added. >> That's not really much of an explanation. >> Let's take an example. I have two out of tree kernel modules A and B. >> B depends on A. >> With "legacy" staging, in A_1.0.bb I have a do_install, that copies >> the kernel object, and a do_stage, that copies the header file at >> a place where B_1.0.bb can find it. >> >> How do I do that with non-"legacy" staging? > > You copy the header in do_install to ${D}${includedir} or a subdir of > that depending on the header. > > Cheat sheet: > > STAGING_BINDIR -> ${D}${bindir} > STAGING_INCDIR -> ${D}${includedir} > STAGING_LIBDIR -> ${D}${libdir} > STAGING_DATADIR -> ${D}${datadir} > > And if your recipe uses BBCLASS_EXTEND = native *and* 'make install' > doesn't do the job (e.g. using do_install_append), use > NATIVE_INSTALL_WORKS = "1" > > If you use packaged-staging it's easy to do dpkg-deb -c on the staging > packages before and after the changes. > > regards, > > Koen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFMSwP0MkyGM64RGpERAlrAAJ0Rn/6RY3f/wSuN++NEFJjRW4y6nwCgn+js > 2prw5jIj56+M4syM4ZOIHtU= > =tisQ > -----END PGP SIGNATURE----- > > > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel >