From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Alan Martinovic Date: Sun, 5 Oct 2014 13:16:22 +0000 Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D01D52E901@nooslzsmx1.zenitelcss.com> References: <916A03CCEB30DF44AD98D4CFDC7448D00D59BAD8@nooslzsmx1.zenitelcss.com> <201409241353.13365.jbe@pengutronix.de> In-Reply-To: <201409241353.13365.jbe@pengutronix.de> Content-Language: en-US MIME-Version: 1.0 Subject: Re: [ptxdist] Modifing platform rules Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Juergen Borleis , "ptxdist@pengutronix.de" Hi, I'm trying to add a new menu option in the platform Kconfig. Here is what i did so far: Copy the /usr/local/lib/ptxdist-2014.09.0/platforms/Kconfig to oselas.bsp/p= latforms I've tested it and changes on the oselas.bsp/platforms/Kconfig are shown in= the platformconfig. I want to add a new top level menu entry. I add: menu "custom image creation rules " source "platforms/custom_image.in" endmenu to oselas.bsp/platforms/Kconfig and that gives a "can't open file" when running ptxdist platformconfig However, if I put an absolute path, everything works. menu "custom image creation rules " source "absolute_path_to/platforms/custom_image.in" endmenu Relative to what path does the extended Kconfig look for .in files? -----Original Message----- From: Juergen Borleis [mailto:jbe@pengutronix.de] = Sent: Wednesday, September 24, 2014 1:53 PM To: ptxdist@pengutronix.de Cc: Alan Martinovic Subject: Re: [ptxdist] Modifing platform rules Hi Alan, On Wednesday 24 September 2014 10:30:36 Alan Martinovic wrote: > I'm trying to get use the kernel from an external source (git repository). > The chapter 6.1. defines this how to do this, however it doesn't suite = > me because it requires additional manual work for someone setting up = > the build system. > > I know how to write the .make and .in file for the kernel but in the = > userpace configuration (creating kernel.in and kernel.make in /rules) = > but that would completely ignore the kernel platform settings which I = > don't believe is the intended way. > > What is the proper way to extend the platform rules and .in files? Do it in the platform. But the folder names differ. The *.make files should= be still in the rules/ directory inside the platform directory, but the co= rresponding *.in file must be located in the platforms/ directory. So, if your platform is located in configs/platform-myboard/ the kernel rul= es must be located in: configs/platform-myboard/platforms/kernel.in configs/platform-myboard/rules/kernel.make Happy hacking Juergen -- Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 | Industrial Linux Solutions =A0 =A0 =A0| http://www.pengutroni= x.de/ | DISCLAIMER: This e-mail may contain confidential and privileged material for the sole u= se of the intended recipient. Any review, use, distribution or disclosure b= y others is strictly prohibited. If you are not the intended recipient (or = authorized to receive for the recipient), please contact the sender by repl= y e-mail and delete all copies of this message. -- = ptxdist mailing list ptxdist@pengutronix.de