On 4/27/21 11:59 AM ken williams wrote:
I've probably done something wrong when installing/uninstalling so many
Yes, that could explain some of the issues you saw.
there's a folder FL but it's empty
which I noticed that it's normal behavior after uninstalling FLTK (with
sudo make uninstall)
Hmm, later you say ...
so I installed FLTK (sudo make install)
and uninstalled it (sudo make uninstall)
and the files were automatically removed
Yes, that's what really should happen. It's good that you found it now
and removed the "system" installation.
Here's another hint: the default install location with CMake is to
install in /usr/local which is often good since most of the installed
software would be found automatically. However, if you're instaling
"experimental" software  it's better to use a separate installation
directory. With CMake you can set the variable CMAKE_PREFIX_PATH
(default: /usr/local) to something different, e.g. with
$ cmake -D CMAKE_PREFIX_PATH=/home/me/dev/fltk-1.4 <other options>
A big advantage of using distinct install folders is that you can
"uninstall" by just deleting the entire folder (rm -rf <folder>). If you
install FLTK 1.3 and 1.4 in different folders below your home dir, that
would be a great achievement because you could switch your app build
easily between both versions (see below).
You can also inspect the install directories to see what gets installed
and where (which subdirs) which can help you learn about how to build
 I call it "experimental" because you're currently trying it out. I'm
always using this because I want to have several versions installed, for
instance 1.3 and 1.4, but also with different configurations (pango,
cairo, debug, release, and so on).
No fltk-config here:
FL folder empty:
but now the Makefile doesn't find the fltk-config...
[ken01@Manjaro 1.make_fltk]$ make
make: fltk-config: No such file or directory
and fltk-config is not found even from the home path:
I'm missing something else here?
You need to tell the system where your fltk-config is located. If it's
in /usr/local/bin then it's in your PATH and it's found automatically.
shows you where the system searches for executable files.
I suggest not to change the PATH though. You should change your Makefile
instead such that fltk-config is found, maybe like this:
Then replace 'fltk-config' with $FLTK_CONFIG or maybe $(FLTK_CONFIG) 
and you should be done. Also, remove all other hard-coded paths, use
$FLTK_CONFIG exclusively for all compiler and linker flags. This way you
can change FLTK_CONFIG to switch between FLTK 1.3 and 1.4 or just
another install directory if you installed more than one version.
 I'm not a Makefile expert
Finally: please don't top-post and trim your citations. Thanks.
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/d3c7c81f-c2ff-7ae4-2917-aa7288694fb5%40online.de.
[ Direct Link to Message ]