Bug 106503 – compile wxGTK 2.6.1 with unicode only (without ANSI)

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Gioele Barabucci 2005-09-19 04:18:11 UTC]

Can you please split wxGTK in two ebuilds? one with support for unicode and 
another with ANSI. 
 
I, and many others as I see from the other bug reports, have no interest in 
the non-unicode version of wxGTK and have a lot of problems with the big disk 
space that the two compilations of wxGTK require. 

Reproducible: Always
Steps to Reproduce:

[Comment 1 Jakub Moc (RETIRED) 2005-09-19 04:25:47 UTC]

Many packages aren't coded properly and fail with unicode, so this is not really
the best idea indeed.

[Comment 2 Gioele Barabucci 2005-09-19 06:07:46 UTC]

The broken packages will DEPENDs on wxGTK-ansi instead of wxGTK. 
 
Those who have only broken packages will have only wxGTK-ansi installed, 
those who, like me, have only good packages will have only wxGTK (unicode 
only) installed, last who have both kind kind of packages will have to install 
both wxGTK-ansi and wxGTK. 
 
Two thirds of the user base will benefits from shorter compile time (more than 
half) and less installed libraries; the last third will not notice any 
difference 

[Comment 3 John Ratliff 2005-09-23 02:04:12 UTC]

What about local use flags? x11-libs/wxGTK:unicode and x11-libs/wxGTK:ansi

unicode only
USE="-ansi" emerge wxGTK

ansi only
USE="-unicode" emerge wxGTK

both
emerge wxGTK

[Comment 4 Gioele Barabucci 2005-09-26 09:11:18 UTC]

(In reply to comment #3) 
> unicode only 
> USE="-ansi" emerge wxGTK 
> ansi only 
> USE="-unicode" emerge wxGTK 
 
I don't think this is a good solution for two reasons. 
* How can an application that use wxGTK say to portage that it needs a "" 
version of wxGTK? 
* Also I want to avoid the big one-huge-compilation-for-two-big-libraries 
step. Two ebuilds mean half time spent recomping wxGTK if one has built a 
unicode-only wxGTK and now needs also an ANSI wxGTK. 

[Comment 5 Gioele Barabucci 2006-02-27 11:11:10 UTC]

This is still unsolved...
Why can't we split the wxGTK ebuild in two: unicode-ONLY and ansi-ONLY?

[Comment 6 Gioele Barabucci 2006-10-08 06:28:11 UTC]

Created attachment 99110 [details]
Ebuild with ansi and unicode USE variables

When the 'ansi' USE variable is disabled, this ebuild will build only the unicode version.

[Comment 7 Ryan Hill (RETIRED) 2007-04-07 01:27:12 UTC]

I tried implementing this while rewriting our wxGTK ebuilds, and it won't work reliably.  We need the ansi version installed to fall back on always.