Community
Participate
Working Groups
Build Identifier: I20110613-1736 If I am indexing remotely-located code, I may choose to use different compiler options from the default. This means that when RDT runs the remote "gcc -dD ..." command, it's not going to obtain the correct set of predefined macros. In addition, since it uses -dD instead of -dM, it obtains an incomplete set of predefined macros for the indexing process. As an example of the former, consider the case where the remote code is set up to build with the -m32 option, but the default is -m64. running "gcc -dD ..." without the -m32 will cause the 64-bit macros to be emitted instead of the 32-bit ones, which will may cause the indexing of the source to be off. In my case, I am indexing the Linux kernel source, which relies on many of these macros, and without the correct macros, the indexing is done incorrectly. Reproducible: Always Steps to Reproduce: 1. Create a Remote C/C++ Project 2. Choose the Remote Linux GCC toolchain 3. Open the project properties and examine the C/C++ Build->Discovery Options page 4. Notice that there is no place to add or modify options passed to gcc (g++ ?)
This is really a CDT problem. It handles the discovery mechanism.
Thanks for your reply, Chris. It's not clear to me that what you said is correct. If I use the local Linux GCC Tool Chain, I *can* specify compiler options to use during discovery. However, that part of the dialog disappears when using the Remote Linux GCC Tool Chain. Is Remote Linux GCC part of the CDT, or part of PTP/RDT, etc.?
Hmmm... maybe we overrode the page? I'll have a look, but I didn't think we did.
As near as I can tell that's the stock property page from CDT. I'll look at the page, I'm not sure what criteria it is using for displaying the controls.
Looks like there is an extension point that allows you to contribute an options page that is mapped to your discovery profile ID. We didn't know this existed so we didn't contribute any pages for the remote discovery profiles. Bouncing back to RDT again.
Assuming this will not be fixed.
