Date: Fri, 2 Aug 1996 07:55:06 -0400 (EDT) From: Chuck Robey <chuckr@glue.umd.edu> To: Tim Vanderhoek <hoek@freenet.hamilton.on.ca> Cc: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu>, FreeBSD Ports <FreeBSD-Ports@freebsd.org> Subject: Re: Sample Makefile Message-ID: <Pine.OSF.3.95.960802075422.5610E-100000@skipper.eng.umd.edu> In-Reply-To: <Pine.SOL.3.91.960802013624.21910A-100000@james.freenet.hamilton.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2 Aug 1996, Tim Vanderhoek wrote: > On Thu, 1 Aug 1996, Chuck Robey wrote: > > > I didn't want to at first, it's 13K in size, but I guess I will. I've > > pasted it to the end of this file. If you comment on it, please don't > > repost the whole thing to the list, but I'd like any comments anyone might > > have. > > Ok. I'll do that. > > > > -------------------cut here (and you'll ruin your monitor!)-------------- > > I'm more worried about what it'd do to my hdd, actually. > > > > |--------------------------------------------------------------------------- > > | NOTE - This file is unneccesarily complicated by these comments. > > | Any comments that begins with "|" MUST NOT be in a final port. > > | They are just here for your enlightenment. > > I'm often critisized for not being particularly tactful, or another such > silly thing, so take this at considerably less than face value. > > I'm not sure I see the advantage of this over the sample makefile already > part of porting.sgml. It doesn't serve to document anything new, and > only complicates the example. Doing my second port right now, I can say > that I think this example would have repulsed me. The current one seemed > to do a great job. What I would find more helpful is more examples with > regards to "real-life" porting problems. For example, an expanded "Do's > and Don'ts" section, or suggestions on when to define a port as > interactive, and when to simply make gimmee-type decisions (wrt to > compilation-options). OK, Jordan was making the same point, maybe it's too complicated. > > > > | LIB_DEPENDS -- depends on this library, both to build and run. > > | Set to "lib:dir", where lib is the name of the library to be searched for, > > | and dir is the name of the directory to go to and do a "make all install" > > | in if the library is not found. If the library is found, then it won't > > | be rebuilt, else the port in "dir" will be built and installed. > > Unless this has changed, you should specify "shared" libraries, here. > Other libraries have to be checked, I believe, either through over-riding > some depends targets (yuck) or making a pre-build: target. > > > > |--------------------------------------------------------------------------- > > | PATCH Creation Notes: > > | > > | To make a patch file: > > To balance my earlier comment (and to continue being frank as opposed to > tactful), I think that this is Good and can be quite useful. I don't > think it belongs in a sample Makefile, though... > > For the rest of it, my original comment applies, though. :) > > > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+-----------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.95.960802075422.5610E-100000>