J. Liles
2012-07-27 18:25:40 UTC
All,
It got to the point where I couldn't maintain the 'next' branch anymore
without including my new NTK (my Cairo-enabled superdooper FLTK fork)
stuff. So if you pull from next do git submodule init and git submodule
update you should see a ton of changes including a dependency on libcairo
and much improved graphics (as well as a fancy new 'Cairo' theme). I'm
still trying to get all the GUI related issues resovled before the next
release... I already know that there are problems and what they are, so
please don't flood me with complaints about the GUI.
Hi Male,It got to the point where I couldn't maintain the 'next' branch anymore
without including my new NTK (my Cairo-enabled superdooper FLTK fork)
stuff. So if you pull from next do git submodule init and git submodule
update you should see a ton of changes including a dependency on libcairo
and much improved graphics (as well as a fancy new 'Cairo' theme). I'm
still trying to get all the GUI related issues resovled before the next
release... I already know that there are problems and what they are, so
please don't flood me with complaints about the GUI.
Just had a bit of time to check this, but actually couldn't get it
http://paste.debian.net/180830/
Another question: if building this ntk module, and installing it in
/usr, is it going to take the place of fltk? and especially of fluid?
it, you have to do make -C lib from the base of the repo in order for the
NTK configure script to get run with the correct arguments. If you've
already tried to build it in another way, you'll have to delete
lib/ntk/config.h and lib/.built to trick make into running the configure
script again.