diff options
| author | graemeg <graemeg@ae50a9b5-8222-0410-bf8d-8a13f76226bf> | 2007-08-26 17:40:05 +0000 |
|---|---|---|
| committer | graemeg <graemeg@ae50a9b5-8222-0410-bf8d-8a13f76226bf> | 2007-08-26 17:40:05 +0000 |
| commit | 4fd4e5cc02054005ce8a9aae976350aefc54a94e (patch) | |
| tree | d18d17f29e4d63c568240fc83a32528dd781abef /src | |
| parent | 8e4a9e6d1e76fe16e965a04a377aff65e82362d0 (diff) | |
| download | fpGUI-4fd4e5cc02054005ce8a9aae976350aefc54a94e.tar.xz | |
* Renamed the fpc.cfg to extrafpc.cfg so it doesn't conflict with
the Lazarus IDE.
* Added extrafpc.cfg files in each of the examples directories.
* Added a examples/readme.txt file explaining how to compile the examples from the
command line.
Diffstat (limited to 'src')
| -rw-r--r-- | src/build.bat | 2 | ||||
| -rwxr-xr-x | src/build.sh | 2 | ||||
| -rw-r--r-- | src/extrafpc.cfg (renamed from src/fpc.cfg) | 0 | ||||
| -rw-r--r-- | src/readme.txt | 33 |
4 files changed, 25 insertions, 12 deletions
diff --git a/src/build.bat b/src/build.bat index 47ac2df8..1fe4669e 100644 --- a/src/build.bat +++ b/src/build.bat @@ -1,2 +1,2 @@ -fpc @C:\Windows\fpc.cfg gui\fpgui_package.pas -dRELEASE -dGDI +fpc @extrafpc.cfg gui\fpgui_package.pas -dRELEASE -dGDI diff --git a/src/build.sh b/src/build.sh index 68b7348a..b0aeae39 100755 --- a/src/build.sh +++ b/src/build.sh @@ -1,2 +1,2 @@ -fpc @~/.fpc.cfg gui/fpgui_package.pas -dRELEASE -dX11 +fpc @extrafpc.cfg gui/fpgui_package.pas -dRELEASE -dX11 diff --git a/src/fpc.cfg b/src/extrafpc.cfg index ca911be1..ca911be1 100644 --- a/src/fpc.cfg +++ b/src/extrafpc.cfg diff --git a/src/readme.txt b/src/readme.txt index 89952f92..6192fc1c 100644 --- a/src/readme.txt +++ b/src/readme.txt @@ -5,21 +5,21 @@ This is still a work in progress until I can find a suitable solution. I'm not 100% satisfied with this, but it's a quick and dirty way to get things to compile. I'll assume you have the 'fpc' executable setup in your PATH so it -can be run from any location on your computer. +can be run from any location on your computer. I'll also assume you global +fpc.cfg file has been setup correctly so the FPC compiler can find the RTL and +FCL units. Under Linux run: build.sh - This assumes that your global fpc.cfg file is located in you HOME directory Under Windows run: build.bat - This assumes that you global fpc.cfg file is located in C:\Windows\ directory. -The fpc.cfg file located in this directory is combined with your global fpc.cfg -file. The locat config file sets up all the required search and include paths -to compile CoreLib and GUI directories. +The extrafpc.cfg file located in this directory is combined with your global +fpc.cfg file. The local extrafpc.cfg file sets up all the required search and +include paths to compile CoreLib and GUI directories. -All compiled units (*.o and *.ppu) are saved in the ../lib directory. This makes -the search paths for you applications a little easier to setup. +All compiled units (*.o and *.ppu) are saved in the ../lib directory. This +makes the search paths for you applications a little easier to setup. Building fpGUI using Lazarus @@ -62,6 +62,21 @@ find all the fpGUI compiled units and source for you. automatically include the paths to the fpGUI compiled units for you. + Compiling any of the examples from the Command Line + =================================================== + +You need to compile fpGUI first as mentioned above! +Every project in the ../examples directory has it's own extrafpc.cfg file. +You only need to specify that config file and the project unit to compile +it. + +fpc @extrafpc.cfg <project unit> + +Example: + fpc @extrafpc.cfg docedit.lpr + + + Regards, - Graeme - @@ -70,5 +85,3 @@ Regards, - - |