X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C6FEC9.F0C88CA5@onstor-exch02.onstor.net>; Thu, 2 Nov 2006 13:57:50 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: "how to" build and load doc
Date: Thu, 2 Nov 2006 13:57:50 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A9398@onstor-exch02.onstor.net>
In-Reply-To: <20061102132118.45553200@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: "how to" build and load doc
thread-index: Acb+xO7qXFyWA71ER4KPeO8Ny19CJgAAg/iQ
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Henry Lau" <henry.lau@onstor.com>
Cc: "Brian DeForest" <brian.deforest@onstor.com>,
	"dl-Software" <dl-software@onstor.com>

There are tons of Makefile targets most are just short-cuts to run the
same thing different ways. I don't know how many are actually used.

If you type:
 make list-targets=20
at the nfx-tree level you get slightly different results from if you
type the same command inside a subdirectory of code.

Probably one of the least used make commands is:

  make ALL (also make everything)

It actually builds all of the relevant targets whether you are in the
nfx-tree or in a subdirectory of nfx-tree/code. This info is somewhat
buried in the Makefile FAQ.

The Makefile how-to and FAQ was written shortly after I redesigned the
build system and has info in it that probably few care about today. I
wrote it with the mindset of explaning the change to existing developers
versus new hires. Very few of the developers that were around in
December 2004 are still here. I agree it is time to revisit that
document and write a section for the impatient.

Larry

-----Original Message-----
From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
Sent: Thursday, November 02, 2006 1:21 PM
To: Henry Lau
Cc: Brian DeForest; dl-Software
Subject: Re: "how to" build and load doc

I'm working on a a basic workstation setup and configuration howto for
knuckleheads like me who like to brew their own.

My current $0.02 on the wiki:

I was looking for a "Getting Started" entry on the
http://wiki/wiki/Software page, but there isn't one.  If there was one,
it would be very useful if it looked like this:

  + a link to the perforce info wiki
  + a building howto -- including what all the various makefile targets
    really mean and which one you actually want to use
  + a link to the hardware reservation wiki
  + and a howto for getting a build onto a filer

Cheers,

a

On Wed, 1 Nov 2006 18:26:46 -0800 "Henry Lau" <henry.lau@onstor.com>
wrote:

> Hi Brian,
>=20
> Same information can be found in=20
> http://wiki.onstor.net/wiki/Software
>=20
> I went through most of the docs initially and have the directions of
> how to setup perforce, build, and many etc.
>=20
> Henry
>=20
> -----Original Message-----
> From: Brian DeForest=20
> Sent: Wednesday, November 01, 2006 6:23 PM
> To: Ken Renshaw; Tim Gardner; dl-Software; Maxim Kozlovsky; Jonathan
> Goldick
> Cc: dl-QE-staff
> Subject: RE: "how to" build and load doc
>=20
> Just found this doc.   I figured out most of this "the hard way"...
>=20
> http://wiki.onstor.net/wiki/Onstor_Makefile_FAQ_and_Glossary
>=20
> -----Original Message-----
> From: Ken Renshaw=20
> Sent: Wednesday, November 01, 2006 6:21 PM
> To: Tim Gardner; Brian DeForest; dl-Software; Maxim Kozlovsky;
> Jonathan Goldick
> Cc: dl-QE-staff
> Subject: RE: "how to" build and load doc
>=20
> I'll collect what I have and post it as well. there's actually a fair
> amount it's just spread all over ( and some existing in email HOWTOs,
> for example ). Ideally this should cover everything from Perforce
> initial setup, building EverON images and getting them loaded and
> running on filers, through how to debug filers, etc.=20
>=20
> Agree the wiki is probably the best place to coallesce all of this,
> and at least partially agree the new employees should document their
> experiences, i.e. generate/update HOWTO docs as needed. But we, all of
> us who know the processes and tools best, should write the drafts or
> supply the initial inputs to the new guys.
>=20
> Thanks for driving this BTW.
>=20
> -Ken
>=20
>=20
> -----Original Message-----
> From: Tim Gardner
> Sent: Wed 11/1/2006 6:10 PM
> To: Brian DeForest; dl-Software; Maxim Kozlovsky; Jonathan Goldick;
> Ken Renshaw
> Subject: RE: "how to" build and load doc
> =20
> The correct place for this info is the wiki. Some of it is already
> there. More needs to be added.
> I have asked Andy to add new info to the wiki if what he needs is not
> there. Best persons to write the
> howto docs are the new employees.
>=20
>=20
> _____________________________________________
> From: Brian DeForest=20
> Sent: Wednesday, November 01, 2006 6:05 PM
> To: dl-Software; Maxim Kozlovsky; Jonathan Goldick; Ken Renshaw
> Subject: "how to" build and load doc
>=20
> One thing every new engineer immediately needs is a "how to" guide to
> start building and downloading images.   We have discussed this in the
> past.    If you know of any existing documents describing how to build
> and download/mount your build, please forward pointers.
>=20
> Otherwise, one possibility is to checkin a README file in the top
> level nfx-tree.   This would include things like:
> 1.	make command line options
> 2.	ways to install/mount binaries
> 3.	tips, known problems, etc.
> 4.	longer term:   high level functional description of each
> directory  (possibly a different file)
>=20
> Thoughts?   Any volunteers to create a first draft?   I'll bring in
> some Halloween candy for the first volunteer, or treat him/her to a
> beverage of choice in the breakroom.  :-)
>=20
> Brian
>=20
>=20
