User forums > General (but related to Code::Blocks)
Track lib changes ?
Kalith:
--- Quote from: oBFusCATed on September 10, 2010, 03:33:38 pm ---In your GUI mock up how would you choose multiple dependencies?
--- End quote ---
The right part of the dialog uses check boxes, so you can choose as many dependencies as you wish.
By the way, it could be the occasion to implement dependencies within a single project (as I've seen somewhere in the source code : it's in somebody's todo list).
I've had a quick glance at the project dependencies GUI source code and, as far as I can tel, it is all located in sdk/resources/project_deps.xrc, in an XML format I'm totally unfamiliar with. I'm afraid it would take me too much time to learn all this...
--- Quote from: MortenMacFly on September 10, 2010, 03:37:06 pm ---I still believe this is possible with what we already have on board. A combination of virtual targets, dependencies between projects in a workspace, the order of targets in a project, the declaration to a target OS and external dependencies is IMHO all you need.
--- End quote ---
I'm sorry, but I still fail to see how it would work in my situation (maybe because I don't fully understand what you mean, I'm not a native english speaker). Would you mind giving a small example ?
MortenMacFly:
--- Quote from: Kalith on September 10, 2010, 03:55:21 pm ---Would you mind giving a small example ?
--- End quote ---
What about setting up virtual targets e.g. WinRelease_OGRE and Win_ReleaseSFML etc.?
Kalith:
Well, specifying "OGRE" for the main project makes no sense because it cannot use anything else :)
And specifying "Win" or "Linux" for the GUI lib also makes no sense because the code is exactly the same regardless of the OS.
It can be done of course, but it seems more like a hack/trick to me. I'm developing a set of library and project that (I hope) will be used by other people, so I need the workspace to be as clear and clean as possible.
If it was only for me, I'd probably go for your solution though !
MortenMacFly:
--- Quote from: Kalith on September 10, 2010, 04:27:33 pm ---Well, specifying "OGRE" for the main project makes no sense because it cannot use anything else :)
--- End quote ---
Mmmmh... I still don't get it (it was a long day for me today...). Are you aware that you can do several virtual targets (VT's), not just one? All I am saying is that you create the VT just as you need it for the platform / library you want to compile. Then you add these VT's in all your projects and configure them to compile the relevant targets pr project as needed.
Of course selecting a wrong VT on a certain platform will fail, but if you do a plausible naming this should be clear.
In fact I have something similar. A library that can / should be compiled using three compilers, a core application who's content depends on the OS and several tools using the library that differ per platform. I was able to setup Virtual targets for every platform / combination that makes sense just fine.
For my understanding: Can you compile a list/table with the combinations you want to have?
Kalith:
--- Quote from: MortenMacFly on September 10, 2010, 05:23:18 pm ---Are you aware that you can do several virtual targets (VT's), not just one?
--- End quote ---
Yes of course ;)
--- Quote from: MortenMacFly on September 10, 2010, 05:23:18 pm ---For my understanding: Can you compile a list/table with the combinations you want to have?
--- End quote ---
I simplified the problem and got rid of redundancy, but here is basically what it looks like :
(the "other project" is secondary, and remains in a different workspace, so I don't care about it for now)
A solution would be to do like Ogre3D : use different project for different targets.
They have a Linux and a Windows workspace for example. But that would render C::B's target system almost useless.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version