Has anyone here had any luck compiling the cvs version of fltk-2.0? I have tried a couple of times by updating every couple of weeks but havn't been able to get past the fluid linking stage.

Plumb

Ignore the previous message, as I have successfully compiled the cvs version from Oct 23, 2004.

I use fltk2.0 for a long time(mingw and FreeBSD)

Glad to hear you got the 2x compiled. I am just getting ready to do the same. Nice to see you both here.

__________________
"Opportunity is missed by most people because it comes dressed in overalls and looks like work."
--Thomas Alva Edison
"Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety."
--Benjamin Franklin
"A happy person is not a person in a certain set of circumstances, but rather a person with a certain set of attitudes."
--Hugh Downs

tell us how U try to build fltk2.0cvs... may be we can help...

Building from CVS snapshot using:

fltk-2.0.x
gcc 3.3.3 <cygwin special.
bash 2.05b

configure
make
then I would:
make install
make clean

I am having some problems (I believe I am missing a -I libs path) so when I got to the fluid linking stage a had a full failure. I had some similar problems with 1.1.5 and had to edit a few dependencies. For now, I just:
make uninstall
make clean

cd /usr/src/fltk1.1.5
configure
make
make install
make clean

I will have to get back at 2.0 next week as I am moving my home this weekend and doubt I will have much time. Thanks for the offer. I will get back here when I start to jump to 2.0. Looking through the newsgroups at fltk.org I noticed a few pointers when using cygwin.

__________________
"Opportunity is missed by most people because it comes dressed in overalls and looks like work."
--Thomas Alva Edison
"Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety."
--Benjamin Franklin
"A happy person is not a person in a certain set of circumstances, but rather a person with a certain set of attitudes."
--Hugh Downs

give us a log when U build sources

For those of you that have built fltk 2.0, does it coexist nicely with the 1.1 branch? I would like to experiment with 2.0, but I don't want to rework all of my existing 1.1 based programs at this time

Thanks.

__________________
The best damn Sports Blog period.

My first attempt with the cvs failed not so badly. I made it to the linking stage with fluid.exe. Then, (what a mistake) I took some advice from the fltk.org newsgroups for changes suggested and my failures compounded. As far as living a comfortable life alongside the 1.1 branch, my opinion is no. It seems that there are named files common to both. Of course, this could also be no more than the new fltk-config not being created or something toward the end of the make.

To clarify, when the 2.0 install failed I jumped back to my work dir to see if I could compile an existing 1.1.x project. Not a chance. I must add though that doing an uninstall and clean on the 2.0 worked great. It was then just a matter or doing a make install on 1.1.5 and I was back to compiling the old project. So I will give it another go by the weekend.

I am not entirely sure that some of my failure was not due to my cygwin installation though. That has always been a bit of a mystery to me no being a *nix person.

Working on the 2.0 install I found some (minor) adjustments needed (zlib, jpeg and png) mostly resolved by adding a "../" to an include. If anyone has successfully built 2.0 I would love to see a success story especially if it is with a cygwin installation. Going through the fltk2.0.x/src it appears that the old "Fl/" is the same as 1.1.5 with the addition of a "fltk/" dir that looks like the "new" way the headers are stored. The names don't all start with "Fl_" as they did before. My thought was so that both the 1.1 and 2.0 would live in harmony. I can't back this up with fact though, just speculation. Hopefully someone out there is having more luck with this than I am. I really like what I have seen of the changes (just the addition of fltk own namespace to start with) seems to say, this is the way it will be done from now on.

My hope is that we will see a source tarball soon so I can quit fighting with cvs.

edit: I will include a log when I make my effort this weekend. Thanks for that simple (yet important) advice. Unless Kreskin is out there it is the only way to get reliable help. :-)

__________________
"Opportunity is missed by most people because it comes dressed in overalls and looks like work."
--Thomas Alva Edison
"Those who would give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety."
--Benjamin Franklin
"A happy person is not a person in a certain set of circumstances, but rather a person with a certain set of attitudes."
--Hugh Downs

for tarbals try http://www.fltk.net
if U use cygwin - try to use www.mingw.org(mingw + msys + msysDTK) - it it more faster and friendly with windows