diff options
| author | Albrecht Schlosser <albrechts.fltk@online.de> | 2016-08-01 12:50:15 +0000 |
|---|---|---|
| committer | Albrecht Schlosser <albrechts.fltk@online.de> | 2016-08-01 12:50:15 +0000 |
| commit | fe0c247dbbd67e0d138d39ff4b0e94deb7e8fbc3 (patch) | |
| tree | 1e9ce423ac2c89e658be7f7551d44252b631072d /README.Unix.txt | |
| parent | 6b0e38942f12b65c7e04f0745516d3007c0ce147 (diff) | |
Documentation fixes.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3-porting@11862 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'README.Unix.txt')
| -rw-r--r-- | README.Unix.txt | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/README.Unix.txt b/README.Unix.txt index 7cd3bb437..0cb15f61d 100644 --- a/README.Unix.txt +++ b/README.Unix.txt @@ -38,7 +38,7 @@ README.Unix.txt - 2010-11-14 - Building FLTK on Unix 1 INTRODUCTION ================= -FLTK currently supports the following development environments on vmost Unix +FLTK currently supports the following development environments on most Unix platforms: - gcc command line tools @@ -305,13 +305,13 @@ Now configure your FLTK installation: ./configure ADVANCED: type "./configure --help" to get a complete list of optional -configurations parameters. These should be pretty self-explanatory. Some +configuration parameters. These should be pretty self-explanatory. Some more details can be found in README. :END_ADVANCED The configuration script will check your machine for the required resources -which you should have installed as described in the Prerequisites chapter. Review -the Configuration Summary, maybe take some notes. +which you should have installed as described in the Prerequisites chapter. +Review the Configuration Summary, maybe take some notes. 3.3 Building FLTK @@ -325,8 +325,8 @@ The entire FLTK toolkit including many test programs will be built for you. No warnings should appear. If some do, please let the FLTK developer team know via the mailing list or the bug reporting template at www.fltk.org . -Actually, as of Oct 28 2010, quite a bunch of warnings will show, mostly about -suggested parenthesis. Please ignore them until we can fix them. +Actually, as of Apr 13 2016, one or two warnings will show, mostly about +deprecated declarations. Please ignore them. 3.4 Testing FLTK @@ -359,11 +359,11 @@ installation path to a location within the user account by adding the 3.6 Creating new Projects ---------------------------- -FLTK provides a neat script named "fltk-config" that can provide all the flags +FLTK provides a neat script named "fltk-config" that can provide all the flags needed to build FLTK applications using the same flags that were used to build the library itself. Running "fltk-config" without arguments will print a list -options. The easiest call to compile an FLTK application from a single source -file is: +of options. The easiest call to compile an FLTK application from a single +source file is: fltk-config --compile myProgram.cxx @@ -390,20 +390,20 @@ version 10.05: Start Code::Blocks. Select File > New > Project. In the "New from template" dialog box, click on "FLTK project" and follow the instructions. -The default project support basic fltk. If you would like to add support for +The default project supports basic fltk. If you would like to add support for images, OpenGL, GLUT, or Forms, add the corresponding flags --use-images, --use-gl, --use-glut, and --use-forms respectively. -The flags are located in the "Project Build Options" dialog. To change the +The flags are located in the "Project Build Options" dialog. To change the compiler flags, select your project in the tree view, then select the -"Compiler Settings" tab, then "Other Options" and add the flags to -`fltk-config --cxxflags` in front of the second "`". +"Compiler Settings" tab, then "Other Options" and add the flags to +`fltk-config --cxxflags` in front of the second "`". The linker flags are located in the "Linker Settings" tab under "Other Linker Options". Add the flags to `fltk-config --ldstaticflags` in front of the second "`". -CodeBlocks can be set up to use fluid to manage modules.. +CodeBlocks can be set up to use fluid to manage modules. The following info is from mingodad@gmail.com posted on fltk.general 06/17/2013: """ |
