User forums > Using Code::Blocks

C::B ignores object output path

<< < (2/2)

mirai:

--- Quote from: Pecan on December 18, 2018, 11:51:09 pm ---This problem appears to have been fixed in the nightlies.

--- End quote ---
I'm glad to hear that. Does this affect the path unrolling in the project manager?

Pecan:

--- Quote from: mirai on December 21, 2018, 11:23:34 pm ---
--- Quote from: Pecan on December 18, 2018, 11:51:09 pm ---This problem appears to have been fixed in the nightlies.

--- End quote ---
I'm glad to hear that. Does this affect the path unrolling in the project manager?

--- End quote ---

I found no references to unrolling symlinks in the project manager.

mirai:

--- Quote from: Pecan on December 23, 2018, 05:29:49 pm ---I found no references to unrolling symlinks in the project manager.

--- End quote ---
If you include in a project a directory which is a symlink to an upper level directory and then save this project, which path will be written to the project file? A path to the symlink or a path to a directory the symlink points to? In the old release 16.01 C::B was handling this the wrong way by substituting symlinks with their contents. Every time I update a project file by saving it I have to go and manually fix paths replacing ../../../<something> with just <something> as it should be in the first place.

oBFusCATed:
I doubt this has changed recently... I agree it is annoying...

Navigation

[0] Message Index

[*] Previous page