User forums > Using Code::Blocks

About the include folder

<< < (2/3) > >>

Jenna:

--- Quote from: scarphin on November 08, 2010, 06:58:37 pm ---I mean the addition of the '#include'd files in the source to the header directory automatically. But never mind I guess it's just a silly idea.


--- End quote ---
You mean moving the files on harddisk ?

That's really a silly idea.
What shall happen with the sstem headers or third-party headers ?

If you mean to move newly created headers to a special directory, there should be no need to do so, C::B asks you for the full name (including the path) of the header to be created.

scarphin:
Sorry my bad! By 'header directory' I mean the 'header' listed near 'sources' on the 'management' window under the 'projects' tab not any actual directory. What I'm trying to say is to automate the process below:

--- Quote from: oBFusCATed on November 08, 2010, 02:59:08 pm ---You should add them to the project and if you've not messed with the extensions handling/virtual folders for the current project, they should show up in the "Headers" folder.

--- End quote ---

MortenMacFly:

--- Quote from: scarphin on November 08, 2010, 09:24:11 pm ---What I'm trying to say is to automate the process below:

--- Quote from: oBFusCATed on November 08, 2010, 02:59:08 pm ---You should add them to the project and if you've not messed with the extensions handling/virtual folders for the current project, they should show up in the "Headers" folder.

--- End quote ---

--- End quote ---
I still don't get it: What do you want to automise here? At some point you'll need to setup the include files. That is a single operation as described by oBFusCATed:

--- Quote from: oBFusCATed on November 08, 2010, 06:10:54 pm ---There is a way to add files recursively, what more do you want?

--- End quote ---
.
So you want to automise what is already a single operation?

scarphin:
I apologize for my English, I'm not a native English speaker. I'll try to explain in greater detail. Say I have the beginning of a source file like below:

--- Code: ---#include <inttypes.h>
#include <avr/io.h>
#include <avr/pgmspace.h>
#include "lcd.h"
--- End code ---
I've seen this in a commercial IDE with compiler integrated. When I hit the compile for the first time every file included (in this case inttypes.h, avr/io.h, avr/pgmspace.h, lcd.h) and the files they include inside them get listed under the 'header' title or related titles in a window similar to the 'management' window in codeblocks. So when I need to look up a function which resides in say 'lcd.h', I just double click the 'lcd.h' file under the 'header' title and it's opened in a new tab in the editor where currently in codeblocks I need to add the 'lcd.h' file to the project or load it manually to achieve the same result. That was something I found very practical at the time and just wanted to share with u devs in case u also might think it may be of use.
If I'm still unclear then just ignore what I said cuz I think codeblocks even in its current state is above many other software that can only be afforded with money!

oBFusCATed:
Have you tried to right click on "#include <someheader.h>", then open header 'someheader.h'?

Navigation

[0] Message Index

[#] Next page

[*] Previous page