🚀 go-pugleaf

ewc@esca.com (Eric Chamberlain) wrote:

>I am currently working on the essentials for porting a large amount of
>code into VC++ (2.0 on NT).   The applications being ported in are
>written in C and C++ and have non-C, non-C++ files which must be
>processed by a separate tool (developed in-house) which generates C output 
>files.
>
>I am wondering now how to arrange the VC++ IDE so that the "foreign"
>files can be built and dependencies on them be established.

The TOOLS menu is not integrated with the project makefiles.

I ended up using the project and makefile generation capabilities
built into my source code control system (MKS Source Integrity) to
build my makefiles and update dependencies. This has the added
advantage of keeping developers from tweaking settings for individual
files within a project, and forces them to add the files to the Source
Integrity project before they can use them.

The Borland approach (with definable tools) is much better, IMO.
However, it's been unreliable for me (at least in 4.02).