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
--
[EMAIL PROTECTED] mailing list
