Compile error for wxNano-X 2.8.3 and 2.6.4

[Vadim Zeitlin]

On Wed, 2 May 2007 14:52:40 +0900 Hisayuki Fujii <hisabojp at gmail.com> wrote:

HF> wxWidgets-2.8.3 and 2.6.4 for Nano-X was not able to be compiled.

 I'm afraid using wxNanoX port is not really a good idea unless you're
prepared to spend some time on fixing it first. Nano-X itself isn't really
maintained AFAIK (last update on the project web page is from January 2005
and this was just about the name change) so I'm not sure if it makes sense
to invest a lot of time into it.

HF> I have to use wxNano-X for embedded device (ARM920T).

 Just FYI, there is a new port in 2.8 which is meant to be used exactly as
an alternative to wx(Nano)X for embedded devices. It is called wxDFB and
uses DirectFB as the underlying toolkit. It's still in pre-beta stage so
you should still expect to have missing parts/problems with it but at least
it is being developed, unlike wxNanoX.

HF> <compile error message>
HF> /home/pub/src/wxWidgets-2.8.3/nano-x/bk-deps g++ -c -o netdll_ftp.o
HF> -D__WXX11__ -D__WXUNIVERSAL__           -DwxUSE_GUI=0 -DWXUSINGDLL
HF> -DWXMAKINGDLL_NET -fPIC
HF> -DPIC -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1
HF> -I/home/pub/src/wxWidgets-2.8.3/nano-x/lib/wx/include/x11univ-ansi-release-2.8
HF> -I../include -I../include/wx/x11/nanox
HF> -I/home/pub/src/microwindows-0.91/src/include -I/usr/X11R6/include
HF> -pthread -fno-exceptions -Wall -Wundef -Wno-ctor-dtor-privacy -O2
HF> -fno-strict-aliasing ../src/common/ftp.cpp
HF> ../src/common/ftp.cpp: In member function `virtual wxInputStream*
HF>    wxFTP::GetInputStream(const wxString&)':
HF> ../src/common/ftp.cpp:770: `wxURI' undeclared (first use this function)
HF> ../src/common/ftp.cpp:770: (Each undeclared identifier is reported only once
HF>    for each function it appears in.)
HF> ../src/common/ftp.cpp:770: parse error before `::' token
HF> make: *** [netdll_ftp.o] Error 1

 This actually looks rather unrelated to wxNanoX, it rather seems that
wxURI was disabled during compilation but wxFTP wasn't (and the latter
requires the former, of course). To fix this the simplest is, if you don't
need wxFTP, to disable it as well: pass --disable-ftp to configure.

 But, again, I'm far from being sure that the port itself still
compiles/works and I'd recommend giving wxDFB a try and see if it's
suitable for your needs.

 Regards,
VZ

-- 
TT-Solutions: wxWidgets consultancy and technical support
               http://www.tt-solutions.com/