 |
Macintosh Development |
[Home]
[About Us]
[People]
[Information Systems]
[Kerberos for Macintosh]
[Applications]
[Miscellaneous Documentation]
|
Macintosh Development |
[Home]
[About Us]
[People]
[Information Systems]
[Kerberos for Macintosh]
[Applications]
[Miscellaneous Documentation]
During the past years, there was not much of a fixed structure throughout the Macdev tree. Various projects have their own ways of doing things, and even thought those were reasonably similar (mostly due to the fact that most of them started as ports from UNIX and/or were started by UNIX programmers), they were dissimilar enough to make the tree rather disorganized and inconsistent. The situation was made worse by several other things: each programmer dealt with Macintosh-specific questions in her own way; no source control has been used on the Macintosh; RCS (via AFS) was not used consistently (and sometimes not at all).
At the moment, we hope to have a CodeWarrior plugin for Kerberized CVS within several months. The command-line CVS client should be working, although testing has been delayed for various reasons (primarily because we had to decide what we would do about the plugin).
Significant changes are necessary to most, if not all, of our projects at this time. Firstly, the new CodeWarrior IDE requires that we convert all of our projects to the new format, and we are also going to use the subproject/multitarget features to deal with building our projects automatically. In addition to this, the Universal Headers have been updated with CodeWarrior 11 so that OLDROUTINENAMES and OLDROUTINELOCATIONS are no longer defined, and some header files have been made obsolete. This requires that we do some searching and replacing throughout our code.
Soon, we'd like to be able to build all of our project automatically directly from the IDE, without having to manually deal with dependencies between them. This is made much simpler with the new CodeWarrior IDE. A uniform, well-defined, and well-organnized structure of the tree would make the transition more complex, but the result of the transition would be a tree that is much more maintainable. (Project-specific documentation in some of our older projects could make this even better, but that's another story...)
The following tree structure we'll begin to follow with the transition to CodeWarrior Professional 1 has been agreed upon in two meetings (June 13 and June 20 1997).
|
Macdev |
|
|
Application projects |
| |
| |
|
|
|
MIT Support Library parts |
|
MIT Support Library common files |
| |
| |
|
|
|
MIT Kerberos for Macintosh parts |
|
MIT Kerberos common files |
|
MIT Kerberos Library parts |
| |
| |
|
|
| |
| |
| |
|
Other projects |
| |
|
Third party software & SDKs |
|
|
|
Project |
|
|
This folder contains the final binaries generated for this project |
|
This folder contains public header files for this project |
|
This folder contains this project's project files |
|
This branch contains the source files for this project |
|
This folder contains intermediate binaries for this project <such as auxiliary code resources> |
|
This folder contains the private header files for the project |
|
This folder contains the precompiled headers for the project |
|
This folder contains the resource files for the project |
|
This folder contains the project's documentation |
|
This folder contains test applications for the project <applicable only to libraries> |
| |
|
|
Tool project folders usually have flat structure, since they tend to be extremely simple. Complex tool projects might have the same structure as applications and libraries.
Questions or comments? Send mail to macdev@mit.edu
Last updated on $Date: 2003/11/18 21:57:55 $
Last modified by $Author: smcguire $