On 05.04.2012 22:20, L Michaels wrote:
> Would appreciate any ideas on this. I did finally try
> export LIBS="-static-libgcc -static-libstdc++ -lgcc_eh"
> just before building fltk and then adding the following to the link for the
> application I wanted to build:
> -static-libgcc -lgcc_eh -static-libstdc++
> Seems to build without errors now and doesn't ask for the MinGW standard C
> and C++ libraries. Not sure if this is the best approach. If anyone has any
> further ideas on this or knows of a better way to do it, please let me know.
That's almost like the way I'm doing it too. I don't know
though what -lgcc_eh is good for, and I don't need it. A quick
search showed "EH support routines" - is this something for
exception handling?
So, what I'm doing: I have a small own configure script that
does this:
CXXFLAGS="${FLAGS}" \
LDFLAGS="-static-libgcc -static-libstdc++" \
./configure \
--enable... (other configure options)
As you can guess, FLAGS can be set to other compiler options.
This is similar to what you do, but I'm using LDFLAGS instead
of LIBS, and I don't (need to) export the variables.
Then, for building your app(s) I recommend to use fltk-config
to add the required libs to your build commands. This is better
if you change the configure options later, and it is intended
to be used just for this case:
$ fltk-config [--use-images] [--use-gl] --ldflags
Note that [] means optional here. You can also use
$ fltk-config --cxxflags
to get the compiler options, and some more.
Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
