| Is the references tab (C/C++ General) feature known to be seriously buggy? [message #1823259] |
Mon, 23 March 2020 18:46 |
 John McCabe
Messages: 228
Registered: July 2009 |
Senior Member |
|
|
I've been using the references feature from the C/C++ General settings for a little while now as it seems to be the way to make sure that, when I build something, it actually uses the correct build of other projects. E.g. I have 6 build configurations, 3 x Debug+Release for native, cross for pi and cross for another ARM device, with suffixes added to the build artefacts to differentiate (e.g. no suffix => release, _d => debug, and _a/_ad or _b/_bd for the other pairs. However I'm finding my .cproject files appear to be corrupted quite often; are there known issues in this feature?
For example, having taken a very close look at some .cproject files, it looks like each configuration has an "externalSetting" node that looks a bit like this:
<externalSetting>
<entry flags="VALUE_WORKSPACE_PATH" kind="includePath" name="/EMADDSLib"/>
<entry flags="VALUE_WORKSPACE_PATH" kind="libraryPath" name="/EMADDSLib/Debug"/>
<entry flags="RESOLVED" kind="libraryFile" name="EMADDSLib_d" srcPrefixMapping="" srcRootPath=""/>
</externalSetting>
I'm randomly finding the 2nd and 3rd lines of some of those missing, which confuses other projects that refer to this configuration through the storageModule node with moduleId="org.eclipse.cdt.core.externalSettings".
I'm not really sure how widely used this feature is; I suspect not very given the experience I've had with it.
Anyway - just wondering what others' experience of it is before (oops) checking if this is a known bug on bugzilla.
John
|
|
|
Powered by
FUDForum. Page generated in 0.03612 seconds
] 
Search
Help
Register
Login
Home
