Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
N Virtual Folders for one file.
Jenna:
Again:
I don't see, why it can not be done with a workspace, that contains several projects (libraries, exes, samples, whatever).
klaas.holwerda:
Well i did my best to explain it, don't know what to add to it to explain the problem. But i do think projects is not the solution for it :-(
One can have only one workspace open at the time i assume, and you want me to put in there all the projects flat.
So all the samples en libraries of wxWidgets and wxLua and Agg and wxArt2D etc. in there as projects. All targets in those packages will become projects.
For me a project should contains several targets, and i want to look at the files for each target as a group. And i don't want to see them split up in a tree of includes and a tree of sources. Even if they are on a disk like that. And i think that such a grouping mechanism is best done with virtual directories. What else is their use? To gather for each target its files and transfer it into a project, is i think not the right thing to do.
I really don't understand why there are virtual directories, if it is not for viewing files in a different structure from what is on the disk.
Jenna:
--- Quote from: klaas.holwerda on July 14, 2011, 05:55:36 pm ---I really don't understand why there are virtual directories, if it is not for viewing files in a different structure from what is on the disk.
--- End quote ---
That's exactly the cause why they are there.
But you can have a file one time in your project and not twice.
Using a workspace with several projects, that use virtual folders, in it would do exactly what you want, if I understand your intention correctly.
Only the naming would be different (workspace instead of project and project instead of target).
klaas.holwerda:
But I do see a file in the normal tree structure and in a virtual directory at the same time, it does not look impossible inside CB, only the project file does not understand it ??
Although in the interface I can indeed only move files, not copy a reference to a virtual folder.
Why there is this limitation on not being able to place the same file in two different virtual folders I don't get. It would make it possible to generate more views on the same set of files on the disc.
I think it would be a great feature :-)
The approach you suggests, is to make each target a project. I think that would indeed allow adding the same source files to N different projects. But does this not go against the idea of a project having several targets? Also, it would mean a completely different approach in Cmake. One needs to generate a bunch of project files. And all the projects files need to be loaded into CB. Like wxLua would need N projects files, same for wxArt2D etc.. And in the workspace I do not see which project comes from which package.
It is a flat list with no hierarchy.
Or should I generate a workspaces instead for each package?? Like for VC, Cmake generates a solution file (sln) containing projects (vcproj). And in Cmake they made include_ms_project statements, to include project files from somewhere else.
Like in de wxArt2D solution/workspace included statements for project from the wxDocview package.
include_external_msproject( docview ${wxart2d_BINARY_DIR}/../wxdocview/docview/src/docview.vcxproj )
I find it Ugly in VC, I hoped CB would be easier, one file for the whole package ;-)
Understand that wxLua and wxArt2D are two different sourceforge projects. You have to generate project files separately with Cmake. Still you want to use them combined in one workspace.
Anyway I better withdraw my patch to CMake using the virt dir approach. The suggested approach generating multiple project files I think I am not able to do :-(
--- Quote ---That's exactly the cause why they are there.
But you can have a file one time in your project and not twice.
Using a workspace with several projects, that use virtual folders, in it would do exactly what you want, if I understand your intention correctly.
Only the naming would be different (workspace instead of project and project instead of target).
--- End quote ---
Navigation
[0] Message Index
[*] Previous page
Go to full version