From e562ec02a6914259a0e07676d4b7f75d90ee4976 Mon Sep 17 00:00:00 2001 From: Albrecht Schlosser Date: Wed, 5 Jul 2017 17:15:16 +0000 Subject: Update several README files, remove obsolete information. To be continued ... git-svn-id: file:///fltk/svn/fltk/branches/branch-1.4@12292 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- README | 6 +- README.CMake.txt | 54 ++++++------ README.Cairo.txt | 74 ++++++++--------- README.MSWindows.txt | 219 +++++++++++++++++++++++++------------------------ README.abi-version.txt | 7 +- 5 files changed, 190 insertions(+), 170 deletions(-) diff --git a/README b/README index f27bb4d37..d1dd4e01a 100644 --- a/README +++ b/README @@ -86,7 +86,7 @@ BUILDING AND INSTALLING FLTK UNDER UNIX AND Mac OS X SVN USERS - + If you've just checked out a fresh copy of FLTK from SVN, you'll need to generate an initial version of 'configure' by running 'make makeinclude'. (We don't include a copy @@ -94,7 +94,7 @@ SVN USERS MAKE TARGETS - + make -- builds the library + test programs (does not install) make install -- builds and installs make clean -- clean for a rebuild @@ -124,7 +124,7 @@ BUILDING HTML DOCUMENTATION If you want to build the PDF documentation: ( cd documentation && make pdf ) - + FLTK uses doxygen for documentation, so you'll at least need doxygen installed for creating html docs, and LaTeX for creating PDF docs. diff --git a/README.CMake.txt b/README.CMake.txt index e94a0a8a8..046398f08 100644 --- a/README.CMake.txt +++ b/README.CMake.txt @@ -95,10 +95,11 @@ CMAKE_INSTALL_PREFIX The following are the FLTK specific options. Platform specific options are ignored on other platforms. -OPTION_OPTIM - Extra optimization flags. +OPTION_OPTIM - default EMPTY + Extra optimization flags for the C and C++ compilers, for instance + "-Wall -Wno-deprecated-declarations". -OPTION_ARCHFLAGS +OPTION_ARCHFLAGS - default EMPTY Extra architecture flags. OPTION_APPLE_X11 - default OFF @@ -116,25 +117,25 @@ OPTION_BUILD_EXAMPLES - default ON Builds the many fine example programs. OPTION_CAIRO - default OFF - Enables libcairo support + Enables libcairo support - see README.CMake.txt. OPTION_CAIROEXT - default OFF - Enables extended libcairo support + Enables extended libcairo support - see README.CMake.txt. OPTION_USE_GL - default ON - Enables OpenGL support + Enables OpenGL support. OPTION_USE_THREADS - default ON - Enables multithreaded support + Enables multithreaded support. OPTION_LARGE_FILE - default ON - Enables large file (>2G) support + Enables large file (>2G) support. OPTION_USE_SYSTEM_LIBJPEG - default ON OPTION_USE_SYSTEM_ZLIB - default ON OPTION_USE_SYSTEM_LIBPNG - default ON - FLTK has built in jpeg, zlib, and png libraries. These let you use - system libraries instead, unless CMake can't find them. If you set + FLTK has built in jpeg, zlib, and png libraries. These options let you + use system libraries instead, unless CMake can't find them. If you set any of these options to OFF, then the built in library will be used. OPTION_USE_XINERAMA - default ON @@ -145,9 +146,8 @@ OPTION_USE_XRENDER - default ON These are X11 extended libraries. OPTION_USE_PANGO - default OFF - Enables use of the Pango library for drawing text. Pango supports - all unicode-defined scripts with limited support of right-to-left - scripts. + Enables use of the Pango library for drawing text. Pango supports all + unicode-defined scripts with limited support of right-to-left scripts. This option makes sense only under X11, and also requires Xft. OPTION_ABI_VERSION - default EMPTY @@ -160,7 +160,7 @@ OPTION_ABI_VERSION - default EMPTY ABI version to select. OPTION_PRINT_SUPPORT - default ON - When turned off, the Fl_Printer class does nothing and the + When turned off, the Fl_Printer class does nothing and the Fl_PostScript_File_Device class cannot be used, but the FLTK library is somewhat smaller. This option makes sense only on the Unix/Linux platform or when OPTION_APPLE_X11 is ON. @@ -168,7 +168,7 @@ OPTION_PRINT_SUPPORT - default ON 2.3 Building under Linux with Unix Makefiles ----------------------------------------------- -After untaring the FLTK source, go to the root of the FLTK tree and type +After unpacking the FLTK source, go to the root of the FLTK tree and type the following. mkdir build @@ -186,14 +186,14 @@ Some flags can be changed during the 'make' command, such as: ..which builds in verbose mode, so you can see all the compile/link commands. Hint: if you intend to build several different versions of FLTK, e.g. a Debug -and a Release version, or multiple libraries with different ABI versions, -then use subdirectories in the build directory, like this: +and a Release version, or multiple libraries with different ABI versions or +options, then use subdirectories in the build directory, like this: mkdir build cd build mkdir Debug cd Debug - cmake ../.. + cmake -D 'CMAKE_BUILD_TYPE=Debug' ../.. make sudo make install (optional) @@ -201,8 +201,9 @@ then use subdirectories in the build directory, like this: 2.4 Building under Windows with Visual Studio ------------------------------------------------ -Building with CMake under Visual Studio requires the CMake generator -with the -G command line switch. +Building with CMake under Visual Studio requires the CMake generator with +the -G command line switch, or the generator can be selected interactively +in the GUI (cmake-gui). 2.4.1 Visual Studio 7 / .NET ------------------------------ @@ -239,6 +240,7 @@ with the -G command line switch. ..and in the popup menu, choose "Build Solution" 5) That's it, that should build FLTK. + The test programs (*.exe) can be found in e.g. Release: C:\fltk-1.4.x\build\bin\examples\release\*.exe @@ -246,8 +248,9 @@ with the -G command line switch. ..and the FLTK include files (*.H & *.h) your own apps can compile with can be found in: - + Release & Debug: C:\fltk-1.4.x\build\FL + *and* [1] in: C:\fltk-1.4.x\FL ..and the FLTK library files (*.lib) which your own apps can link with can be found in: @@ -255,6 +258,11 @@ with the -G command line switch. Release: C:\fltk-1.4.x\build\lib\release\*.lib Debug: C:\fltk-1.4.x\build\lib\debug\*.lib + [1] If you want to build your own FLTK application directly using + the build directories (i.e. without "installation") you need + to include both the build tree (first) and then the FLTK source + tree in the compiler's header search list. + 2.5 Building under Windows with MinGW using Makefiles -------------------------------------------------------- @@ -274,7 +282,7 @@ use your MinGW PATH to find the compilers and build tools. Example: mkdir build cd build - cmake -G "Unix Makefiles" .. + cmake -G "Unix Makefiles" -D 'CMAKE_BUILD_TYPE=Debug' .. Note the path to FLTK ".." in the last command line. Depending on where you installed CMake you may need to adjust the path's in the alias commands. @@ -337,7 +345,7 @@ of the cmake related files are updated, Xcode wil rerun cmake for you. Once you have a crosscompiler going, to use CMake to build FLTK you need two more things. You need a toolchain file which tells CMake where your build tools are. The CMake website is a good source of information on -this file. Here's mine for MinGW under Linux. +this file. Here's one for MinGW under Linux. ---- # the name of the target operating system diff --git a/README.Cairo.txt b/README.Cairo.txt index 84c6ed432..c25654cb9 100644 --- a/README.Cairo.txt +++ b/README.Cairo.txt @@ -10,7 +10,7 @@ README.Cairo.txt - 2011-12-10 - Cairo rendering support for FLTK 2 CAIRO SUPPORT FOR FLTK 1.3 2.1 Configuration 2.2 Currently supported features - 2.3 Future considerations + 2.3 Future considerations 3 PLATFORM SPECIFIC NOTES 3.1 Linux 3.2 Windows @@ -22,16 +22,16 @@ README.Cairo.txt - 2011-12-10 - Cairo rendering support for FLTK INTRODUCTION ============== -Cairo is a software library used to provide a vector graphics-based, -device-independent API for software developers. It is designed to provide -primitives for 2-dimensional drawing across a number of different +Cairo is a software library used to provide a vector graphics-based, +device-independent API for software developers. It is designed to provide +primitives for 2-dimensional drawing across a number of different backends. Cairo is designed to use hardware acceleration when available. CAIRO SUPPORT FOR FLTK 1.3 ============================ -It is now possible to integrate cairo rendering in your fltk application +It is now possible to integrate cairo rendering in your FLTK application more easily and transparently. In 1.3, we provide minimum support for Cairo, in particular, no "total" cairo rendering layer support is achieved, @@ -42,38 +42,37 @@ as in fltk2. --------------- All the changes are *inactive* as long as the new configuration -option --enable-cairo is not added to the configure command. -For non configure based platforms/ide, the FLTK_HAVE_CAIRO preprocess -variable has to be defined. -All configure based build files have now this feature integrated, -also vc2005 build files have 2 new build modes "Release Cairo" and -"Debug Cairo". -Other IDE's will be updated progressively. +option --enable-cairo is not added to the configure command or the CMake +variable OPTION_CAIRO:BOOL=ON is set. Currently supported features ------------------------------ -- Adding a new Fl_Cairo_Window class permitting transparent and easy -integration of a Cairo draw callback without the need to achieve subclassing. +(1) Adding a new Fl_Cairo_Window class permitting transparent and easy + integration of a Cairo draw callback without the need subclass Fl_Window. -- Adding a Fl::cairo_make_current(Fl_Window*) function only providing -transparently a cairo context to your custom Fl_Window derived class. -This function is intended to be used in your overloaded draw() method. +(2) Adding a Fl::cairo_make_current(Fl_Window*) function only providing + transparently a cairo context to your custom Fl_Window derived class. + This function is intended to be used in your overloaded draw() method. -- Adding an optional cairo autolink context mode support (disabled by default) - which permits complete & automatic synchronization of OS dependent graphical - context and cairo contexts, thus furthering a valid cairo context anytime, - in any current window. - This feature should be only necessary in the following cases: - - Intensive and almost systematic use of cairo contexts in an fltk application - - Creation of a new cairo based scheme for fltk ... - - Other uses of cairo necessitating the fltk internal instrumentation - to automatically making possible the use of a cairo context - in any fltk window. +(3) Adding an optional cairo autolink context mode support which permits + complete and automatic synchronization of OS dependent graphical context + and cairo contexts, thus furthering a valid cairo context anytime, + in any current window. -- A new cairo demo that is available in the test subdirectory and has been - used as a testcase during the multiplatform tests. + This feature should be only necessary in the following cases: + - Intensive and almost systematic use of cairo in an FLTK application + - Creation of a new cairo based scheme for FLTK + - Other uses of cairo necessitating the FLTK internal instrumentation + to automatically making possible the use of a cairo context + in any FLTK window. + + This feature must be enabled with 'configure --enable-cairoext' or the + CMake variable OPTION_CAIROEXT:BOOL=ON (Default: OFF). + +(4) A new cairo demo that is available in the test subdirectory and has + been used as a testcase during the multiplatform tests. For more details, please have a look to the doxygen documentation, in the Modules section. @@ -86,7 +85,7 @@ From Bill: First there is the FLTK_HAVE_CAIRO configuration option. This indicates that any cairo calls are available. In this case you get something like this: -// static variable holding the last cairo context fltk set: +// static variable holding the last cairo context FLTK set: cairo_t* Fl::cr; // Make cr draw in this window. This hides the ugly platform-dependent @@ -95,14 +94,14 @@ void Fl::cairo_make_current(Fl_Window*) *** POST 1.3 potential cairo use: // Set cr to something you made yourself. This lets you reuse functions -// that use cr, and also tells fltk that cr is not one of its own and +// that use cr, and also tells FLTK that cr is not one of its own and // thus cannot be destroyed or reused for a different window: void Fl::cairo_make_current(cairo_t*) Second there is the FLTK_USE_CAIRO configuration option. This means that all drawing is done using Cairo. In this case when a widget draw() method is called, it is exactly as though cairo_make_current(window) has been done. -*** +*** Note that it should be possible to compile so FLTK_HAVE_CAIRO works even if FLTK_USE_CAIRO does not, and so that turning on FLTK_USE_CAIRO does not @@ -112,7 +111,7 @@ break any programs written for FLTK_HAVE_CAIRO. PLATFORM SPECIFIC NOTES ========================= -The folowing are notes about building FLTK with Cairo support +The following are notes about building FLTK with Cairo support on the various supported operating systems. 3.1 Linux @@ -121,10 +120,10 @@ on the various supported operating systems. From Greg (erco@seriss.com): To get FLTK 1.3.x (r9204) to build on Centos 5.5, I found that I only needed to install the "cairo-devel" package, ie: - + sudo yum install cairo-devel - ..and then rebuild fltk: + ..and then rebuild FLTK: make distclean ./configure --enable-cairo @@ -138,14 +137,14 @@ on the various supported operating systems. collect2: ld returned 1 exit status make[1]: *** [cairo_test] Error 1 - ..remove "-lpixman-1" from fltk's makeinclude file, i.e. change this line: + ..remove "-lpixman-1" from FLTK's makeinclude file, i.e. change this line: -CAIROLIBS = -lcairo -lpixman-1 +CAIROLIBS = -lcairo ..then another 'make' should finish the build without errors. You should be able to then run the test/cairo_test program. - + According to the cairo site, "For Debian and Debian derivatives including Ubuntu" you need to install libcairo2-dev, i.e. @@ -173,3 +172,4 @@ on the various supported operating systems. Dec 20 2010 - matt: restructured document Dec 09 2011 - greg: Updates for Centos 5.5 builds Dec 10 2011 - Albrecht: Updates for Ubuntu and Debian, fixed typos. +Jul 05 2017 - Albrecht: Added CMake config info, fixed typos. diff --git a/README.MSWindows.txt b/README.MSWindows.txt index e3b3d32ef..9e67c09bd 100644 --- a/README.MSWindows.txt +++ b/README.MSWindows.txt @@ -1,5 +1,5 @@ -README.MSWindows.txt - 2016-10-16 - Building FLTK under Microsoft Windows -------------------------------------------------------------------------- + README.MSWindows.txt - Building FLTK under Microsoft Windows +-------------------------------------------------------------- @@ -50,14 +50,21 @@ Windows 8/8.1, and Windows 10. FLTK currently supports the following development environments on the Windows platform: - - Free Microsoft Visual C++ 2008 Express and Visual C++ 2010 Express - using the supplied workspace and project files. Older and the - commercial versions can be used as well, if they can open the project - files. Visual C++ 2015 Express/Community can be used with the - Visual C++ 2010 project files. Be sure to get your service packs! + - Free Microsoft "Visual C++ 2008 Express" or later or "Visual Studio + Community 2013" or later. The Visual Studio project files must be + generated using CMake. Visual Studio 2017 includes CMake support: - The project files can be found in the ide/ directory. - Please read ide/README.IDE for more info about this. + "Visual Studio 2017 introduces built-in support for handling CMake + projects. This makes it a lot simpler to develop C++ projects built + with CMake without the need to generate VS projects and solutions + from the command line. This post gives you an overview of the CMake + support, how to easily get started and stay productive in Visual Studio." + + Citation from: + https://blogs.msdn.microsoft.com/vcblog/2016/10/05/cmake-support-in-visual-studio/ + + As of this writing (07/2017) the FLTK team did not yet test and + verify the functionality of Microsoft's included CMake features. - GNU toolsets (Cygwin or MinGW) hosted on Windows. @@ -84,28 +91,21 @@ the "BASH" Bourne-compatible shell and all of the standard Unix file utilities (ls, cat, grep, etc.). Cygwin is developed by Cygnus (now part of RedHat, Inc). -Although provided for free download under the GPL, -distributing programs that require the Cygwin DLL under a -license other than the GPL requires a commercial license for -the Cygwin DLL. Native Windows programs that do not require -the Cygwin DLL (compiled and linked with the "-mno-cygwin" -option) may be released under any license freely. - -Note: Since December 2009, there is a new gcc 4.x compiler -that doesn't support the -mno-cygwin option anymore. You -must use the older gcc-3 compiler instead. - -An alternative is to install the new (since about Oct. 2010) -mingw cross tools that support newer gcc compilers for building -native Windows applications (like -mno-cygwin above). +Although provided for free download under the GPL, distributing +programs that require the Cygwin DLL under a license other than +the GPL requires a commercial license for the Cygwin DLL. + +Native Windows programs that do not require the Cygwin DLL +(cross-compiled and linked with the MinGW gcc/g++ cross compilers +supplied with Cygwin) may be released under any license freely. + Currently you would have to install mingw64-i686-gcc-g++ for 32-bit Windows applications (despite its name!), and/or mingw64-x86_64-gcc-g++ for 64-bit applications. You may also need to install the corresponding '-headers' packages as well. -Currently these tools support gcc 4.5.x or newer, but the -setup for FLTK is somewhat more complicated and not yet -completely supported automatically (you may need to edit -some lines in the generated makeinclude file). +Currently these tools support gcc 4.5 or newer. The setup for +FLTK is somewhat more complicated because you must configure +this as a cross compiler, but it works well. The MinGW distribution (Minimalist GNU for Windows) provides a similar toolset but geared solely towards native Windows @@ -128,17 +128,18 @@ check out their license conditions carefully before use. There are currently three main configurations supported by FLTK with the GNU tools: - 1. Cygwin: Built using the Cygwin toolset and using the - Unix-like POSIX compatibility layer provided by the - Cygwin DLL. + 1. Cygwin: Built using the Cygwin toolset and using the Unix-like + POSIX compatibility layer provided by the Cygwin DLL. + License: GPL or non-free commercial license (ask Redhat). - 2. Cygwin using the "-mno-cygwin" option: Built using - the Cygwin toolset but not using the Cygwin DLL. + 2. Cygwin using the MinGW cross compiler suite: Built using + the Cygwin tools but not using the Cygwin DLL. + License: freely distributable on all Windows systems. - 3. MinGW: Built using the MinGW utilities, compiler and - tools. This is, in many aspects, analogous to the - Cygwin "-mno-cygwin" option. This is the recommended + 3. MinGW: Built using the MinGW utilities, compiler and tools. This + is, in many aspects, analogous to (2.). This is the recommended one if you want to build native Windows programs only. + License: freely distributable on all Windows systems. Recommended Command Line Build Environment @@ -149,23 +150,18 @@ Our recommendation is to: 1. Get the current Cygwin toolset. This can either produce executables that do or do not - rely on the Cygwin DLL (check licensing) at your - choice. - - 2. Get the latest MinGW toolset. It is recommended that - you also get the MSYS shell and the msysDTK developer - toolset. + rely on the Cygwin DLL (check licensing) at your choice. - This will only produce normal Windows native - executables without any Unix or POSIX compatibility - layer. + 2. Get the latest MinGW toolset. It is recommended that you + also get the MSYS shell and the msysDTK developer toolset. + This will only produce normal Windows native executables + without any Unix or POSIX compatibility layer. - See the links section below for more information. + See the links section below for more information. -Either option can generate windows-native executables and -option 1 can provide a Unix-like POSIX portability layer that -is reliant on a GPLed library. +Either option can generate Windows native executables and option 1 can +provide a Unix-like POSIX portability layer that is reliant on a GPLed library. See the later sections for detailed information about using one of these configurations. @@ -308,25 +304,40 @@ I recommend that you add it to the command search path. - HOW TO BUILD FLTK USING VISUAL STUDIO 2008 -============================================ + HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO +================================================ Prerequisites --------------- -In order to build FLTK from within VisualStudio 2008, you need to install the -VisualC developer environment from the Microsoft web site. The Express edition -is free of charge and sufficient to develop FLTK applications: +In order to build FLTK from within Visual Studio, you need to install the +Visual C++ developer environment from the Microsoft web site. The "Express" +or "Community" edition is free of charge and sufficient to develop FLTK +applications: - http://www.microsoft.com/express/Downloads/ + https://www.visualstudio.com/vs/visual-studio-express/ -You must make sure that at least VisualStudio 2008 Service Pack 1 is installed -or building FLTK on a multicore CPU will be very painful! +If you intend to use an older (maybe commercial) version you need at least +a version that is supported by the version of CMake you are using to generate +the project files. You should make sure that all available service packs are +installed or building FLTK may fail. +As of this writing (07/2017) the FLTK team recommends at least Visual +Studio 2008 with current service packs. Visual Studio 2008, 2010, 2013, +2015, and 2017 are known to work with FLTK 1.4.0 (svn, 07/2017). - Downloading and Unpacking ---------------------------- +You also need to install CMake (cmake-gui) from: + + https://cmake.org/download/ + +Visual Studio 2017 has internal CMake support (so you may not need to +install CMake separately), but this has not yet been tested thoroughly +by the FLTK team. + + + Downloading and Unpacking FLTK +-------------------------------- Download FLTK from here: @@ -344,9 +355,16 @@ my projects. Configuring FLTK ------------------ -Launch VisualStudio. Open the project file in +Note: Configuration with Visual Studio 2017's internal CMake support is +not yet included here. You may try yourself... - ...\fltk-1.3.xxxx\ide\VisualC2008\fltk.sln +Please refer to README.CMake.txt for how to configure FLTK with CMake. + +Once you have followed the instructions you should have created a new +build directory with the Visual Studio Solution (project files) for FLTK. + +Launch Visual Studio and open the project file (FLTK.sln) or double-click +on FLTK.sln in the Windows Explorer. Choose "Debug" or "Release" mode from the "Solution Configurations" menu. @@ -358,13 +376,6 @@ Use the context menu of the "demo" project to "Set as StartUp Project". Then select "Build Solution" from the "Build" menu or press F7 to build all libraries. -VisualC 2008 has a bug that messes up building a Solution on multicore CPUs. -Make sure that Visual Studio 2008 Service Pack 1 is installed or, as a -workaround, set the "maximum number of parallel project builds" to 1 (Tools > -Options > Projects and Solutions > Build and Run > maximum number of parallel -project builds). Also, repeating the build command two or three times may -clear unresolved reference errors. - Testing FLTK -------------- @@ -376,6 +387,10 @@ Demo program. Use "Demo" to explore all test programs. Installing FLTK ----------------- +******************************************************************************** + The information in this chapter is NO LONGER RECOMMENDED by the FLTK team. +******************************************************************************** + The default location for VisualC 2008 libraries and headers is here: C:\Program Files\Microsoft Visual Studio 9.0\VC\ @@ -401,7 +416,11 @@ conflicts. Use the static .lib libraries instead. Creating new Projects ----------------------- -This chapter assumes that libraries and headers are copied into +******************************************************************************** + The information in this chapter is NO LONGER RECOMMENDED by the FLTK team. +******************************************************************************** + +This chapter assumes that libraries and headers were copied into C:\Program Files\Microsoft Visual Studio 9.0\VC\ @@ -439,57 +458,39 @@ is changed, the corresponding .cxx file will be recompiled. Prerequisites --------------- -In order to build FLTK from within VisualStudio 2010 or later, you need to -install the VisualC developer environment from the Microsoft web site. The -Express edition is free of charge and sufficient to develop FLTK applications: - - http://www.microsoft.com/express/Downloads/ +See previous chapter "HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO". Downloading and Unpacking --------------------------- -Download FLTK from here: - - http://www.fltk.org/software.php - -If you are familiar with "subversion" and like to stay current with your -version, you will find the subversion access parameters at the bottom of -that page. - -Unpack FLTK by using an appropriate unpacker and copy the new folder into a -convenient location. I have set up a "dev" folder in my home folder for all -my projects. +See previous chapter "HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO". Configuring FLTK ------------------ -Launch VisualStudio. Open the project file in - - .../fltk-1.3.xxxx/ide/VisualC2010/fltk.sln - -Choose "Debug" or "Release" mode from the "Solution Configurations" menu. +See previous chapter "HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO". Building FLTK --------------- -Use the context menu of the "demo" project to "Set as StartUp Project". Then -select "Build Solution" from the "Build" menu or press F7 to build all -libraries. - +See previous chapter "HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO". Testing FLTK -------------- -Select "Start Debugging" from the "Debug" menu or just press F5 to run the -Demo program. Use "Demo" to explore all test programs. +See previous chapter "HOW TO BUILD FLTK USING MICROSOFT VISUAL STUDIO". Installing FLTK ----------------- +******************************************************************************** + The information in this chapter is NO LONGER RECOMMENDED by the FLTK team. +******************************************************************************** + The default location for VisualC 2010 libraries and headers is here: C:\Program Files\Microsoft Visual Studio 10.0\VC\ @@ -515,6 +516,10 @@ conflicts. Use the static .lib libraries instead. Creating new Projects ----------------------- +******************************************************************************** + The information in this chapter is NO LONGER RECOMMENDED by the FLTK team. +******************************************************************************** + This chapter assumes that libraries and headers are copied into C:\Program Files\Microsoft Visual Studio 10.0\VC\ @@ -605,20 +610,19 @@ The following links may be of use: 1. Main Cygwin homepage: - http://www.cygwin.com/ + http://www.cygwin.com/ -2. Main Mingw homepage: +2. Main MinGW homepage: - http://www.mingw.org/ + http://www.mingw.org/ In particular look for the MinGW FAQ at this link for - a lot of useful Mingw-native development - documentation. + a lot of useful Mingw-native development documentation. 3. Check out the FLTK newsgroups at the FLTK homepage: - http://www.fltk.org/ + http://www.fltk.org/ Its archival search facilities are EXTREMELY useful to check back through previous problems with this @@ -626,11 +630,15 @@ The following links may be of use: 4. GNU Compiler Collection (GCC) compiler homepage: - http://gcc.gnu.org/ + http://gcc.gnu.org/ 5. OpenGL page - for OpenGL and GLUT libs - http://www.opengl.org/ + http://www.opengl.org/ + +6. CMake homepage: + + https://cmake.org/ @@ -639,5 +647,6 @@ The following links may be of use: Oct 25 2010 - matt: restructured entire document and verified instructions Dec 20 2010 - matt: merged with README.win32 -Dec 22 2010 - AlbrechtS: added newer Cygwin (cross/mingw-w64) options -Feb 24 2012 - AlbrechtS: clarified console window FAQ +Dec 22 2010 - Albrecht: added newer Cygwin (cross/mingw-w64) options +Feb 24 2012 - Albrecht: clarified console window FAQ +Jul 05 2017 - Albrecht: several updates, particularly on Visual Studio usage diff --git a/README.abi-version.txt b/README.abi-version.txt index 6c760bc76..d40ef71dd 100644 --- a/README.abi-version.txt +++ b/README.abi-version.txt @@ -66,10 +66,13 @@ the version number. FLTK versions 1.4.0 and later contain full CMake support. Use CMake to build the Makefile's and run 'make'. To configure the - ABI version, use ccmake, cmake-gui, or run make with the following + ABI version, use ccmake, cmake-gui, or run cmake with the following command: cmake -D OPTION_ABI_VERSION:STRING=10401 /path/to/fltk + + Then execute + make You can define OPTION_ABI_VERSION to the required version number using @@ -95,7 +98,7 @@ the version number. Use CMake option OPTION_ABI_VERSION:STRING=10401 with the command line - or any of the CMake GUI programs. + or set OPTION_ABI_VERSION with one of the CMake GUI programs. Then start the build process in the IDE solution of your choice. This will run the build with the defined ABI version. -- cgit v1.2.3