FLTK logo

Re: [fltk/fltk] Build instructions for Unix seem out of date (#67)

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.issues  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: [fltk/fltk] Build instructions for Unix seem out of date (#67) Albrecht Schlosser Apr 16, 2021  
 

@diplodocuslongus Hi Ludo, thanks for testing and reporting your results here. The general answer to this issue is that I intend to add another chapter to the docs describing the correct way to build FLTK itself and to build programs with FLTK. I hope I can find the time soon after the release of 1.3.6.

Regarding some of your points:

  • using the instructions in the README_Unix.txt

These instructions are really outdated. With the latest version 1.4 (Git master) an easier way is:

autoconf
./configure
  • using the approach mentioned above by @Albrecht-S (me)

The idea here it NOT to run a full make in the first step which would build the entire FLTK library and test programs unless you interrupt it with ^C. Using make clean as the first command skips the build step and is much faster, so you would use:

make clean
./configure <options> ...
make
  • using cmake

Instructions are so far correct. There's indeed no .configure but there are several CMake options you can set via the commandline or edit in the cache.

  • Worth noting, there's also the approach to download a tar.gz archive ... (URL elided)

Where did you get that URL from? The correct URL is: https://www.fltk.org/software.php?VERSION=1.3.5 where VERSION=... may be omitted or replaced with the requested version. You still need to select the correct file(s) and trigger the download manually. Note that you can also click the Download link on the main FLTK page.

  • Not mentioned before: you can also download a Zip archive from GitHub for any version (branch, commit) you like. This archive contains the same files as a Git download, hence you need to run autoconf as in points one and two above.

There's much more to say about it (configure and/or CMake options, different CMake generators etc.) which is why I'm planning to add a full chapter to the documentation rather than having lots of README files with unavoidable overlap. For instance README.CMake.txt naturally has to cover all available build platforms and README.Unix.txt also applies to builds under Windows with Cygwin or MinGW (MSYS).


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.