nanogui: Building my own examples
Subject:
Re: [nanogui] Building my own examples
From:
"Edward King" ####@####.####
Date:
12 Jun 2007 14:13:05 +0100
Message-Id: <001601c7acf3$443bd230$460aa8c0@eklt1>
----- Original Message -----
From: "Greg Haerr" ####@####.####
To: "Edward King" ####@####.#### ####@####.####
Sent: Tuesday, June 12, 2007 1:43 AM
Subject: Re: [nanogui] Building my own examples
>> I finally got Nano-X to compile by removing the ttf (1 and 2) stuff from
> the config file. Thats a shame really, because it would be nice to use
> TTF's.
>
> Well, all you have to do is install freetype and you'll have TTFs.
Yes, I actually cant get freetype to build. Thats something else I have to
look into!
Perhaps its because Im using Slackware and the freetype website seems to
imply everything is geared towards redhat or debian?
>
>
>> The thing that I find odd though is that in the example in the
>> programming
> tutorial, only two includes are specified (stdio.h and graphics.h) yet in
> the other demos, nano-X.h and stdlib.h are required.
>
> No, that's not odd, its design. The whole idea is to use only the
> standard
> C header file stdio.h and microwindows' only public header file nano-X.h.
No, I meant that its odd that in the programming tutorial graphics.h is
specified, but in the demos in the source directory, nano-X.h is specified.
Is the use of graphics.h no longer the way to do things?
>
>
>> Is this just a case of out of date documentation (and if so, should I be
> using the other demos as a template for testing) or is this the base usage
> appropriate for what Im trying to do?
>
> Just make sure that <nano-X.h> is accessible either in /usr/include or
> with a -I<path> in your makefile, along with the libnano-X.{a,so}
> client link lib.
>
> Regards,
>
> Greg
>
