| 1 |
Donnie Berkholz wrote: |
| 2 |
> On 21:14 Mon 24 Sep , Ryan Hill wrote: |
| 3 |
>> - is the stuff in global scope kosher? i've seen other eclasses do |
| 4 |
>> similar, but i want to be sure. the reason for the looping is because |
| 5 |
>> i figure calling built_with_use in global would get me hung. |
| 6 |
> |
| 7 |
>> for wxtoolkit in gtk2 base; do |
| 8 |
>> debug-print "global outer loop - wxtoolkit is ${wxtoolkit}" |
| 9 |
>> for wxdebug in release debug; do |
| 10 |
>> debug-print "global inner loop - wxdebug is ${wxdebug}" |
| 11 |
>> wxconf="${wxtoolkit}-${wxchar}-${wxdebug}-${WX_GTK_VER}" |
| 12 |
>> debug-print "testing for config ${wxconf}" |
| 13 |
>> [[ -f /usr/$(get_libdir)/wx/config/${wxconf} ]] || continue |
| 14 |
> |
| 15 |
> Checking for existence of files in global scope? |
| 16 |
|
| 17 |
Yeah. These config files work like pkg-config, in that calling, say, |
| 18 |
`gtk2-unicode-release-2.8 --libs` outputs the linker flags needed to link |
| 19 |
to those libraries. We need a way to know what config scripts are available. |
| 20 |
This is the least expensive way i could think of, a minimum of one and max of |
| 21 |
four stat calls. |
| 22 |
|
| 23 |
I'm also going to drop the debug-prints here as there's too much overhead. |
| 24 |
|
| 25 |
>> debug-print "found config ${wxconf} - setting WX_CONFIG" |
| 26 |
>> WX_CONFIG="/usr/$(get_libdir)/wx/config/${wxconf}" |
| 27 |
>> # TODO: needed for the wx-config wrapper |
| 28 |
>> #WX_ECLASS_CONFIG="${WX_CONFIG}" |
| 29 |
>> break |
| 30 |
>> done |
| 31 |
>> [[ -n ${WX_CONFIG} ]] && break |
| 32 |
>> done |
| 33 |
>> [[ -n ${WX_CONFIG} ]] && export WX_CONFIG #WX_ECLASS_CONFIG |
| 34 |
> |
| 35 |
> OK, so let me try to follow the logic of preferences here: |
| 36 |
> |
| 37 |
> 1. gtk2-release |
| 38 |
> 2. gtk2-debug |
| 39 |
> 3. base-release |
| 40 |
> 4. base-debug |
| 41 |
> |
| 42 |
> Does that mean they can't get a debug setup if the release one is found? |
| 43 |
> Does a debug build only produce debug and not release? |
| 44 |
|
| 45 |
True. For example the 2.6 ebuild will install one of gtk2-ansi-release-2.6 or |
| 46 |
gtk2-ansi-debug-2.6 depending on the debug USE flag. With USE="-X" it installs |
| 47 |
base-ansi-release-2.6 or base-ansi-debug-2.6. gtk2 builds provide both the gtk2 |
| 48 |
and base libraries so are preferred over plain base. |
| 49 |
|
| 50 |
It technically possible to install debug and release builds side-by-side. In |
| 51 |
fact, the previous version of this eclass was designed around it. Some invasive |
| 52 |
hackery was needed to pull it off though, and we decided not to support it. |
| 53 |
|
| 54 |
>> else |
| 55 |
>> : |
| 56 |
>> fi |
| 57 |
> |
| 58 |
> What's up with the 'else' here? |
| 59 |
|
| 60 |
oops, leftover from debugging. i had an echo in there, then replaced it with |
| 61 |
a no-op and forgot to remove it completely. |
| 62 |
|
| 63 |
> |
| 64 |
> Thanks, |
| 65 |
> Donnie |
| 66 |
|
| 67 |
Thanks for taking the time to look at it. |
| 68 |
|
| 69 |
-- |
| 70 |
fonts / wxWindows / gcc-porting / treecleaners |
| 71 |
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) |
| 72 |
|
| 73 |
-- |
| 74 |
gentoo-dev@g.o mailing list |
Archives