AW: [cdt-dev] "Managed Make projects treat the entire project asasource

["Ploett Norbert" <norbert.ploett@xxxxxxxxxxx>]

Leo,

thanks for your answer, though I have to say that you seem to misunderstood the direction my question was pointing to.

> I see the behavior that you want - i.e. that is, both funca and funcb

This was not that I wish to see a particular behavior but just that I find that the documentation may be out of date. The documentation seems to say that the "source folders" feature does not work with managed make projects while my test indicates that it actually does work and limit the scope of the indexer.

How about that?

Thank you,


Norbert

-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Treggiari, Leo
Gesendet: Freitag, 22. Juli 2005 17:22
An: CDT General developers list.
Betreff: RE: [cdt-dev] "Managed Make projects treat the entire project asasource folder." - still true?

MBS tells the rest of CDT about the include paths that it knows about.
It will add to the list from a number of sources:

1.  The tool-chain integrator can tell MBS which environment variables
it uses to look for include and library paths (e.g. lib, include) by
specifying envVarBuildPath elements in the tool-chain definition.

2.  The tool-chain integrator can add to the environment variables by
specifying a project or configuration level environment variable
supplier.

3.  The tool-chain integrator can define a "scanner configuration
discovery profile" that provides this sort of information to both MBS
and the Standard make builder.

I think that all of these are set up for the GNU tool-chain in the MBS
GNU integration.

The user can typically add (depending upon the tool-chain) additional
include and library paths via the project property pages.  For GNU, you
add them to the GCC C Compiler -> Directories -> Include Paths.

I tried your test after adding ${ProjDirPath} (i.e. a build macro that
returns the project path) to the user specified include directories, and
I see the behavior that you want - i.e. that is, both funca and funcb
are suggested.

Regards,
Leo

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ploett Norbert
Sent: Friday, July 22, 2005 3:03 AM
To: CDT General developers list.
Subject: [cdt-dev] "Managed Make projects treat the entire project as
asource folder." - still true?

Hello folks,
 
I found this sentence in the documentation, in 
 
"C/C++ Development User Guide" --> "Tasks" --> "Searching the CDT" -->
"Setting Source Folders"
 
in the first paragraph it says 
 
"Note that source folders can only be currently used with Standard Make
projects. Managed Make projects treat the entire project as a source
folder."

A simple test indicated the contrary:

- Create a managed make C project.
- Create a source folder and place a main.c source file with the main
function in it.
- Create a header "funca.h" in the source folder with a sample function
definition (void funca(char* str))
- Create a header "funcb.h" directly in the project, defining, say, void
funcb(char* str)
- In the main() function write func and then get content assist
(ctrl-space)

The list has a suggestion for funca, but not for funcb.
Should the above sentences be removed from the docs?

Thanks,


Norbert
_______________________________________________
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