User forums > Using Code::Blocks
Bug Report: [#18755] C::B hangs for 20 seconds while opening large project...
dmoore:
--- Quote from: jens on October 25, 2012, 09:09:55 am ---Here it is .
--- End quote ---
Ok, that resolves the broken links after saving a project to a new folder. Projects with relative build paths get built in different locations now, of course... Guessing this will also break builds when there a link libs specified on relative paths. (e.g. the ..\..\devel linker path that we use in CB), but it might be enough to warn the user if they change the project path that they will need to manually update these things?
Jenna:
--- Quote from: dmoore on October 25, 2012, 05:26:22 pm ---
--- Quote from: jens on October 25, 2012, 09:09:55 am ---Here it is .
--- End quote ---
Ok, that resolves the broken links after saving a project to a new folder. Projects with relative build paths get built in different locations now, of course... Guessing this will also break builds when there a link libs specified on relative paths. (e.g. the ..\..\devel linker path that we use in CB), but it might be enough to warn the user if they change the project path that they will need to manually update these things?
--- End quote ---
This surely breaks it, but trying to update each and any possible path will surely lead to other errors.
EDIT:
And as posted before, it is not related to the patch.
MortenMacFly:
--- Quote from: dmoore on October 25, 2012, 05:26:22 pm ---Projects with relative build paths get built in different locations now, of course...
--- End quote ---
BTW: It was always like that. In the past you were able to save the project file to different locations and the project file was updated accordingly. So yes, this breaks such things, but that would be the same for every IDE out there. And I think it should be pretty cleasr.
However, as also many Newbies use C::B - an AnnoyingDiaolg maybe worth a try...
Jenna:
What probably could be done in the Project SaveAs routine, is updating relative paths like workdir etc, but this would be ahidden magic, which can lead to broken projects as well as not doing this.
So an annoying dialog, before the project's new base-path is changed is the best thing.
MortenMacFly:
--- Quote from: jens on October 24, 2012, 09:25:06 am ---But what if the projectfile (*.cbp) has an UNC path ?
--- End quote ---
You mean if its on an UNC path? In that case, all files need to have absolute information and there is no common top-level path. But that doesn't matter, if all files have absolute path's... isn't it?
BTW: Testing the patch:
Unfortunately already the first trial fails miserably:
- create a project
- add a path on an UNC path
- file is immediately broken in project tree (although the "tree path" would be OK)
-> you cannot open/edit that file from the project tree.
(This I had just tried to fix in trunk recently...:-()
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version