Do you have a typical platform dependent issue you're battling with ? Ask it here. Make sure you mention your platform, compiler, and wxWidgets version.
- I live to help wx-kind
- Posts: 153
- Joined: Fri Feb 11, 2005 9:05 am
- Location: Stockholm, Sweden
I had one question. Was this trouble (and its solution) relevent to wxWidgets 2.6.3 or you've encountered it in other versions too?
My profile says I'm using 2.6.3 but that is for my main commercial projects. This project is personal (currently
) and I thought it a good idea to start with the latest version. I never built for wxWince on 2.6.3.
(The reason I use 2.6.3 is that I program GUI enabled plug-ins for Mac. Long story...)
PS. My first test failed in the way I describe in this thread, because the wxWince project was incorrectly/incompletely conveted into a VS2005 project. What was missing was a link parameter indicating I am targeting a modern OS (or however the flag is interpreted). No recompile of the code is needed, just a relink. So the code is the same I guess.
/Michael Ljunggren, developer
Windows: 2.6.3, 2.8.9 (VS2005) ** Mac: 2.6.3 (XCode 3) ** WinCE: 2.8.9 (VS2005), ** GTK: 2.8.9 (Kdevelop)
- Experienced Solver
- Posts: 70
- Joined: Fri Nov 07, 2008 4:25 pm
- Location: Saint-Petersburg, Russia
Oh, in this case I'd advise to pay attention to another preprocessor directives. Apparently those are UNDER_CE and _WIN32_WCE. As I see, this misplaced link parameter is used to define OS version. Those macros also serve this purpose and some code (in WinAPI and wxWidgets) depends on them. You should have them set to 0x0501 to match that linker parameter you described earlier. So if it's not there or not set appropriately, then setting it and recompilation is a must
win xp pro sp3/VS Express 2008/MinGW;
win Vista Ultimate/VS 2005;