X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/51d55e1c0cb6d783164f5c8550f424ea3b49c051..186005466d585f5553e6acc7d963cd5b62c3ea9f:/docs/gtk/install.txt?ds=sidebyside diff --git a/docs/gtk/install.txt b/docs/gtk/install.txt index 347560e521..2c482a12e7 100644 --- a/docs/gtk/install.txt +++ b/docs/gtk/install.txt @@ -6,22 +6,30 @@ * The most simple case ----------------------- -If you compile wxWindows on Unix for the first time and don't like to read +If you compile wxWindows on Linux for the first time and don't like to read install instructions just do (in the base dir): -./configure -make -su -make install -ldconfig -exit +> ./configure --with-gtk +> make +> su +> make install +> ldconfig +> exit + +Afterwards you can continue with + +> make +> su +> make install +> ldconfig +> exit If you want to remove wxWindows on Unix you can do this: -su -make uninstall -ldconfig -exit +> su +> make uninstall +> ldconfig +> exit * The expert case ----------------- @@ -214,15 +222,19 @@ not been defined. And Make in some circumstances as well... * General options ------------------- -The confiugre options have not yet been thoroughly tested -in wxWindows snapshot 6. +Given below are the commands to change the default behaviour, +i.e. if it says "--disable-threads" it means that threads +are enabled by default. + +Many of the confiugre options have been thoroughly tested +in wxWindows snapshot 6, but not yet all (ODBC not). Normally, you won't have to choose a toolkit, because when you download wxGTK, it will default to --with-gtk etc. But if you use all of our CVS repository you have to choose a toolkit. You must do this by running configure with either of: - --with-gtk Use the GIMP ToolKit (GTK) + --without-gtk Don't use the GIMP ToolKit (GTK) --with-motif Use either Motif or Lesstif Configure will look for both. @@ -244,6 +256,24 @@ The following options handle the kind of library you want to build. --enable-profile Add profiling info to the object files. Currently broken, I think. + --enable-no_rtti Enable compilation without creation of + C++ RTTI information in object files. + This will speed-up compilation and reduce + binary size. + + --enable-no_exceptions Enable compilation without creation of + C++ exception information in object files. + This will speed-up compilation and reduce + binary size. Also fewer crashes during the + actual compilation... + + --enable-no_deps Enable compilation without creation of + dependency information. + + --enable-permissive Enable compilation without creation of + giving erros as soon as you compile with + Solaris ANSI-defying headers... + --enable-mem_tracing Add built-in memory tracing. --enable-dmalloc Use the dmalloc memory debugger. @@ -264,8 +294,8 @@ The following options handle the kind of library you want to build. * Feature Options ------------------- -The confiugre options have not yet been thoroughly tested -in wxWindows snapshot 6. ODBC not at all. +Many of the confiugre options have been thoroughly tested +in wxWindows snapshot 6, but not yet all (ODBC not). When producing an executable that is linked statically with wxGTK you'll be surprised at its immense size. This can sometimes be @@ -277,9 +307,9 @@ are --without-libjpeg Disables JPEG image format code. - --without-odbc Disables ODBC code. +{ --without-odbc Disables ODBC code. Not yet. } - --disable-wxresources Disables the use of *.wxr type + --disable-resources Disables the use of *.wxr type resources. --disable-threads Disables threads. Will also @@ -295,6 +325,16 @@ are --disable-streams Disables the wxStream classes. + --disable-file Disables the wxFile class. + + --disable-textfile Disables the wxTextFile class. + + --disable-intl Disables the internationalisation. + + --disable-validators Disables validators. + + --disable-accel Disables accel. + Apart from disabling certain features you can very often "strip" the program of its debugging information resulting in a significant reduction in size.