User forums > General (but related to Code::Blocks)

Feature Request: Linked Libraries in project tree

<< < (3/3)

Charon:
actually because of this thread i tried assigning files to different targets for the first time.

when i change the active target nothing in the project-tree changes :-/
(i am not sure if the tree is supposed to change, actually i didn't expect this)


to which target would dropped libraries be attached when the policy for the active target is "use project options only"? since you can't see this in the project-tree you run in the risk of invalidating all your others targets.

sorry if i sound too pessimistic. i acknowledge the usefulness of something like this. i just can't see how this should work :)

Markus

AngleWyrm:
When right-clicking on a project and select "Add Files...", the only question asked is "To which targets does this file belong?" No further details are asked when adding files to a project. Do libraries require additional information?

For drag-n-drop, the most useful would be to have a normal (left-mouse) drag automatically apply the dragged files to all targets. For the more specialized files (debug, platform-specific, etc) one could have a right-drag that would call up the file properties dialog on completion of the drag-n-drop operation.  Right-clicking a file is already in the current build, and brings up the properties, where the the build targets can be (de)selected.

kelo81:
Also take in mind that C::B supports several compilers, and each one has a different technology when dealing with libs; so how to adapt this architecture on a multiplatform-multicompiler-fullyportable-IDE ?  (the linker settings are part of every compiler plugin, and that structure shouldn't be modified).
In my opinion it's great as it is right now  :D

AngleWyrm:
The way things are:
1).Go to Settings->Compiler->Link and add general libraries
2).Go to Project->Build Options->Project and add libraries for the project
3).Select individual builds (debug, release, etc) and add libraries for each build

Then let's say several months go by and Microsoft releases a new version of DirectX SDK. Spend some quality time mousing around trying to remember where each linked library goes. Hint: At least three of those lists of included libraries will need to be updated.

I am willing to understand how things got to where they are now, but I wouldn't describe them as "great".

dmoore:
AngleWyrm - if you use custom/global variables you can minimize some of this hassle to the point that updating settings is pleasant. For bigger jobs you can always just regex/script the xml project files. I also think Mandrav has plans to offer project settings hooks to squirrel scripts (if he hasn't done so already)

That being said, I see no reason not to have multiple ways of doing things. Task #1: add option to show only files of a specific target in the project tree (seems like a generally useful feature). Task #2: show libraries in the tree. Quite a bit of work there and not something I imagine any of the core team will want to work on before the next release.

Navigation

[0] Message Index

[*] Previous page