I need to port some command line tool using wxWidgets from win/lin/mac
to iOS (*). The code uses only wxString. I tried to substitute it with
typedef std::string wxString;
but there were too many lines which gave compiler errors, e.g. because
the operator<< was used, or operator= to convert from two-byte-strings.
Since wxWidgets doesn't work (yet) on iOS, I cannot use it (as whole).
So I'd like to extract only wxString.
Anyone already done this before?
(*) and then write a new UI in native objective-c.
--
In a world without walls and fences,
who needs windows and gates?
On 2012-08-14, Marc Stibane wrote:
> I was hoping for some links...
Everything is in wxWidgets sources, i.e. you should just grab 2.9.4
downloads (or current svn/git, of course).
> I just stumbled upon "__WXOSX_IPHONE__" - where does this get defined?
> Or do I have to define that myself in the target options (preprocessor
> symbols)?
Yes, you need to define it yourself to build for iOS.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/
Vadim Zeitlin wrote:
> On 2012-08-08, Marc Stibane wrote:
>> I need to port some command line tool using wxWidgets from
>> win/lin/mac to iOS (*). The code uses only wxString. I tried to
>> substitute it with
>> typedef std::string wxString;
>> but there were too many lines which gave compiler errors, e.g.
>> because the operator<< was used, or operator= to convert from
>> two-byte-strings.
>>
>> Since wxWidgets doesn't work (yet) on iOS, I cannot use it (as
>> whole). So I'd like to extract only wxString.
>> Anyone already done this before?
>
> Yes, several people used parts of wxWidgets (including some GUI ones)
Thanks for the answer.
I was hoping for some links...
Searching for wxString without wxWidgets brought no results.
> under wxiOS.
I just searched for wxiOS - no updates in the last 15 months. Seems
dead... I'll download it anyway, once I have a svn command line tool...
currently installing MacPorts 2.1.2 for 10.8...
Rats. Kerberos5 doesn't build...
> I didn't do it myself but I think it should work without any
> problems with 2.9.4.
I just stumbled upon "__WXOSX_IPHONE__" - where does this get defined?
Or do I have to define that myself in the target options (preprocessor
symbols)?
--
In a world without walls and fences,
who needs windows and gates?
On 2012-08-08, Marc Stibane wrote:
> I need to port some command line tool using wxWidgets from win/lin/mac
> to iOS (*). The code uses only wxString. I tried to substitute it with
> typedef std::string wxString;
> but there were too many lines which gave compiler errors, e.g. because
> the operator<< was used, or operator= to convert from two-byte-strings.
>
> Since wxWidgets doesn't work (yet) on iOS, I cannot use it (as whole).
> So I'd like to extract only wxString.
>
> Anyone already done this before?
Yes, several people used parts of wxWidgets (including some GUI ones)
under wxiOS. I didn't do it myself but I think it should work without any
problems with 2.9.4.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/