| scons, svn [message #157438] |
Mon, 07 November 2005 16:05  |
Eclipse User |
|
|
|
I am currently struggling to get the CDT to play nicely with our
existing projects. It appears to make to the following assumptions:
I use make. Actually I use scons.
I use cvs. Actually I use svn.
I have got subclipse working, but it feels more like a workaround than a
feature. The cvs menu items are still there, but the svn items are less
prominent. For example, there is no "Checkout projects from SVN" under
File->New->Project, but the CVS option is there.
The same occurs with scons. I can get it to use scons instead of make,
but it feels like a hack and doesn't play nicely with the built in
indexer. The scons plugin is even worse.
At the end of the day, I feel like svn and scons are thorns in the side
of CDT, instead of welcomed alternatives.
To me, the CDT should see "source control" or "build tool" as generic
aspects of each project, and then support different implementations with
equal precedence, instead of the current system of a preferred version
sytem and a preferred build system.
This is a barrier to entry, how can we get around it? Where do such
discussions take place? Where is the CDT design documentation?
Regards,
Richard Brady
|
|
|
| Re: scons, svn [message #157470 is a reply to message #157438] |
Tue, 08 November 2005 15:31  |
| Eclipse User |
|
|
|
Originally posted by: markp.softlanding.com
Richard Brady wrote:
> I am currently struggling to get the CDT to play nicely with our
> existing projects. It appears to make to the following assumptions:
>
> I use make. Actually I use scons.
> I use cvs. Actually I use svn.
>
> I have got subclipse working, but it feels more like a workaround
> than a feature. The cvs menu items are still there, but the svn items
> are less prominent. For example, there is no "Checkout projects from
> SVN" under File->New->Project, but the CVS option is there.
>
> The same occurs with scons. I can get it to use scons instead of make,
> but it feels like a hack and doesn't play nicely with the built in
> indexer. The scons plugin is even worse.
>
> At the end of the day, I feel like svn and scons are thorns in the
> side of CDT, instead of welcomed alternatives.
>
> To me, the CDT should see "source control" or "build tool" as generic
> aspects of each project, and then support different implementations
> with equal precedence, instead of the current system of a preferred
> version sytem and a preferred build system.
>
> This is a barrier to entry, how can we get around it? Where do such
> discussions take place? Where is the CDT design documentation?
In the case of CVS vs. SVN this has nothing to do with CDT. Those are
just plugins, and they control what shows and doesn't show in the UI,
not CDT. You can use Customize Perspective to remove the CVS menu if
you do not want it there.
Subclipse doesn't provide a File -> New option. With Subclipse you
define a repository location, browse it and right-click to checkout a
project. Once checked out, the decorators and Team menu will be
populated for SVN.
Mark
|
|
|
Powered by
FUDForum. Page generated in 0.02951 seconds
Home