Subject: Re: installing tools to compiler pbsdboot.exe
To: TAKEMURA, Shin <takemura@netbsd.org>
From: Chris G. Demetriou <cgd@netbsd.org>
List: port-hpcmips
Date: 01/06/2000 11:55:34
"TAKEMURA, Shin" <takemura@netbsd.org> writes:
> >I've got some improvements to the project files, etc., but i want
> >folks to try them out with VC5 before i check them in.
> 
> Shall I try that? How can I get patches?

NetBSD developers can grab a copy of my update at
cvs.netbsd.org:~cgd/dspgen.shar

run that script in hpcmips/stand.  It'll create a few directory
(dspgen) and some new files.  run 'make -f Makefile.winfiles' at the
top level, and you'll have automatically generated project files for
libsa and pbsdboot and a workspace file in stand (which even gets the
dependency right).

Building the project files automatically like this is in many ways the
Right Thing.  Using the GUI to frob the project files is kinda broken,
because it often leads to inconsistencies in the flags used to build
the projects, etc.  Plus, if you want to make one sweeping change, all
you need to do is figure out how to modify the config files and/or the
project file templates, and you just re-make.

In general, the way you use these are, to make an update to the
project files, you tweak the appropriate files and re-make.  Your IDE
may update your .dsp files to its current style, but you shouldn't
check those in; instead after verifying that they work, you re-gen and
check in the generated files.  (You'll note that this also provides a
somewhat-sane way for people who have to use VC6 to make changes to
the project files, as well.)

The actual changes caused by the scripts/templates that are there now
are fairly miniman.  I made the Debug and Release targets have
comparable sets of flags (/D's, /I's), and tweaked the Release targets
compilation flags so that 'Release' actually builds.


On the topic of CRs in the files:

At least VC6 seems to:
	* require CRs in the .dsp and .dsw files
	* cope with either CR/NL or just NL as the line-end convention
	  in actual sources.  Like, I can srip the CRs off the .h and
	  .c files, and they work, and when i edit and save them, they
	  don't get CRs added back.

Does VC5 work the same way?  (If so, we can nuke the CRs in the source
files, which would make them more editable under UNIX...)


cgd
-- 
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.