MacArthur, Ian (SELEX GALILEO, UK) wrote:
> What are we going to call fltk-config and the libs themselves?
> During the transition I (and I guess others) am going to have
> fltk-1.1.8, fltk-2 and fltk-1.3 around... At present, I have the
> following:
>
> Fltk-1.1 : fltk-config, libfltk.a, etc.
> Fltk-2 : fltk2-config, libfltk2.a, etc.
> Fltk-utff8 : fltk-utf8-config, libfltk-utf8.a, etc.
>
> Where will fltk-1.3 fit in?
for now i use:
Distro's fltk: fltk-config
latest fltk-1: fltk1-config
(*modified, see below)
latest fltk-2: fltk2-config
with ~/bin/fltk?-config symlinked to ~/src/fltk?/fltk-config
and ~/src/fltk? symlinked to fltk-?.*.x-whatever
For what i wish is to allow fltk to be usable without
installation (not even local). Perhaps it's a good idea
to add:
[--fluid] return Fluid path
or --basepath to fltk-config. (not really important, could
be done in makefiles with --cflags and sed)
This way allows parallel installation of fltk,
and provides easy version switching (just change symlink).
If it seems necessary to have distinct 1.1 and 1.3 versions
i would extend this to:
fltk1.1-config
fltk1.3-config
greetings
* added selfdir-readlink detection from fltk2-config
#selfdir=`dirname $0`
# First, we need to figure out where we are, ...
# BUT to do that we need to check if we were called via a symlink
# AND some systems (e.g. mingw) have neither symlinks, ...
HAVE_READLINK=`type -p readlink`
if test -z "$HAVE_READLINK"; then
# We don't have readlink, so just use local dir as selfdir
selfdir=`dirname $0`
else
# We do have readlink - let us check if we were called via a symlink
selfdir=`readlink $0`
if test -n "$selfdir"; then
# Was a symlink, find the real selfdir
selfdir=`dirname $selfdir`
else
# Not a symlink, find the selfdir
selfdir=`dirname $0`
fi
fi
b.t.w
there was (is) a bug with --libs returning wrong libs, hope this is fixed.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
