Debian and libwx-c
Les Ferguson <[email protected]>
| Newsgroups | gmane.comp.lib.wxwindows.wxnet |
|---|---|
| Message-ID | <[email protected]> |
Ok, after a bit of advice & much trial-and-error I decided the prebuilt wx.NET
files may not be compatable with my current Debian environment, so I tried to
build them from the sources.
This was also unsuccessful, possibly partly due to my insistence on installing
everything I can from official Debian packages, along with lack of extensive
knowledge on handling these anomalies.
In wx.NET-0.3 I did:
# premake --target gnu
then make
(also tried premake --with-shared --target gnu)
It gives this:
==== Building wx-c ====
document.cxx
document.cxx: In function `wxOutputStream* wxDocument_SaveObject(wxDocument*,
wxOutputStream*)':
document.cxx:123: error: no matching function for call to `wxDocument::
SaveObject(wxOutputStream&)'
/usr/include/wx/docview.h:90: error: candidates are: virtual std::ostream&
wxDocument::SaveObject(std::ostream&)
document.cxx: In function `wxInputStream* wxDocument_LoadObject(wxDocument*,
wxInputStream*)':
document.cxx:129: error: no matching function for call to `wxDocument::
LoadObject(wxInputStream&)'
/usr/include/wx/docview.h:91: error: candidates are: virtual std::istream&
wxDocument::LoadObject(std::istream&)
make[1]: *** [obj/document.o] Error 1
make: *** [wx-c] Error 2
---------------------
Now, in docview.h, I find this:
---------------------
#if wxUSE_STD_IOSTREAM
virtual wxSTD ostream& SaveObject(wxSTD ostream& stream);
virtual wxSTD istream& LoadObject(wxSTD istream& stream);
#else
virtual wxOutputStream& SaveObject(wxOutputStream& stream);
virtual wxInputStream& LoadObject(wxInputStream& stream);
#endif
---------------------
while in the Debian changelog I find this:
---------------------
wxwindows2.4 (2.4.2.4) unstable; urgency=low
* Enabled iostream support despite my opinion of this c++ 'feature'.
Closes: #211050
---------------------
Now I am guessing I must determine where this wxUSE_STD_IOSTREAM flag should
be set, and does this require building all of wxWindows from source &
changing the default options used in the Debian package ?
Note: I had expected the wxWindows stuff to have been installed from
debian-testing, but it appears to have come from debian-unstable. Should I
back it out & try an older version ?
Any suggestions welcome, particularly those related to wx.NET or wxWindows...
--
Les Ferguson
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click