From 1fa018ff4a36dd57bdf2d1b916ac07bdbf616975 Mon Sep 17 00:00:00 2001 From: James Richters Date: Sat, 30 Nov 2024 17:41:10 -0500 Subject: [PATCH] Give correct instructions for Windows It needs to be much more clear that X11 is for Linux and GDI is for Windows. I don't know what Mac or other platforms would use here Also the better way to compile with the Text IDE is to load the appropriate fpgui_toolkit.pas file which will compile ALL units, not just what may be used in a particular project, then all the newly created units can be used for various projects, and you won't run into a problem if your original project didn't use one of the units. The instructions for compiling with the IDE have been modified to show usage for Linux and Windows and further explain how to compile fpgui_toolkit.pas to compile all units --- docs/INSTALL.txt | 52 ++++++++++++++++++++++++++++++++++++------------ 1 file changed, 39 insertions(+), 13 deletions(-) diff --git a/docs/INSTALL.txt b/docs/INSTALL.txt index 26eee1682..9d37d1a50 100644 --- a/docs/INSTALL.txt +++ b/docs/INSTALL.txt @@ -80,24 +80,38 @@ so doesn't read the standard fpc.cfg file. * Navigate the menus to: Options|Directories and select the 'Units' tab. * Now enter the following directories replacing the relevant parts with - your actual paths. The example below is valid on my system only. - I was using FPC 2.2.0 under Linux and the X11 corelib backend. - - /opt/fpc_2.2.0/lib/fpc/2.2.0/units/i386-linux/* - /opt/fpc_2.2.0/lib/fpc/2.2.0/units/i386-linux/rtl - /home/graemeg/programming/fpGUI/src/corelib - /home/graemeg/programming/fpGUI/src/corelib/x11 - /home/graemeg/programming/fpGUI/src/gui + your actual full paths for fpGUI. + + For Linux: + full_path_to/fpGUI/src/corelib + full_path_to/fpGUI/src/corelib/x11 \\for linux + full_path_to/fpGUI/src/gui + full_path_to/fpGUI/src/gui/db + full_path_to/fpGUI/src/3rdparty/regex + + For Windows: + full_path_to\fpGUI\src\corelib + full_path_to\fpGUI\src\corelib\gdi \\for windows + full_path_to\fpGUI\src\gui + full_path_to\fpGUI\src\gui\db + full_path_to\fpGUI\src\3rdparty\regex * Now select the 'Include files' tab and enter the following paths. Again change the paths to point to your actual directories and X11 or GDI corelib backend. - /home/graemeg/programming/fpGUI/src/corelib - /home/graemeg/programming/fpGUI/src/corelib/x11 + For Linux: + full_path_to/fpGUI/src + full_path_to/fpGUI/src/corelib + full_path_to/fpGUI/src/corelib/x11 \\for linux + + For Windows: + full_path_to\fpGUI\src + full_path_to\fpGUI\src\corelib + full_path_to\fpGUI\src\corelib\gdi \\for windows * Now changes to 'Miscellaneous' tab, PPU output directory. Type in - the edit box: units + the edit box: full_path_to\units NOTE: This will place all the compiled *.ppu and *.o files into a 'units' @@ -105,10 +119,22 @@ so doesn't read the standard fpc.cfg file. before you try to compile for the first time. FPC doesn't create directories for you! - * Now you are ready to open your projects main program unit (F3) and + * To create all the units for fpGUI, + compile one of the following: + full_path_to/fpGUI/src/corelib/x11/fpgui_toolkit.pas //for linux + full_path_to\fpGUI\src\corelib\gdi\fpgui_toolkit.pas //for windows + + * Now you can restore your freepascal configuration by: + remove all the directories added in the Units Tab + remove the directories added in Include Files Tab + remove units from the Miscellaneous tab + + * Add the directory to the newly created units in the units tab + full_path_to\units + + you are ready to open your projects main program unit (F3) and compiling it by pressing (F9). - Compiling any of the examples from the Command Line ═══════════════════════════════════════════════════