On ubuntu I get the same error. The waf script is failing because pkgconfig cannot find the ntk lib on your system. This is probably because by default the ntk waf scripts install ntk in /usr/local/lib, and pkgconfig doesn't check there. (At least on ubuntu 12.04 it doesn't, I'm assuming the same thing is happening on Arch.) There are two solutions: you can either force pkgconfig to check for libs in /usr/local/lib or you can tell waf to put the ntk lib somewhere else in the first place. I can never remember how to do the first one without reading the man pages. The second solution is easy: when you configure ntk, do it like this:
./waf configure --prefix=/usr (I think...I'm not in front of my linux box right now) Now pkgconfig should be able to find ntk. I also like to configure non this way...though I'm not sure if this is strictly necessary... On Apr 27, 2013 3:18 AM, "Jonathan E. Brickman" <[email protected]> wrote: > On Arch Linux, I'm failing ./waf configure; the log file says: > > ---------------------------------------------------- > Checking for 'ntk' >= 1.3.0 > ['/usr/bin/pkg-config', '--atleast-version=1.3.0', 'ntk'] > not found > from /home/jeb/SRC/non: The configuration failed > > I was careful to build NTK first, I left everything default. Help? :-) > > > J.E.B. > > > On 11/14/2012 04:08 AM, J. Liles wrote: > > All, > > I've converted the build system of non-* (including NTK) over to waf ( > http://code.google.com/p/waf/). That basically replaces a dependency on > makedepend with one on python. Waf is otherwise self-contained. It's a bit > smarter than make, so builds should be quicker and more up-to-date. > > Hopefully this will make things a little easier on packagers too! > > Also, NTK no longer includes an ntk-config program. Instead, it uses > pkg-config like everything else: modules are named ntk, ntk_images and > ntk_gl. > > > > > -- > Jonathan E. Brickmanhttp://linuxsynth.ponderworthy.com > >
