Timo Röhling writes:
> AFAICT upstream has modified their FLTKConfig.cmake to set
> FLTK_FLUID_EXECUTABLE without UseFLTK.cmake; albeit still to "fluid"
> without absolute path.
Ah, yeah, I see in retrospect that *only* 1.3.3 played poorly with
FindFLTK.cmake.
> Is this sufficient for you to co
Hi Aaron,
On Fri, 24 Jul 2015 19:46:57 -0400 "Aaron M. Ucko" wrote:
Prior to 1.3.3, this worked fine, because /usr/lib/fltk/FLTKConfig.cmake
defined FLTK_FLUID_EXECUTABLE, and to an absolute path at that.
However, 1.3.3 yields a very different setup: the definition appears
only in UseFLTK.cmake
As Rebecca N. Palmer just reminded me at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793517#28 ,
FLTK's upstream README.CMake.txt recommends bypassing CMake's
FindFLTK.cmake altogether by specifying NO_MODULE:
https://sources.debian.net/src/fltk1.3/1.3.3-2/README.CMake.txt/#L235
As such, I'm
Package: cmake-data
Version: 3.2.2-2
Severity: normal
FindFLTK.cmake uses the following call to find FLTK's code generator,
fluid:
find_program(FLTK_FLUID_EXECUTABLE fluid PATHS
${FLTK_EXECUTABLE_DIRS}
${FLTK_EXECUTABLE_DIRS}/RelWithDebInfo
${FLTK_EXECUTABLE_DIRS}/De
4 matches
Mail list logo
