Short answer: yes.
Long answer follows (no need to read unless you're really interested):
Either that (another name) or even another directory as suggested by
Greg. One problem I'm still working on is the multi-config build feature
of IDE's like Xcode, Visual Studio, and maybe others.
Since we have two or more different build types (Debug, Release, ...) we
can't create `fltk-config` statically at configure time as it is done
now. We must either postpone creating it at build time or even later at
installation time. I don't know what the final solution will be, but
I'll try to take care of the concerns regarding multiple instances of
fltk-config.
Some preliminary thoughts:
(1) the fltk-config file to be used in the build tree may need to be
created in the specific build directory, i.e. for instance in Xcode builds:
- BUILD/bin/Debug/fltk-config
- BUILD/bin/Release/fltk-config
- etc. for more build types
For single config builds (Makefiles, Ninja, ...) this would collapse to
- BUILD/bin/fltk-config
Note that this is different from now where the file to be used with the
build tree is:
- BUILD/fltk-config
This seems to be wrong from my POV of today.
This fltk-config file would most likely have to be created during the
build process (`make` ...) rather than at configure time (same as the
macOS wrapper scripts).
(2) the fltk-config file to be installed can be created elsewhere or
maybe only at `install` time. We have other files in the folder `etc`
(CMake config files to be installed). This is a possible place but maybe
not optimal.
I still need to find out how this can all be done to be able to support
both single- and multi-config builds and to avoid confusion.