Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] A few more build/project questions

Hi Sascha,

Sorry for not responding sooner.
I've been thinking on how the .d files and custom dep calculator could
be put together, and I guess that making the TYPE_CUSTOM implement the
IManagedDependencyCommands as you propose should work for all the issues
you are mentioning.
Of course some changes will be required to the Internal Builder to make
it pick up the IManagedDependencyCommands info for the TYPE_CUSTOM, but
I guess this should not be a hard change since most of the functionality
of dealing with the IManagedDependencyCommands is already there.

> I'm going to work on this when I get the time. If everything works
well I'll
> probably be able to contribute the code to future CDT.
That would be great. Feel free to ask any question/problems you
encounter while working on this.

Regards,
Mikhail

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sascha Radike
Sent: Thursday, April 26, 2007 3:47 PM
To: 'CDT General developers list.'
Subject: Re: [cdt-dev] A few more build/project questions

Hi Mikhail,

Thanks for the reply. Please see my questions below:

>My current thought is that the TYPE_CUSTOM dep calculator should be
>used.

Creating a .d dependency generator I need to let the builder know about
the
command flags which should be added. Am I supposed to return a
IManagedDependencyCommands for TYPE_CUSTOM, too?

And I think I have to inform the builder about the additional .d files
being
created. I think somewhere in the internal builder code certain output
files
will be deleted (like .o) ("Clean selected file(s)" maybe?). So when the
.o
gets deleted, the .d should be deleted, too.

I'm going to work on this when I get the time. If everything works well
I'll
probably be able to contribute the code to future CDT.


Sascha

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top