Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » Sub-project management?
Sub-project management? [message #168170] Sat, 15 April 2006 03:51 Go to next message
Eclipse UserFriend
Originally posted by: bob.nospam.org

Hi all, I am involved in a large cross-platform C++ based project. We are
actively looking for alternatives to our "vi-only" approach on Unix
platforms (we are currently using Visual Studio on windows and make on
unix).

It is a fairly large project divided into multiple dynamic libraries and a
main executable, all managed by our own set of makefiles. Due to the
complexity of the build process, we would like to keep it that way but
also to rely on a more consistent and powerfull IDE for editing, code
browsing and debugging.

I having a hard time trying to setup CDT so it has multiple "sub-projects"
(one for each library) with their individual make target (think it as the
visual studio Solution handling my multiple vcproj).

Any insights or experience to share?

Bob
Re: Sub-project management? [message #168177 is a reply to message #168170] Sat, 15 April 2006 10:35 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: shea08.eastlink.ca

Bob wrote:
> Hi all, I am involved in a large cross-platform C++ based project. We
> are actively looking for alternatives to our "vi-only" approach on Unix
> platforms (we are currently using Visual Studio on windows and make on
> unix).
>
> It is a fairly large project divided into multiple dynamic libraries and
> a main executable, all managed by our own set of makefiles. Due to the
> complexity of the build process, we would like to keep it that way but
> also to rely on a more consistent and powerfull IDE for editing, code
> browsing and debugging.
>
> I having a hard time trying to setup CDT so it has multiple
> "sub-projects" (one for each library) with their individual make target
> (think it as the visual studio Solution handling my multiple vcproj).
>
> Any insights or experience to share?
>
> Bob
>
>

Are you developing on multiple platforms? Or just building on multiple
platforms?

If you just need to build on non-ms platforms, then I think your current
approach is the best. There are good standalone gui debuggers for
non-ms platforms, just use one of those when you need to debug on a
non-ms platform. That should be enough for tweaking and testing your
non-ms platforms.

If you need to develop on both, then that is a different story.

~S
Re: Sub-project management? [message #168184 is a reply to message #168177] Sat, 15 April 2006 15:16 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: bob.nospam.org

Thanks for your answer, this is a good point. Actually, we have our "young
generation" of developpers who seems to be more comfortable with visual
studio while most of our senior developper are sticking to unix(vi+make).

They are using ddd or gdb but sometimes, they want to investigate more
integrated approach that would be available on linux, irix and solaris.

Bob
Re: Sub-project management? [message #168308 is a reply to message #168184] Mon, 17 April 2006 22:28 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: none.none.com

Here, I am answering to my own question. There is something I just
understood with Eclipse: we can have multiple workspace (simply load a
different one at the startup). So What I did, is simply create a standard
make project for each shared library plus one on the top for the
executable. That's it. Quite flexible actually.

Minor Problem:
--------------
- I see in my tree a bunch of files I don't want to see in my project tree
on UNIX (including our autmatically generated Makefiles, and windows
stuff's...)
- I am still working on the CVS integration

Bob
Re: Sub-project management? [message #168320 is a reply to message #168308] Tue, 18 April 2006 09:16 Go to previous message
Eclipse UserFriend
Originally posted by: thomas.stephens.gmail.com

Hi,
You probably don't need separate workspaces, just different projects in
the same workspace for each of the shared libraries that you want to
build plus one for the executable. The exception to this is if the root
directory for any of these projects is a parent directory of any of the
others. Eclipse won't let you have a project defined in a directory
that is contained in another project. At least in the same workspace,
I've never tried multiple workspaces. As long as each on is in a
separate directory tree there is no problem. My main project is a 3
shared libraries plus 4 executables that use those libraries. I use
standard make projects (we have our own in-house build system) and have
them all in the same workspace.

As for hiding files you don't want to see, that depends on which of the
tree views you are using (Navigator or C/C++ Projects). In both cases,
there are filters that you can apply. Just click on the menu icon (the
point down triangle) and select the Filters entry to get a list of
filters you can apply. The C/C++ Projects view's filters have more
options and allow you to create your own filename filters that you can
use to hide file types not covered by the defaults.

Hope that helps.

- Tom

Bob wrote:
> Here, I am answering to my own question. There is something I just
> understood with Eclipse: we can have multiple workspace (simply load a
> different one at the startup). So What I did, is simply create a
> standard make project for each shared library plus one on the top for
> the executable. That's it. Quite flexible actually.
>
> Minor Problem:
> --------------
> - I see in my tree a bunch of files I don't want to see in my project
> tree on UNIX (including our autmatically generated Makefiles, and
> windows stuff's...)
> - I am still working on the CVS integration
>
> Bob
>
Previous Topic:How to speed up the debugger?
Next Topic:CPU is not supported by selected debugger
Goto Forum:
  


Current Time: Mon Jul 21 21:48:20 EDT 2025

Powered by FUDForum. Page generated in 0.25170 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top