nanogui: Makefile.rules
Subject:
Re: Makefile.rules
From:
Jordan Crouse ####@####.####
Date:
28 Nov 2000 19:08:39 -0000
Message-Id: <3A240352.3CC12D5A@censoft.com>
Hmmmm... I don't know about that. My inital reaction is no, since most
of the platform specific stuff goes on in the server anway, but we
should ask the expert. Greg, if one was to write a "glue layer" that
interfaced with the server, would they need the defines from the config
file or would it be sufficent to just include the header files?????
Gary James wrote:
>
> Thanks Jordan that looks a whole bunch easier. I'll do that tonight.
>
> For some reason I got into my head that I needed the defines that
> result from the config file.
>
> At one point I was looking at Microwindows programming from the point
> of view of the "middle layer". I was interested in Gregs "Glue
> layers..." article
> (http://www.linuxdevices.com/articles/AT5848940287.html).
>
> If I do try to interface to the drawing engine, rather than to one of
> the current "top layers" (mwin or nano-X), do I need to know about
> those defines that result from the config file?
>
> Thanks
> Gary James
>
> Jordan Crouse wrote:
> >
> > Gary -
> > Thanks for your work on this matter. However, when building
> > applications based on Microwindows, Greg has built the system in such a
> > way, that you simply need to link to the libraries available in the
> > /src/lib directory and the headers found in /src/include. In fact, you
> > would be best served if you ignored all of the complicated targets that
> > Microwindows has, and just narrow yourself down to something similar to
> > the following:
> >
> > ------------
> >
> > MWBASEDIR = /foo/bar/microwin/src
> > MWLIBDIR = $(MWBASEDIR)/lib
> > MWINCDIR = $(MWBASEDIR)/include
> >
> > foo.target: foo.o bar.o
> > $(CC) -o foo.target -I$(MWINCDIR) -L$(MWLIBDIR) foo.o bar.o -lnano-X
> >
> > .PREFIX: .o .c
> >
> > .o.c:
> > $(CC) -c -I$(MWINCDIR) $< -o $@
> > -------------
> >
> > In fact, we build the FNLX and ViewML binaries in exactly this manner.
> > This has the advantage of being easier for other people to understand,
> > especially if you are writing code that will be open source.
> >
> > In the near future, we hope to have a standardized installation process
> > for microwindows, which will place the libraries and headers in a
> > standard location (kind of like what X11 does), which will make this
> > process even easier, especially for novices. Stay tuned.
> >
> > Happy hacking,
> > Jordan
> >
>
> --
>
> Gary A James, Critical Link, LLC
> Voice: 315.425.4045 x218
> Fax: 315.425.4048
> E-Mail: ####@####.####
> WEB: http://www.criticallink.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
