From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new old eclass - wxwidgets.eclass
Date: Wed, 26 Sep 2007 00:21:02 -0700 [thread overview]
Message-ID: <20070926072102.GF22279@supernova> (raw)
In-Reply-To: <fd9uem$dei$1@sea.gmane.org>
On 21:14 Mon 24 Sep , Ryan Hill wrote:
> - is the stuff in global scope kosher? i've seen other eclasses do
> similar, but i want to be sure. the reason for the looping is because
> i figure calling built_with_use in global would get me hung.
> for wxtoolkit in gtk2 base; do
> debug-print "global outer loop - wxtoolkit is ${wxtoolkit}"
> for wxdebug in release debug; do
> debug-print "global inner loop - wxdebug is ${wxdebug}"
> wxconf="${wxtoolkit}-${wxchar}-${wxdebug}-${WX_GTK_VER}"
> debug-print "testing for config ${wxconf}"
> [[ -f /usr/$(get_libdir)/wx/config/${wxconf} ]] || continue
Checking for existence of files in global scope?
> debug-print "found config ${wxconf} - setting WX_CONFIG"
> WX_CONFIG="/usr/$(get_libdir)/wx/config/${wxconf}"
> # TODO: needed for the wx-config wrapper
> #WX_ECLASS_CONFIG="${WX_CONFIG}"
> break
> done
> [[ -n ${WX_CONFIG} ]] && break
> done
> [[ -n ${WX_CONFIG} ]] && export WX_CONFIG #WX_ECLASS_CONFIG
OK, so let me try to follow the logic of preferences here:
1. gtk2-release
2. gtk2-debug
3. base-release
4. base-debug
Does that mean they can't get a debug setup if the release one is found?
Does a debug build only produce debug and not release?
> else
> :
> fi
What's up with the 'else' here?
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-26 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 3:14 [gentoo-dev] new old eclass - wxwidgets.eclass Ryan Hill
2007-09-26 7:21 ` Donnie Berkholz [this message]
2007-09-27 0:56 ` [gentoo-dev] " Ryan Hill
2007-10-07 4:32 ` [gentoo-dev] " Mart Raudsepp
2007-10-07 6:10 ` Ryan Hill
2007-10-07 22:10 ` Carsten Lohrke
2007-10-14 2:46 ` [gentoo-dev] " Ryan Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070926072102.GF22279@supernova \
--to=dberkholz@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox