importing a project

[datax]

Andreas Pakulat wrote:
> On 06.01.07 17:32:39, datax wrote:
>   
>> Perhaps you could help me understand what goes on in parsing a project, 
>> that is, does the parser start with the Makefile and follow it through 
>> to sub-make files? What are the other considerations in KDevelop parsing 
>> a project and where can it go awry?
>>     
>
> As addition to the other post from me, I was just informed that there is
> a way to deactivate the C++ parser for a certain directory by putting a
> file called .kdev_ignore into that directory. This file needs to be in
> every directory you want to be ignored, it doesn't populate into any
> subdirectories of a ignored directory.
>
> Andreas
>
>   
Dear Andreas:

OK, I get that there are some variables that can change the personality 
of the parsing. Perhaps another thing might be happening also.

I tend to start KDevelop from the command line and I notice in the 
fedora core 6 install that there are menu items with arguments to 
KDevelop for different functionality.

Is there an argument to KDevelop that sets the parser in a fashion to 
reasonably handle C projects like u-boot and various kernel drivers. It 
would be nice to know there is a way to tell KDevelop from the command 
line without modifying all the subdirectories in a kernel-type of C project.

Charles