From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [81.228.8.83] (helo=pne-smtpout1-sn2.hy.skanova.net) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1Melze-0003Xr-Lw for openembedded-devel@lists.openembedded.org; Sat, 22 Aug 2009 10:30:34 +0200 Received: from [10.175.196.247] (213.66.88.44) by pne-smtpout1-sn2.hy.skanova.net (7.3.140.3) (authenticated as u82406562) id 4A7285AE00225347 for openembedded-devel@lists.openembedded.org; Sat, 22 Aug 2009 10:13:04 +0200 Message-ID: <4A8FA88E.1050805@atmel.com> Date: Sat, 22 Aug 2009 10:13:02 +0200 From: Ulf Samuelsson Organization: Atmel Nordic AB User-Agent: Thunderbird 2.0.0.22 (X11/20090605) MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4A8D5E37.5010806@atmel.com> In-Reply-To: Subject: Re: Is it possible for a recipe to include/require something from a subdirectory? 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, 22 Aug 2009 08:30:36 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Chris Larson skrev: > On Thu, Aug 20, 2009 at 7:31 AM, Ulf Samuelsson wrote: >> I just finished a nice gnome script which allows me to automatically >> generate SRC_URI_append's >> >> I select the files[1-4] in ///", >> and then run the script >> >> result is: >> >> SRC_URI_append_ = "\ >> file:// \ >> file:// \ >> file:// \ >> file:// \ >> " >> >> Now, in /.bb I want to include the file using >> >> require //SRC_URI_append >> >> This did not work, so I tried symlinking - bad move... >> I'd hate having to move it to the top directory of the recipe. >> >> Any ideas? > > include/require obey BBPATH. As far as I know, the parser should be > temporarily changing bbpath to facilitate includes relative to the > file doing the including. If that isn't working, you could try > require ${FILE_DIRNAME}/foo/bar instead. That worked, This saves me a lot of time. I am thinking of checking in the script that generates the file. Anyone interested? Got as few other gnome scripts which I find useful. 1: Select ; Copy to -0rig for creating a patch 2: Select and ; diff -urN 3: Select .patch; splitdiff the patch into the directory /patchdir. Rename each to .patch If the file "template" is present: For each (one per line) in template If a patch matches the string: create the directory move all matching patches to this directory. 4: Select and The is identified by having "./patchdir" "./patchdir contains a number of directories (patchsets). Attempt to apply all patches in the patch directory to the source tree using --dry-run. Provide OK/FAIL result + a list of all working patches are collected in a file. 5: Select a number of files; Generate SRC_URI_append.inc, optimized for the kernel It will check if a file "arch" exists and for each machine listed in "arch" it will check its subdirectory for a "defconfig", and will generate a SRC_URI_append_.inc, containing the stuff for each arch. 6: Select ; Set the execute bit on the 7: Select .patch; apply .patch to Report results -- Best Regards Ulf Samuelsson