[wxWorkshop-dev] Conversion to wxWidgets-2.6.1 - Part 4
Status: Pre-Alpha
Brought to you by:
spicerun
From: <wxw...@li...> - 2005-08-13 16:50:13
|
Hello, Time again for my weekly report on the progress to converting wxWorkshop to wxWidgets-2.6.1 Progress this week slowed as I ran into a lot of problems in linking the object files for wxWorkshop in the final ws directory. I have gotten all of the source files converted well enough to compile on my Linux unicode wxWidgets-2.6.1 platform by adding all of the Unicode macros, and removing Deprecated functions, of which 99% of them have been changed to the recommended replacement functions). In the ws directory alone, I have not yet converted the wxStringList variables to the wxArrayString types as I have been working on the unresolved references problems when trying to link & create the final program. And this has been my delay all week, that I have a lot of unresolved class members in the libraries which took a while to track down. I have found that those class members are in the pmf library. After some time as to analyzing why the classes aren't resolving, I have class members like TPinPainterBase::mPinPainterBase(int tc) exist in the pmf files, but the unresolved reference is TPinPainterBase::TPinPainterBase(int tc). I have a suspicion that the Visual Studio 2003 C++ is taking these symbols and is somehow resolving them, allowing the program object files to be linked. However, g++, the GNU compiler used on linux, does not know that these class members are one in the same, and does not see the problem class members it needs. I will be converting the pmf files to provide the proper classes for the g++ compiler this coming week, and hope to have an executable soon for a baseline to start with. Also, I need input from people who successfully compile wxWorkshop on their Windows environment to see what adjustments can be made to the files that will be acceptable to the MS C++ and g++ compilers. I need some help from the Visual Studio Guys as to why these classes resolve and build in Windows. Stay tuned, --James |