STR #3264

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 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]

Return to Bugs & Features ]

STR #3264

Application:FLTK Library
Status:1 - Closed w/Resolution
Priority:1 - Request for Enhancement, e.g. asking for a feature
Scope:3 - Applies to all machines and operating systems
Subsystem:Build Files
Summary:The autotools build system does not build FLTKConfig.cmake
Created By:elgaton
Assigned To:AlbrechtS
Fix Version:1.5.0
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:

No files

Trouble Report Comments:

Name/Time/Date Text top right image
#1 elgaton
02:48 Nov 02, 2015
If FLTK is built with autotools, FLTKConfig.cmake is not created nor installed. This forces developers using CMake as their build system and on a distribution using autotools in the FLTK package build file to recompile FLTK or create FLTKConfig.cmake manually in order to link their software with the library.  
#2 AlbrechtS
08:33 Nov 03, 2015
Thanks for the report.

I can see your point: Linux distros use (and _should_ currently use) autotools to build FLTK. It would be nice to ship the CMake files with the distro so users can use CMake to build their own software, although the shipped and installed version was built with autotools.

That said, I'm afraid we can't resolve this issue quickly. We'd need to generate three files (actually six, see below):

 - FLTKConfig.cmake (as mentioned by the OP)
 - FLTK-Targets.cmake
 - UseFLTK.cmake

or (maybe, if possible) one file containing everything in these three files.

We need to generate two versions of each file to have a complete CMake build environment: one file for use with the build directory and one file for use with the install directory.

All these (six) files are generated by CMake and contain CMake-specific code and variables. We'd need to replicate these files as templates for the autotools build system and update them regularly if the CMake build system changes these generated files.

That would be possible, but not easily maintainable. Currently we don't support this scenario. CMake support is still experimental and incomplete.

We can try to do this later, but please don't hold your breath. It's very likely that this will not happen before FLTK 1.4.0.
#3 AlbrechtS
08:37 Nov 03, 2015
Changed priority from 2 (low) to 1 (RFE).  
#4 AlbrechtS
07:53 Aug 08, 2016
Pushed from 1.3-feature to 1.4-feature.  
#5 AlbrechtS
15:11 Jan 16, 2023
Assigned to myself.

Please see also GitHub Issue #655 "CMake fixes".
#7 AlbrechtS
08:47 Nov 17, 2023
FLTKConfig.cmake can't be built by the autotools system because it would need too many internal information that only CMake has.

The short term "solution" for users is to build FLTK with CMake. Hopefully Linux distributors and others will do this once FLTK 1.4.0 will be released.

Please note that autotools (configure/make) builds will not be supported starting with FLTK 1.5.0 (or any version higher than 1.4.x).
bottom left image   bottom right image

Return to Bugs & Features ]


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