[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] How to produce build output for scanner info discovery?
|
I believe so. I would also quit and reenter eclipse, doublecheck the settings, clear discovery profile, rename the project and rebuild the index - all in random order. Don't ask, this is an art of black magic.
Andrew
On Fri, Jan 14, 2011 at 2:36 PM, Sergey Prigogin
<eclipse.sprigogin@xxxxxxxxx> wrote:
What discovery options should I use? Are the following options ok?
Discovery profiles scope: Configuration-wide
Discovery profile: GCC per file scanner info profile
All checkboxes enabled.
-sergeyOn Fri, Jan 14, 2011 at 11:26 AM, Andrew Gvozdev
<angvoz.dev@xxxxxxxxx> wrote:
You need full gcc commands printout in the output (-n option) and pushd/popd output could help, i.e messages like "Entering /current/working/directory/" (-w option).
Andrew
On Fri, Jan 14, 2011 at 1:56 PM, Sergey Prigogin
<eclipse.sprigogin@xxxxxxxxx> wrote:
Does the silence mean that nobody was able to successfully import complex makefile projects into CDT?
-sergey
I'm trying to configure a C++ makefile project on Linux. From the command line the project is built using a hierarchical system of makefiles. What is the right way to produce a build output file for loading on the Discovery Options page? I tried to run make -n on the top level makefile to produce the build output. Loading that file did help to resolve couple include directories, but the majority of required include directories and externally defined symbols were still missing.
Could please somebody enlighten me on how to produce the build output file expected by the scanner info discovery and what options to choose on the Discovery Options page.
-sergey
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev