Subj : Re: Some makefile questions
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy
Date : Thu Jun 16 2005 08:27 am

There is a facility for forcing make.exe to return zero if a specific 
command fails (some character or word used simiilar to how '-' is used to 
the left of a statement).

I do not recall anything which handles if the file were missing when it 
searches for the dependencies mentioned in a rule.

However I am hundreds of miles away from the docs so all of this is from 
memory so you should consider the source.  You need to look in the 
documentation to verify what I said.

Checking if the VB compiler is present might be done by checking the 
environment strings.  Doesn't VB establish some environment variables? 
Environment variables are handled by make.exe in much the same way as -D 
macros.  With
      "!ifdef" or "!if MACRO_NAME == WHATEVER"
statements you can do conditional expansion of what the make file is.

..  Ed

> Matthias Reuss wrote in message
> news:42b12a95$1@newsgroups.borland.com...
>
>> It already does that, issuing a message something like
>>   name.ext does not exist, do not know how to make it
>> and exits with a return value of non-zero
>
> I know, but this is not really what I need. I would be glad to be
> able to have "make" exit with return value zero in special
> cases. In a large project, there is 1 subproject that needs the
> Visual Basic compiler. There are several workstations that do
> not have this compiler, and they can do fine without compiling
> this subproject; however those that have VB (including the
> compile server), should regularly build it. My plan was to
> check within the makefile whether the VB compiler is present.
> So this seems not to be possible :-(
>
>> ... There is no block limitation on the macro.  If it is defined, then
>> it is known from then on in the make file.
>
> Not really what I hoped for, either. Are flag files the only possibilty to
> save the information whether foo.obj had to be made or had been
> up-to-date?

.