About project dependencies...

[thomas]

Well, it is quite obvious that you need the platform SDK - but even if you have it, you cannot build a plain normal Win32 app.

Ok, you can... but you have to start with a console app and change the project's type and do everything by hand. This cannot seriously be the way... :lol:

[mandrav]

Project dependencies inside workspaces implemented (rev.1499).

[MortenMacFly]

Project dependencies inside workspaces implemented (rev.1499).

Yiannis, this rocks again!!!
Within my workspace I've had to order the projects according to it's build dependencies. Then a "build workspace" made sure that the dependencies were right. Now I can do REAL dependency which allows me to put libs I don't change often at the bottom of the workspace... THANKS!!!

Morten.

Ps.: I (of course) tried it by now and (of course :lol:) it works!!!

[Michael]

Well, it is quite obvious that you need the platform SDK - but even if you have it, you cannot build a plain normal Win32 app.

Ok, you can... but you have to start with a console app and change the project's type and do everything by hand. This cannot seriously be the way... :lol:

Yes, you are right. It is not very serious and it would have been much better to add a Win32 GUI template directly .

If I remeber correctly there is a template for windows form (managed code)...but personally, I prefer C++ pure and simple .

Michael

[Michael]

Project dependencies inside workspaces implemented (rev.1499).

Cool . Thank you very much.

Michael

[killerbot]

supercool, but I just rebuilded, and I don't seem to find the menu entries for it.

[mandrav]

supercool, but I just rebuilded, and I don't seem to find the menu entries for it.

"Project->Properties->Project's dependencies"

[killerbot]

Thanks.

The active project is 'saved' in the workspace file.
I can imagine that people want to put the worspace file in a version control system. Maybe it's better not to store it in the workspace then, but in another worspace layout file or something like that ?

For example : workspace for CB, main project depends on all the other projects, but I could make one of those others active for  development purposes. When I close CB then (time to go home ..) it will say the workspace has changed and so on ...


Lieven

[MortenMacFly]

When I close CB then (time to go home ..) it will say the workspace has changed and so on ...

I do have my workspace under version control and I see no problem. I would like to store the project dependencies in it to have another user using it. If the workspace file is saved then normally (in my case) only the date changes. A (good ) version control system will detect that and not commit. If the project dependencies have changed then I normally want to provide these changes to the other users as well.

I have furthermore another workspace for my experiements which is the same as the "default" worspace plus aditional projects. Of course it would be nice if one workspace could include another workspace (and not only projects). Thus I could have my experiment workspace better seperated from the "default" workspace I provide to others. I would not require to update my experiment workspace if my "default" workspace changes.

Yiannis, how do you think about that? Is it worth a feature request?

Morten.

[killerbot]

Some ideas about future enhancements/requirements :

project X is dependent on project Y :
- which target (M$ style : debug build depends on the other debug builds, release on the other release builds ...)
           --> dependency requires same target names, otherwise depend on the default target, and if that one is not around ...
- specify by hand the target (table : project/targets) : selection by check boxes


What do you think ?

Lieven