SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Topic started by: timur on June 02, 2011, 10:06:41 pm

Title: How do I get Slickedit to find my #include files?
Post by: timur on June 02, 2011, 10:06:41 pm
I'm using Slickedit to work on the Linux kernel, which keeps all header files in the include/ directory.  So if I want to include a header file, I need to make sure I don't specify the "include/" part.  That is:

#include <linux/string.h>

Includes the file include/linux/string.h

It seems to me that Slickedit understands the #include directive and wants to help me find header files, but that doesn't seem to work.  How do I tell it that all header files are under include/ ?

Searching the help files got me nowhere.
Title: Re: How do I get Slickedit to find my #include files?
Post by: jimlangrunner on June 03, 2011, 01:37:44 pm
I'm guessing here, but it rings a bell.

Under Project Properties, Directories tab.  In the includes, do you have /include/ ?  From there, it should find the includes you're working with.

I assume from your post that
Code: [Select]
#include </include/linux/string.h> is not permitted. What about
Code: [Select]
#include <./linux/string.h>?
Title: Re: How do I get Slickedit to find my #include files?
Post by: ScottW, VP of Dev on June 03, 2011, 01:42:24 pm
Sorry if this is an obtuse question, but what is the specific behavior you are after? Is this issue about completing your #include statement as you type or is it about tagging and navigation?
Title: Re: How do I get Slickedit to find my #include files?
Post by: timur on June 05, 2011, 01:31:49 am
I am under the impression that when I type in

#include <lin

That Slickedit can fill in the "ux" part for me and change that into

#include <linux/

Maybe I'm imagining things, but I could have sworn I was able to do this once.  It's a sort of "tab completion" for #include statements.
Title: Re: How do I get Slickedit to find my #include files?
Post by: Dennis on June 06, 2011, 06:40:31 pm
Document > C/C++ Options > Auto-Complete ...

Check your setting for "List include files after typing #include"

Jim is correct that the include paths it uses are based on the include directories configured for the current project, as well as the C++ compiler include directories.