Eric Liao wrote:
> 1. I tried "fltk2-config --compile mycode.cxx" and got the correct
> display. So, the problem is solved. What left to answer is how did that
> happen. I have some interesting test result. Please read the following.
>
> 2. I always built your code using: "g++ -o fltkhello1 fltkhello1.cxx
> -I/usr/local/include -L/local/lib -lfltk2 -lXext -lXft -lX11 -lXi -lm".
I was able to compile+run with that same g++ command
and it worked fine.
I wonder if when you checked out the new fltk2, did you also
do a 'make install' after doing the 'make' to install it?
If not, the 'old' fltk2 would still be out there in /usr/local/include,
which would link against the 'old' fltk2,
while the 'new' fltk2 would still be in your fltk-2.x dir.
The above g++ command assumes linking against the 'installed' fltk2,
where 'fltk2-config' will use the libs that are in the fltk2 source
directory (which would work whether you did the 'make install' or not)
This could explain why there's a difference between using fltk2-config
and the g++ command.
I would think if you do a 'make install', then the above "g++" command
would then work normally.
If that helps, then the issue was the 'old' fltk2 that you had
installed was the problem.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
