sudden amnesia of linker?

[oBFusCATed]

PS: I would rather not like deleting cbproject.depend with my project open... maybe I'll set up a test project...

Why? Aren't you storing your project in a VCS (subversion,git,etc)?

The best thing to do is to try reproduce the problem with a simple console project. Then post the exact steps needed to reproduce it on another computer.

[frithjofh]

hi, and thanks for the interest...

actually I am using git as version control system...

but back to my observed c::b problem: did anyone else reproduce it on his/her machine?

regards

frithjof

[Jenna]

but back to my observed c::b problem: did anyone else reproduce it on his/her machine?

No.

Which settings do you use in the new class dialog ?
Which pch-settings do you have for your project ?

As written by oBFusCATed: a minimal test-project and exact steps (all settings in new class dialog) would be good.

[frithjofh]

Hi everybody,

I attached a zip with a minimal console test project. PCH settin is the default: PCH generatedalongside original header.

I have added two classes via the new class dialog. Settings of the dialog for both classes like in the attached jpg file screen shot.

After adding the first class, the compilation/linking failed. I closed the project and reopened it and it compiled/linked fine.

After adding the second class, compilation/linking failed. I attach the build log as fail_2.txt.

regards

frithjofh

[attachment deleted by admin]

[BlueHazzard]

i think i know what is going on...
this should fix the error...

greetings

[edit] a better patch would be, in the compiler plugin, witch prevents to add a empty patch to the command line.... at the moment i have no time, but later i could try to fix it...

[BlueHazzard]

I would prefer this patch...

[oBFusCATed]

BlueHazzard:
Are you able to reproduce the problem?
If so can you enlighten us about the steps needed to reproduce it?

[BlueHazzard]

To reproduce the bug, you have only to create a project and add a class with the class wizzard.
The options "Add path to Project", "Use relative Path", and "Header and implementation file shall be in the same folder"
and the folder should point to the main project directory.
The problem is, that the relative path to the project directory is nothing (or a empty string). And if we add a empty Include path, c::b produce the output with the empty -I flag.
My patch checks if the path to add to the include directories is empty, if so, reject it... (or should we add a "."?)

greetings

[Jenna]

I would prefer the "-I .", because it does what the wizard is told to do (add the reletive path).
@oBFusCATed: I can reproduce it now also, you have to uncheck "Explicitely add currently compiling file's directory to compilers search dir" in compiler options.

[oBFusCATed]

Great now you'll choose a way to fix it

[frithjofh]

thanks for the efforts and the fix. maybe I should mention, that this worked fine all the time in the past. the bug was introduced only some months ago...

thanks again

[BlueHazzard]

@frithjofh: you can remove the tick at "Add path to Project" and it should work, for the moment, until a fix is committed...

i think this patch should work...


greetings