Subj : Re: Some makefile questions
To   : borland.public.cpp.borlandcpp
From : Matthias Reuss
Date : Thu Jun 16 2005 10:30 am

"Ed Mulroy" <dont_email_me@bitbuc.ket> schrieb im Newsbeitrag
news:42b05943@newsgroups.borland.com...
> > 1) Is it possible to use a directory as target or source?
>
> No, but what you can do is create a tag file in the directory and test for
> that.
>
> c:\mydir\foodir\tag.txt :
>   - mkdir c:\mydir\foodir
>   @echo abc >c:\mydir\foodir\tag.txt
>
> > 2) Is it possible to have make exit gracefully if some source
> > does not exist?
>
> 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 :-(

> > 3) Can macros be defined within a description block?
> > i.e. something like:
> >
> > foo.obj : foo.cpp
> >    cl foo.cpp
> > MACRO = bar
>
> 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?

Regards,

Matthias

.