aspose file tools*
The moose likes IDEs, Version Control and other tools and the fly likes Conditional Dependency Scanning issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Conditional Dependency Scanning issue" Watch "Conditional Dependency Scanning issue" New topic
Author

Conditional Dependency Scanning issue

Mahesh Kedari
Ranch Hand

Joined: Nov 28, 2009
Posts: 111
Hi all,
This is about Eclipse CDT framework. I need some help on Conditional dependency scanning issue.

Below is a code snippet where dependency scanning is failing.



I have this structure in test.c file. When i build it for first time, it generates a dependency file test.d.
Depending upon the status of macro ABCD, it adds the entry in test.d file.
e.g. If ABCD is defined then test.d contains entry for a.h In other case it adds b.h

Now once the dependency file is generated, and i go to Managed Build Settings page, and define/remove one macro ABCD, my project gets rebuilt but dependency files does not get deleted automatically.
For reference, below are some of the links of similar bugs.

#343685


#197989

Regards,
Mahesh Kedari - Fidus Technologies Ltd.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Conditional Dependency Scanning issue