This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: Automatic dependency generation for libcpp


DJ Delorie <dj@redhat.com> writes:

>>  Report bugs to <bug-automake@gnu.org>.
>>  EOF
>> -    exit 0
>> +    exit $?
>>      ;;
>>    -v | --v*)
>>      echo "depcomp $scriptversion"
>> -    exit 0
>> +    exit $?
>
> Won't these return the exit code of cat and echo, respectively?

Looks like it; however, that should be harmless, as they are unlikely
to fail.  In any case, that's not my change; it's part of the import
from automake CVS.

>> +-include $(patsubst %.o, $(DEPDIR)/%.Po, $(libcpp_a_OBJS) $(makedepend_OBJS))
>
> We're back to the usual questions:
>
> * What happens if the .Po files don't exist?

The leading dash on "-include" causes GNU make to proceed regardless.

> * What happens when dependencies change and headers get removed?

The .Po file contains dummy targets for each header, of the form

foo.h:

which prevents Make from complaining.  When GCC is in use, these are
triggered by the -MP switch on the compile command line.  For other
mechanisms, they're synthesized inside 'depcomp'.

zw


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]