[OpenWrt-Devel] OpenWRT build system: how to run configure for a single package?

[Alexey Loukianov]

Greetings,

Today I've been busy creating a package makefile for a piece of software. One
thing I would like to be able to do is to test the configuration part of the
package build process. Accordingly to the OpenWRT docs (and to the wiki pages)
there should be a special build target available for this purposes:

# make V-99 package/some-name/configure

Trouble is that with the latest trunk all I get is:

# make V=99 package/helloworld/configure
make[1]: Entering directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make[1]: *** No rule to make target `package/helloworld/configure'. Stop.
make[1]: Leaving directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make: *** [package/helloworld/configure] Error 2

Am I missing something?

- --
Best regards,
Alexey Loukianov mailto:***@mail.ru
System Engineer, Mob.:[phone]
*nix Specialist

[Alexey Loukianov]

Post by Alexey Loukianov
Am I missing something?

Ping?

- --
Best regards,
Alexey Loukianov mailto:***@mail.ru
System Engineer, Mob.:[phone]
*nix Specialist

[Florian Fainelli]

Hi,

Post by Alexey Loukianov
Greetings,
Today I've been busy creating a package makefile for a piece of software.
One thing I would like to be able to do is to test the configuration part
of the package build process. Accordingly to the OpenWRT docs (and to the
wiki pages) there should be a special build target available for this
# make V-99 package/some-name/configure
# make V=99 package/helloworld/configure
make[1]: Entering directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make[1]: *** No rule to make target `package/helloworld/configure'. Stop.
make[1]: Leaving directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make: *** [package/helloworld/configure] Error 2

...

What about doing the following instead:

make package/helloworld/{clean,prepare,compile,install} V=99 ?

Post by Alexey Loukianov
Am I missing something?

The 'configure' target you are looking for is 'prepare'

[Alexey Loukianov]

Florian, please, stay on the list when answering the messages.
Thanks!

-------- Here is the forwarded original message --------
From: - Tue Oct 5 01:10:33 2010
X-Account-Key: account4
X-UIDL: 1286226411796
X-Mozilla-Status: 0011
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-path: <***@gmail.com>
Received: from [74.125.82.180] (port=42093 helo=mail-wy0-f180.google.com) by
mx103.mail.ru with esmtp id 1P2sFG-0001Bc-00 for ***@mail.ru; Tue, 05 Oct
2010 01:06:50 +0400
Received-SPF: pass (mx103.mail.ru: domain of gmail.com designates 74.125.82.180
as permitted sender) client-ip=74.125.82.180;
envelope-from=***@gmail.com; helo=mail-wy0-f180.google.com;
X-Mru-BL: 0:4:0
X-Mru-PTR: mail-wy0-f180.google.com
X-Mru-NR: 1
X-Mru-OF: Linux ((Google 2))
X-Mru-RC: US
Received: by mail-wy0-f180.google.com with SMTP id 26so5407636wyj.25 for
<***@mail.ru>; Mon, 04 Oct 2010 14:06:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com;
s=gamma; h=domainkey-signature:received:received:sender:from:reply-to:to
:subject:date:user-agent:cc:references:in-reply-to:mime-version
:content-type:content-transfer-encoding:message-id;
bh=HdV3BNzizB4ulIDUnmyleK0HdXxGC957tXMhODmgTP4=;
b=o8ApkhdpUD8BM7EKjvDNHct7MMgVtApXxPZTEBDlbGePlnrzOakX9wI3OobtGex9Z5
mhtSCab4godSCj0o4Ih+s3zEjsSKH7+PLCHxo0xdggtDpGtBbKYaPsuxLbqHamtemdY9
Jnv8M91FwVne8DS40FLE5kk+ATeQZF2g5+vjs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
h=sender:from:reply-to:to:subject:date:user-agent:cc:references
:in-reply-to:mime-version:content-type:content-transfer-encoding
:message-id;
b=K/zPqf2SzKhg7nho3PAXPUp4C/cfgyhBjvMsQNeu03vhX0GlEwIlFfFvni3fZWtKBF
dgU5XXuG3VFDBqiF6C6LkLWHJVoqeo+vdXEPMxIJ9O89rJmoDp2x9DKZXHp1Fvqx8Egv
IsVqmoTN8KSW4VSEVq0r3hV7VAx4ryd5yhNVc=
Received: by 10.216.4.19 with SMTP id 19mr8212303wei.110.1286226410224;
Mon, 04 Oct 2010 14:06:50 -0700 (PDT)
Received: from lenovo.localnet (gob75-6-82-236-225-16.fbx.proxad.net
[82.236.225.16]) by mx.google.com with ESMTPS id
r18sm3328822weo.0.2010.10.04.14.06.48 (version=TLSv1/SSLv3
cipher=RC4-MD5); Mon, 04 Oct 2010 14:06:49 -0700 (PDT)
Sender: Florian Fainelli <***@gmail.com>
From: Florian Fainelli <***@openwrt.org>
Reply-To: Florian Fainelli <***@openwrt.org>
To: openwrt-***@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] OpenWRT build system: how to run configure for a
single package?
Date: Mon, 4 Oct 2010 23:08:21 +0200
User-Agent: KMail/1.13.5 (Linux/2.6.34-1-amd64; KDE/4.4.5; x86_64; ; )
Cc: Alexey Loukianov <***@mail.ru>
References: <***@mail.ru>
In-Reply-To: <***@mail.ru>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart3405743.GHQSyjZacl";
protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <***@openwrt.org>
Authentication-Results: dkim=pass, header.i=@gmail.com
X-Spam: Not detected
X-Mras: Ok

Hi,

Post by Alexey Loukianov
Greetings,
Today I've been busy creating a package makefile for a piece of software.
One thing I would like to be able to do is to test the configuration part
of the package build process. Accordingly to the OpenWRT docs (and to the
wiki pages) there should be a special build target available for this
# make V-99 package/some-name/configure
# make V=99 package/helloworld/configure
make[1]: Entering directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make[1]: *** No rule to make target `package/helloworld/configure'. Stop.
make[1]: Leaving directory `/misc/Raid5/Projects/OpenWRT/Builds/dir320'
make: *** [package/helloworld/configure] Error 2

...

What about doing the following instead:

make package/helloworld/{clean,prepare,compile,install} V=99 ?

Post by Alexey Loukianov
Am I missing something?

The 'configure' target you are looking for is 'prepare'

[Alexey Loukianov]

Post by Florian Fainelli
make package/helloworld/{clean,prepare,compile,install} V=99 ?

Post by Alexey Loukianov
Am I missing something?

The 'configure' target you are looking for is 'prepare'

Unfortunately you're wrong with this: "prepare" is the target that downloads the
sources, unpacks them to the build dir and applies all the patches to be
applied. Configure target I'm interested in is the one that proceedes a step
further and runs the configure script (autoreconfing it in advance if
necessary). When creating a new package I'm insterested in looking into
config.log before entering the compilation stage of the build process - this
would allow me to catch build configuration mistakes earlier and don't waste a
lot of time on debugging later.

- --
Best regards,
Alexey Loukianov mailto:***@mail.ru
System Engineer, Mob.:[phone]
*nix Specialist

[R***@lantiq.com]

Post by Alexey Loukianov
would allow me to catch build configuration mistakes earlier and don't waste a
lot of time on debugging later.

core$hg diff include/subdir.mk
diff --git a/include/subdir.mk b/include/subdir.mk
- --- a/include/subdir.mk
+++ b/include/subdir.mk
@@ -5,7 +5,7 @@
# See /LICENSE for more information.
#

- -SUBTARGETS:=clean download prepare compile install update refresh prereq dist distcheck
+SUBTARGETS:=clean download prepare compile install update refresh prereq dist distcheck configure

subtarget-default = $(filter-out ., \
$(if $($(1)/builddirs-$(2)),$($(1)/builddirs-$(2)), \


This works on my owrt clone.

br
Ralph

[Alexey Loukianov]

Post by R***@lantiq.com
core$hg diff include/subdir.mk
diff --git a/include/subdir.mk b/include/subdir.mk
--- a/include/subdir.mk
+++ b/include/subdir.mk
@@ -5,7 +5,7 @@
# See /LICENSE for more information.
#
-SUBTARGETS:=clean download prepare compile install update refresh prereq dist distcheck
+SUBTARGETS:=clean download prepare compile install update refresh prereq dist distcheck configure
subtarget-default = $(filter-out ., \
$(if $($(1)/builddirs-$(2)),$($(1)/builddirs-$(2)), \
This works on my owrt clone.

...

Thanks, works for me too.
Looks like this is a bug in the OpenWRT build system, it might be reasonable to
fire the bug report against this.

- --
Best regards,
Alexey Loukianov mailto:***@mail.ru
System Engineer, Mob.:[phone]
*nix Specialist

[R***@lantiq.com]

Post by Alexey Loukianov
Looks like this is a bug in the OpenWRT build system, it might be reasonable to
fire the bug report against this.

... it's just an enhancement for source ball developers (like dist & distcheck) .
Let me add it today night to svn .

br
Ralph