j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM{ <div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=12.msg66#msg66">Quote from: madhatter2 on December 14, 2009, 03:01:39 PM</a></div><div class="quote">Can anyone shed some light here?<br/><br/>g++ -c -O0 -Wno-invalid-offsetof -Wformat -g -D<b>__WXMAC__</b> -DNOPCH -DBUILD_MACOSX -I"/usr/include" -I"/usr/local/include/wx-2.8" -I"/usr/local/include" -I"/usr/local/boost_1_41_0" -I"/sw/include/db4" -I"/usr/local/ssl/include" -I"/usr/local/lib/wx/include/mac-ansi-release-2.8" -o headers.h.gch headers.h<br/>...<br/>ui.h:430: error: no matching function for call to 'wxTextCtrl::SetValue(const <b>std::basic_string</b><char, std::char_traits<char>, std::allocator<char> >&)'<br/>/usr/local/include/wx-2.8/wx/textctrl.h:303: note: candidates are: virtual void wxTextCtrlBase::SetValue(<b>const wxString&</b>)<br/></div><br/>It looks like the implicit conversion from std::string to wxString isn't working. Â That's used everywhere, the conversion needs to work.<br/><br/>wxString is complicated by supporting win32's 16-bit wchar and 8-bit ansi dual-compile. Â You can get that problem on Windows if the "unicode" (meaning wchar) build is used, so that wxString is wchar and std::string is char.<br/><br/>It's probably some wxWidgets compile defines or build configuration. Â What "configure" options did you use?<br/><br/>I'm not sure __WXMAC__ is the right define. Â It may be the Mac Classic support that's complicating wxString, and we only want OSX. Â Try __WXOSX__ (or see below)<br/><br/><a href="http://docs.wxwidgets.org/stable/wx_cppconst.html">http://docs.wxwidgets.org/stable/wx_cppconst.html</a><br/>"There are two wxWidgets ports to Mac OS. One of them, wxMac, exists in two versions: Classic and Carbon. The Classic version is the only one to work on Mac OS version 8. The Carbon version may be built either as CFM or Mach-O (binary format, like ELF) and the former may run under OS 9 while the latter only runs under OS X. Finally, there is a new Cocoa port which can only be used under OS X. To summarize:<br/><br/>Â Â Â * If you want to test for all Mac platforms, classic and OS X, you should test both __WXMAC__ and __WXCOCOA__.<br/>Â Â Â * If you want to test for any GUI Mac port under OS X, use __WXOSX__.<br/>Â Â Â * If you want to test for any port under Mac OS X, including, for example, wxGTK and also wxBase, use __DARWIN__"</div> text/html
https://whatsonchain.com/tx/913dc08bc61493c2e983633e7d4ac7b240f7e5d2b85ae8a256972759d1f65e8d