Bug 143258

Summary:	"wxrc" program missing from wxGTK-devel
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Andreas Hanke <andreas.hanke>
Component:	GNOME	Assignee:	Stanislav Brabec <sbrabec>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Alpha 4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	proposed patch to current spec file

Description Andreas Hanke 2006-01-14 07:16:40 UTC

The "wxrc" tool is missing from the wxGTK-devel package. This tool is needed at build time by all programs using wxWidgets XML resources (XRC). It is installed by default usually, but missing from the SuSE package because the SuSE package is built from the wxPython source. This is not optimal because the xrc library is indeed included, but quite useless without this tool.

This can be fixed by simply creating the directory "utils/wxrc" in the build tree and copying "wxrc.cpp" and "Makefile.in" from wxWidgets CVS there before running configure. The top-level Makefile takes care of the rest, it tests for that subdirectory, builds the targets if the sources are present and does nothing otherwise.

Summary:

- add the files "wxrc.cpp" and "Makefile.in" from wxWidgets CVS as extra Source2 and Source3:

http://cvs.wxwidgets.org/viewcvs.cgi/wxWidgets/utils/wxrc/

- add this somewhere between %setup and %build:

mkdir -p utils/wxrc

- copy the files "wxrc.cpp" and "Makefile.in" to that directory:

cp %{S:2} %{S:3} utils/wxrc

- build as usual

- add these files to the wxGTK-devel file list:

%{_bindir}/wxrc
%{_bindir}/wxrc-2.6

Please note that both files must be taken from a matching branch. Otherwise there will be build failures because the libraries are versioned and the build system tries to use the wrong ones. Everything was tested with "wxrc.cpp" rev. 1.46 and "Makefile.in" rev. 1.35, both from WX_2_6 branch.

Comment 1 Andreas Hanke 2006-01-14 07:38:57 UTC

Created attachment 63348 [details]
proposed patch to current spec file

These are the needed extra sources:

Source2: http://cvs.wxwidgets.org/viewcvs.cgi/*checkout*/wxWidgets/utils/wxrc/wxrc.cpp?rev=1.46

Source3: http://cvs.wxwidgets.org/viewcvs.cgi/*checkout*/wxWidgets/utils/wxrc/Makefile.in?rev=1.35

Comment 2 Stanislav Brabec 2006-01-16 10:27:12 UTC

For some reason, this program is named pywxrc.

Maybe I will update wxpython bundled version to standard version. I will check the name.

Comment 3 Andreas Hanke 2006-01-16 11:13:49 UTC

(In reply to comment #2)
> For some reason, this program is named pywxrc.

They are not the same. pywxrc is a python script, wxrc is built from the mentioned C++ source. Are they compatible? I don't think so, but even if they were, most ./configure scripts just search for wxrc.

> Maybe I will update wxpython bundled version to standard version.

Is that really a good idea? There's a wxPython release which is newer than the last released standalone wxWidgets, see bug 141806

Standalone wxWidgets 2.6.2 is actually worse than both wxPython 2.6.1.0 and wxPython 2.6.2.1 because it introduced a bug in src/common/intl.cpp which makes some applications crash on startup in any other locale than English. It is triggered by aMule (not part of the distribution, but still...) and maybe others.

This is fixed in wxPython 2.6.2.1 (or CVS rev. 1.166.2.1 of that file, src/common/intl.cpp), so it might be easier (for multiple reasons) to stay with the wxPython bundled version.

Comment 4 Stanislav Brabec 2006-01-16 12:56:42 UTC

At least for hugin, use of pywxrc worked for me.
I see no problem with adding wxrc.
Note that in 10.0 we are building wxGTK from wxpython snapshot.
Now I am just thinking, whether to update and how.
There is a bug 141806, which recommends to update.

Comment 5 Stanislav Brabec 2006-01-20 14:23:58 UTC

Thanks for the information.

Files added and patch applied for 10.1 and supplementary with minor changes to prevent double packaging.