[wxWorkshop-dev] Now Builds on Linux - Ansi & Unicode Versions (Progress Status Part 6)

[<wxw...@li...>]

Hello,

It's been 2 weeks since the last Progress Status on wxWorkshop, but 
progress has been continuing....

It has gotten apparent that there are some differences between the 
Windows compiler & how it handles the source code, and  the g++ compiler 
used on Linux, and the way it handles source code, which is why I have 
created a Linux_v0_80 Branch for the linux code work.  Eventually we 
will be merging this code back into the main branch.  So currently we 
have the following in the wxWorkshop CVS Repository on sourceforge.net:

HEAD or MAIN Branch - wxWorkshop v0.7.5 for Window (only the ansi 
version has been tested), that builds with MS Visual Studio 2003, and 
creates a binary that can even do simple editing on a file, but nothing 
else.

Linux_v0_80 Branch - wxWorkshop v0.8.0 for Linux (ansi & unicode 
versions tested), that builds with g++ v4.0.1, and creates a binary that 
does nothing much than display the initial dialog box and the about 
box.  This Linux version is set up to build with wxWidgets-2.6.1, 
unicode or ansi version, g++ v4.0.1 for the C++ compiler, and the 
wxWorkshop libraries are being linked statically into the wxWidgets 
binary (in the future, the user will get to decide between shared 
dynamic libraries or statically linked libraries).  Also, if the unicode 
build is selected to be built, an external libiodbc library will need to 
be installed to be linked with the binary.

By the above, you can determine that we have reached a minor milestone, 
which is we now have wxWorkshop building with wxWidgets-2.6.1 with 
source code converted for Unicode (but it can also build on the Ansi 
version of wxWidgets) for both Windows (via MS Visual Studio 2003), and 
Linux (g++ v4.0.1).

The immediate next step for me which should not take long is to make the 
Linux package use the autoconf utility so that a package may be created 
to allow a linux user to just put the sources on their machine, and with 
running 3 commands (configure, make, and make install), be able to 
create an executable binary for their system.

Once this is done, we can now start tackling the features (debugging why 
existing features aren't working), and start getting the new features 
implemented.  The fun really starts now.

Tod & George will be helping me getting the source code more common 
between our 2 platforms and we will be working on the features together 
as we continue to resurrect wxWorkshop.  We are expecting that the Web 
Page for wxWorkshop will be revamped soon.

The fun is only beginning.  :)  Stay tuned.

--James (The Spicerun)