Compiling wxWorkshop
getting it to build under *nix

updated: March 8, 2006
Compiling

Configuration used in compiling these instructions

Prerequisites

Building wxWindows

There are two ways to build wxWindows depending upon whether you want to have shared libraries or static libraries. The steps for building using shared libraries are outlined below.

Make a buildgtk-debug directory:

    cd wxWidgets-2.6.3
    mkdir buildgtk-debug


For wxGTK-ansi build:

    ../configure --with-gtk --with-odbc --enable-debug --enable-shared
    make
    make install

For wxGTK-unicode build:

    ../configure --with-gtk --enable-unicode --enable-debug -enable-shared
    make
    make install
    /* NOTE:  Remember that libiodbc must be installed before building wxWorkshop */

You will also need to compile fl which is in contrib/src/fl:

    cd contrib/src/fl
    make
    make install

Building wxWorkshop

Environment Variables

Two environment variables are vital for building wxWorkshop and there are a few methods for defining them. To set these variables, you could Start the wxWorkshop Build

    
/* For Now: */
    cd wxWorkshop
    make -f Makefile.linux

    /* Future build instructions:  */
    cd wxWorkshop
    ../configure

    make
    make install

Edit ld.so.conf (using whatever editor you like) to include the wxWidgets lib path - $WXWIN/lib - you will have the replace the $WXWIN with whatever is the path to the wxWindows base. Run ldconfig. This operation will take a few seconds.

Code Completion Database

To create these databases, you will need the binaries which you will find in your src/diamond directory. You should copy this to your ws/db directory to make use easier.

You can move dsc to ws/db by running the following in the ws/db directory:

    mv ../../src/diamond/dsc_linux.tar.gz .

or to copy, replace mv with cp.

To untar, use

    tar zxvf dsc_linux.tar.gz

To create the databases, run

    ./regen_both

This should run fine, perhaps with some warnings.

Running wxWorkshop

To run wxWorkshop, go into ws and run ./ws

Further details and contact info

If you find that a step has been missed or notice some errors/omissions, please feel free to post to the wxWorkshop help forum.