Post by Szuts AttilaPlease forgive my sentimentalism! :-)
I'm very happy that I was able to successfully build my Linux wxApp on
MSW with Visual Studio 2010 Express against winSSL and cURL.
Only minor parts of the code had to be modified, mainly standard C++
function calls. Wx source codes worked out-of-the-box.
Then I have to build the whole thing on OSX. :-)
--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
or visit http://groups.google.com/group/wx-users
One tip for you is to look at some of the wx Non-GUI & convenience
wrappers - these abstract some of the C++ operations that vary in API
between platforms to give a more portable interface and easier code
porting.
Some examples include:
* Byte Order - The endian-ness issues (that is the difference between
big-endian and little-endian architectures) are important for the
portable programs working with the external binary data (for
example, data files or data coming from network) which is usually in
some fixed, platform-independent format.
* Debugging macros - Useful macros and functions for error checking
and defensive programming.
* Dialogs - A number of convenience functions for getting input from
the user or displaying messages.
* *Environment
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__env.html>*
-Functions allow access to get or change the values of environment
variables in a portable way.
* *Files and Directories
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__file.html>***-
Functions provide a platform-independent API for common file and
directory functionality.
* Graphics Device Interface (GDI) - Functions and macros related to
GDI (Graphics Device Interface) access.
* Locale-dependent functions - Anumber of functions/macros which
accept as last parameter a specific wxXLocale instance.
* Logging
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__log.html> -
Functions provide a variety of logging functions.
* Math
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__math.html> -
Math operations and floating point numbers.
* *Miscellaneous
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__misc.html>*
- Miscellaneous functions and macros /(Some very useful ones here)/.
* Network, User and OS
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__networkuseros.html>
- Functions in this section are used to retrieve information about
the current computer and/or user characteristics.
* Process Control
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__procctrl.html>
- Used to launch or terminate the other processes.
* Runtime Type Information (RTTI)
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__rtti.html> -
wxWidgets uses its own RTTI ("run-time type identification") system
which predates the current standard C++ RTTI and so is kept for
backwards compatibility reasons but also because it allows some
things which the standard RTTI doesn't directly support (such as
creating a class from its name).
* *Strings
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__string.html>* -
Global string functions and macros.
* Threads
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__thread.html>
- The functions and macros here mainly exist to make it possible to
write code which may be compiled in multi thread build
(wxUSE_THREADS = 1) as well as in single thread configuration
(wxUSE_THREADS = 0).
* Time
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__time.html> -
The functions in this section deal with getting the current time and
sleeping for the specified time interval.
* Versioning
<http://docs.wxwidgets.org/3.0/group__group__funcmacro__version.html> -
Information about the wxWidgets Versions.
Taking the time to take a look at these and using them will sometimes
make porting your code from one platform to another simply a matter of
rebuilding.
Have Fun!
Gadget/Steve
--
Please read http://www.wxwidgets.org/support/mlhowto.htm before posting.
To unsubscribe, send email to wx-users+***@googlegroups.com
or visit http://groups.google.com/group/wx-users