User forums > Nightly builds

The 03 June 2012 build (8024) is out.

<< < (6/7) > >>

carra:
Hi again, I have had some unexpected behavior with relative directories under C::B and I wonder if I should consider this a bug in C::B project system??

* Project base folder: C:\Programacion\KTools\Sources\LogStream
* Output folder for objects:  ..\..\Objects  (i.e.: "C:\Programacion\KTools\Objects")
* 3 Files in project:
    - ..\..\Headers\General.hpp       (i.e.: "C:\Programacion\KTools\Headers\General.hpp")
    - ..\..\Headers\LogStream.hpp   (i.e.: "C:\Programacion\KTools\Headers\LogStream.hpp")
    - LogStream.cpp                     (i.e.: "C:\Programacion\KTools\Sources\LogStream\LogStream.cpp")

No matter what I try, instead of the intended Objects directory, my objwect files end up in the following directory:

"C:\Programacion\KTools\Objects\Sources\LogStream"

Seeing the resulting command line, it seems as if C::B is doing the following folder concatenation for some reason:

(1) In the Project Explorer, the source file appears listed as "Sources\LogStream\LogStream.cpp" (why all that route? it's in the project's base directory!!)

(2) What seems to be happening is:
"C:\Programacion\KTools\Objects" + "Sources\LogStream\LogStream.cpp" ==> "C:\Programacion\KTools\Objects\Sources\LogStream\LogStream.o"

carra:
OK, since the project file is very simple I thought I might post it here.
For simplicity, I have parameterized folders with an env var KTOOLS_FOLDER which in my case is: C:\Programacion\KTools


--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="LogStream" />
<Option pch_mode="2" />
<Option compiler="gcc" />
<Build>
<Target title="Release">
<Option output="$(KTOOLS_FOLDER)\Libraries\LogStream" prefix_auto="1" extension_auto="1" />
<Option working_dir="" />
<Option object_output="$(KTOOLS_FOLDER)\Objects" />
<Option type="2" />
<Option compiler="gcc" />
<Option createDefFile="1" />
<Compiler>
<Add option="-Wall" />
<Add option="-O2" />
</Compiler>
<Linker>
<Add option="-s" />
</Linker>
</Target>
</Build>
<Unit filename="..\..\Headers\General.hpp" />
<Unit filename="..\..\Headers\LogStream.hpp" />
<Unit filename="LogStream.cpp" />
<Extensions>
<code_completion />
<envvars />
<debugger />
<lib_finder disable_auto="1" />
</Extensions>
</Project>
</CodeBlocks_project_file>
--- End code ---

If I had to guess, I'd say that C::B is trying to set a "common base folder" for all the project files. As if it didn't properly support routes with "\.." in them.

saidus:
Hello.
Is there any ready to download package for windows (codeblocks-setup-10.05.8024.exe) with the current svn release.
Thank you .

gd_on:
may-be that one : http://forums.codeblocks.org/index.php/topic,13234.msg88948.html#msg88948

gd_on

carra:
It's curious... the problem I reported earlier with relative paths seems not to be present in nightly 7925. The very same project I posted produces the object in the correct folder. A regression?

Navigation

[0] Message Index

[#] Next page

[*] Previous page