User forums > Using Code::Blocks

Project tree and symlinks

<< < (2/3) > >>

mirai:
But C::B replaces them every time I save a project even if changes is not about files, but any other option in a project.
This leads to many problems at once.

1) can't tell if files in dereferenced paths in project tree are the same files I included in the project (looking at them in file manager which doesn't play around with symlinks).
2) I have to click the hell out of my mouse just to open that bloody tree of ../../../../.. (which shouldn't be there in the first place) just to get to my files.
3) can't tell if these files were initially included from these relative paths or if their paths were dereferenced by the C::B.
4) eventually I end up with all this garbage in a Makefile which immediately makes the latter unusable in any other environment where symlinks in project directory point to other places.

Finally, why in the world does C::B project manager interfere with the user's way of organizing workspaces? This is just plain wrong IMO.

mirai:
Up

jens, MortenMacFly, oBFusCATed, other C::B devs I don't know,

People, say something. This issue has to be solved.

Jenna:

--- Quote from: mirai on June 17, 2013, 08:15:53 pm ---Up

jens, MortenMacFly, oBFusCATed, other C::B devs I don't know,

People, say something. This issue has to be solved.

--- End quote ---
If it is so important fo you, the fastest way to get it fixed might be a working patch.

It's something dpecial for linux developers, not for windows devs, but my time (and power) is very limited at the moment, due to very much and often very long work (about 50 to 60 hours in the most week since march). It will most likely be less in one or two months.
And there is (of course) my family that always has precedence over my work on C::B.

mirai:
I know you all are busy... but, well, could you at least tell which part of C::B code could be responsible for processing project file paths?

And the issue might be not exactly Linux-specific. In Windows you can define NTFS-junctions to directories which work almost the same as symlinks in Linux, the only big difference that you cannot define an NTFS junction for a file while you can define a symlink to a file, linking directories works on both platforms. However, I haven't checked yet how a recent version of C::B deals with NTFS junctions.

MortenMacFly:

--- Quote from: mirai on June 18, 2013, 10:33:21 am ---I know you all are busy... but, well, could you at least tell which part of C::B code could be responsible for processing project file paths?

--- End quote ---
Start by looking into cbproject.cpp.

As for Windows: Here it works as expected, including junctions (hard links). For Linux I cannot tell - I am rarely working on that platform, especially since the last Ubuntu update screwed my VM (again).

Navigation

[0] Message Index

[#] Next page

[*] Previous page