From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: =?iso-8859-1?q?J=FCrgen_Beisert?= Date: Tue, 8 Oct 2013 15:58:54 +0200 References: <24635EE72167A34F98C0A19CAD298DE7149E4775@SBS01.phenom.local> <201310081520.14687.jbe@pengutronix.de> <24635EE72167A34F98C0A19CAD298DE7149E497D@SBS01.phenom.local> In-Reply-To: <24635EE72167A34F98C0A19CAD298DE7149E497D@SBS01.phenom.local> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201310081558.54314.jbe@pengutronix.de> Subject: Re: [ptxdist] Where do configure options for simple autotools packages come from? 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-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Sander Stoks Hi Sander, please keep the mailing list on CC. On Tuesday 08 October 2013 15:30:23 Sander Stoks wrote: > > Where did you read there is "not need for a rule file"? Each package in > > PTXdist needs a rule file. The content of this rule may vary, depending > > on the package's build system. > > On page 34 of the english manual, it is explained under "Adding new > Packages", > > "In this example we expect an autotoolized source package. E.g. to prepare > the build, the archive comes with a configure script. This is the default > case for PTXdist. So, there is no need to modify the rule file and we can > simply run ptxdist prepare foo" I have written there is "no need to modify the rule file", I haven't = written "there is no need for a rule file". ;) > Since I could not find the relevant rules file (looking in the wrong plac= e) > I thought that maybe there was a "generic" rule for any package containing > a ./configure script. There is generic code what has to be done in each stage. If you do not prov= ide = your own stage code in your rule file, the generic code will be used instea= d. = For (perfect) autotoolized packages the generic stage code can be used. > However, I was suspicious about this since there were definitely options > being passed to ./configure. To forward special options to the configure stage you just have to provide = the = _CONF_OPT variable. But no code. The generic code uses th= e = *_CONF_OPT content automagically. > Getting the required dependencies to work is a simple matter of defining > packages for those (in this case, krb5-libs-devel, keyutils-libs-devel, a= nd > libwbclient-devel) and selecting those? Dependencies are handled inside the *.in files via "select". If you enable = a = package and this package needs another package, the enabled package must = select the package it depends on. PTXdist also uses these "select" statemen= ts = to define the build order of the packages. Regards, Juergen -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Beisert =A0 =A0 =A0 =A0 =A0 =A0 | Linux Solutions for Science and Industry =A0 =A0 =A0| http://www.pengutroni= x.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de