problem with "File/New/File..."

[nenin]

In some cases C::B creates new file in project with full path to file instead of relative. So, in file property fields "File name (absolute)" and "File name (relative)" are identical. As result, C::B generates really odd  build errors. It may be corrected by direct edit of project file snf temporary cured by deletion of the C:B config. Looks like it is an issue with global C:B configuration file. Any suggestions? 
OS: WinXP SP3.

[oBFusCATed]

CB version, please?

I've never seen this kind of behavior, but I'm running CB on linux, most of the time.

[nenin]

CB version, please?

I've never seen this kind of behavior, but I'm running CB on linux, most of the time.

both last releases, 8 & 10, and some  nightly builds.  At my work PC it occurs some times, but not really often- so I ignored it. But now it became really annoying on one PC, from v.8.02.  Migration to v.10 does not help. After some time in all more or less big projects (with sub-dirs) it appear. IMHO, glitches with build originated from ":\" in path, so under linux it may not be so explicit. For exact file it may be corrected by edit of the .sbp.   

[nenin]

This problem re-appears in C::B 20.03 on Win 10 64b.
In some projects new files always added with absolute path in "File name (relative)" property. What can be the source of such strange behavior?

[BlueHazzard]

can you provide a example project?
What kind of path are you using? Any non ascii characters?

[nenin]

I`ll try to reproduce it on dedicated project. Currently it is "production" project, it cannot be shared.
There are no spaces, non-ascii symbols in path, etc.
I suspect that the problem occurred after I included some already existing files from subfolder. Then, when I wished to make a new *.cpp file, wizard opened this subfolder, I walked from it level up, to the root folder of the project, and then it happened.

[BlueHazzard]

If you can reproduce this, please post a step by step list. Something like this:
1) Open codeblocks
2) Crete a new project
3) Add file XY by clicking Project->Add
ecc...

Thank you!

[nenin]

At that moment I cannot reproduce that, but I found two strange point in cbp:
1. In list of the virtual folders:

Code Select Expand


<Option virtualFolders="main/;static/" />

typical in projects it looks like

Code Select Expand


<Option virtualFolders="main/;static/;" />

2.  and Extensions:

Code Select Expand


<Extensions />

while it must be at least:

Code Select Expand


<Extensions>
<code_completion />
<envvars />
<debugger />
</Extensions>

No other deviations was found so far.
When  I tried to make "Save As" for this project, I  got all source files with full path, and mentioned above deviations was reproduced as well even if they were corrected manually.

[oBFusCATed]

Empty extensions is a "feature" of recent builds.

[nenin]

I found that on different computer it work fine on C::B 17 (on my main workstation- not works on both 17 & 20 with the same pattern).
Is there any place (registry, user profile folder...) where C::B can also store project options?

[oBFusCATed]

Nope. They are only stored in the project.
Have you compared full build logs for working and non working builds?
Are you sure there aren't differences in global compiler options?

[nenin]

Have you compared full build logs for working and non working builds?

It not related to build, it is situation, when C::B makes the wrong path to new file in project. I dont try even build it because compiler gone crazy when such path was offered. 

Are you sure there aren't differences in global compiler options?

This installation (which is working) is a clone from defected one from my workstation, ~1 month fresh,   including C::B profile and whole mingw. Nothing was changed in global scope.
I suspect that something wrong might be in default.conf, but cannot find anything.

[BlueHazzard]

Can you please exactly describe the failing steps and the outcome? I am not sure if i understand the issue...

If you can reproduce this, please post a step by step list. Something like this:
1) Open codeblocks
2) Crete a new project
3) Add file XY by clicking Project->Add
ecc...

Thank you!

[nenin]

Please find attached file with step-by_step explanation.

[BlueHazzard]

Thank You!
This explains the error perfectly... Now lets try how i can reproduce this...