Precompiled headers (PCH) support in Code::Blocks

[tiwag]

@Yiannis

i just updated some of my private projects to use CB's PCH-support and would like to know,
if there is some proposed way till now, to change the compiling sequence.

* all my projects where i have added PCH support, have the relevant header file precomp.h as last file in the project list

* when i do a Rebuild, all source files get compiled without PCH and at last the header precomp.h get's precompiled to precomp.h.gch :?

* i changed the "Priority Weight" Slider of the precomp.h to 100%, but it didn't change anything

* as last resort i edited the project file and put the precomp.h at the first position of project files, 
 but it didn't change anything

? is it somehow possible to create the .gch file BEFORE the source modules are compiled when i use Rebuild Project ?

thanks

[Urxae]

3.) i manually compiled the wxsheaders.h to wxsheaders.h.gch
because the wxSmith_2_6.cbp project file has not marked the wxsheaders.h to use it pre-compiled.

Why not just mark them as precompiled yourself? (and adjust priorities, see below)

(nice feature which Yiannis added into one of the very last CB commits, thanks to Yiannis btw. !!)
[...]
really nice !

I agree

@Yiannis

Not me, but I'll answer anyway

* when i do a Rebuild, all source files get compiled without PCH and at last the header precomp.h get's precompiled to precomp.h.gch :?

* i changed the "Priority Weight" Slider of the precomp.h to 100%, but it didn't change anything

* as last resort i edited the project file and put the precomp.h at the first position of project files, 
 but it didn't change anything

? is it somehow possible to create the .gch file BEFORE the source modules are compiled when i use Rebuild Project ?

You should set the "Priority Weight" slider to 0% (or anything below the other source files at least). This one had me confused also, but basically it works the other way around than you'd expect :shock:. Lower priority weight means compiled earlier.
If you have multiple precompiled headers, and one uses the other, make sure the used one's priority weight is lower than the using one.

But this is indeed a very cool feature . Thanks, Yiannis.

[tiwag]

...You should set the "Priority Weight" slider to 0% (or anything below the other source files at least). This one had me confused also, but basically it works the other way around than you'd expect :shock:. Lower priority weight means compiled earlier....

thanks Urxae for enlightening me !! it works as you told , even when i never expected it working this way ... ( i have to improve my logic  :? isn't it ?)

But this is indeed a very cool feature . Thanks, Yiannis.

indeed it is, again, thanks too !

as i know CB is the second IDE which is able to use GCC's PCH features
(the first one was Chinook, from where i looked how it works)

[tiwag]

3.) i manually compiled the wxsheaders.h to wxsheaders.h.gch
because the wxSmith_2_6.cbp project file has not marked the wxsheaders.h to use it pre-compiled.

Why not just mark them as precompiled yourself? (and adjust priorities, see below)

yes i did it that way, thanks again !

I only wanted to post my comment about, that the project file in CVS could be optimised for that specific feature too 

[mandrav]

* i changed the "Priority Weight" Slider of the precomp.h to 100%, but it didn't change anything

As pointed out by Urxae, priority should be less than the default (50). Possibly 0 to ensure that it's compiled first.
Is it actually displaying the percent (%) sign? Because that would be wrong. Priority is a number ranging from 0 to 100, with lowest number meaning higher priority...

[tiwag]

...Is it actually displaying the percent (%) sign?

no %  sign there ! everything is OK 

Priority is a number ranging from 0 to 100, with lowest number meaning higher priority...

somehow i intuitively thought - higher number - higher priority - but this is obviously too simple 
i understand now  , and it works as intended 


thanks to all for your rapid help, tips & tricks !

[mandrav]

I added an explanation string regarding the priority setting, in the file properties dialog.

[tiwag]

I added an explanation string regarding the priority setting, in the file properties dialog.

there is another bug in this dialog
the scale title shows here by me : "  0          0        100 "     instead of      " 0       50      100 "

edit:
i understand, the middle number is the actual set value.
i'm somewhat over-worked and tired today - sorry for my lot of stupid questions which i was posting today -

[mandrav]

I added an explanation string regarding the priority setting, in the file properties dialog.

there is another bug in this dialog
the scale title shows here by me : "  0          0        100 "     instead of      " 0       50      100 "

This appearence is windows-only so I can't verify it now. But from what I remember, the middle number is the actual setting so if you move the slider it will change too...

[tiwag]

... from what I remember, the middle number is the actual setting so if you move the slider it will change too...

maybe it would be a lot clearer, if the dialog would show

Code

" Priority:    high                    xx                 low  "
"                 |   |   |   |   |   |   |   |   |   |   |    "

and xx displays the number from 0 ... 100 according to the actual setting of the slider


edit:
btw Yiannis - which tool are you using for editing the xrc dialogs ?