said:
>
> >This is an important hint-- the compiler was developed as a Project.
>
> It would be more correct to say the compiler is a subproject.
>
> >The overall project is to develop a compiler.
>
> Not really. OpenWatcom is a complete development system. The compiler is
> an important subproject, but it is really just one of a number of major
> components.
OK. Let's just say that the whole shebang -- the development system --
makes up a project.
> >This abbreviated list shows SOME of the tasks that were used to develop
> >the Watcom compiler.
>
> Some of these are separate components of the development system.
>
> >directory. Some names are obvious such as 'f77' and 'yacc' while other
> >names are more obsucre such as 'wv'.
>
> Yes. Some of the directory names reflect components with names that
> changed long ago. The wv subdirectory happens to contain the debugger.
The terminology is a bit forced: tasks <==> components
My copy of "Practical Project Management" by Dobson is more of a general
introduction to project management. I have a few PM texts that are more
directed to software development. However, the short courses in project
management that I have taken were for more generic projects. (By the
way, we have an overloaded abbreviation in this paragraph. The term
PM here refers to Project Management, not Presentation Manager.)
> >But we have our roadmap and we know that our starting point is the 'vi'
> >editor.
>
> You can do this, but you will quickly find its not going to serve the
> requirements of the development system that has been proposed up to now.
I was going to point out the gotcha in my next post. The version of 'vi'
that comes with OpenWatcom is not a PM application. In fact, the Watcom
IDE throws you into EPM when you want to edit a source file. (And in this
paragraph, PM refers to Presentation Manager.)
> >tasks are laid out in different directories. Code that is specific to
> >OS/2 is in the directories 'bld\vi\os2\', 'bld\vi\os2386\', and
> >'bld\vi\os2i86\'.
>
> In general, these kinds of directories correspond to builds for specific
> os/2 versions. OpenWatcom can be still be built to run on OS/2 1.x,
> although it's likely to need some tweaking to be usable. I don't think
> this build has been tested in a while.
>
> FWIW, if you intend to use the OpenWatcom sources as a starting point for
> you development system of your dreams, you will need to first understand
> the OpenWatcom build system. See bld\builder\builder.doc. The builder
> scripts ensure that the components get built in the proper order. Once
> the initial build has been done, wmake can be used to do peephole
> development within specific subdirectory trees.
But in the brave new world of Warpicity/Developer's Assistant we have no
such thing as a build system. . . . Oh well, we will get there some day.
>
> Steven
>
> --
> ----------------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4
> www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
> ----------------------------------------------------------------------
--
Gregory W. Smith (WD9GAY) gsmith@well.com
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
>> Next Message >>
Return to [ 15 |
March |
2006 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
