| svn: Debug and Release under versioncontrol [message #156658] |
Sat, 22 October 2005 15:39  |
Eclipse User |
|
|
|
Originally posted by: v.thoma.htp-tel.de
Hi everyone,
I want the configurstion data from release and debug store under
versioncontrol by subversion.
I use Eclipse 3.1.1 under Linux, subclipse 0.9.34 (java-client) and the
subversion server 1.23.
Any idea ?
best regards
|
|
|
|
|
|
|
| Re: svn: Debug and Release under versioncontrol [message #158984 is a reply to message #158951] |
Fri, 25 November 2005 04:16  |
| Eclipse User |
|
|
|
Hi Toni,
you must distinguish between a project's build settings which describe
compiler, environment etc. for the build process and debug launch
configurations which describe the setup for debugging sessions.
The build configuration is stored it the project's base directory, in
..project, .cdtproject and (for managed make projects) .cdtbuild. They are
hidden in the C/C++ Projects View but visible in the Navigator view. Put
them under version control and you're done.
If you also want to share launch configurations, they are stored in the
metadata. I have not done this before, putting metadata under version
control is more tricky, since they also contain machine-specific and
user-specific settings so you do this at your own risk. The launch
configurations are stored as xml files in
<workspace>\.metadata\.plugins\org.eclipse.debug.core\.launches
Hope this helps
Norbert
"Toni Brkic" <tonib.brkic@switchcore.com> schrieb im Newsbeitrag
news:dm4j6g$4j4$1@news.eclipse.org...
> Kurt Dirix wrote:
>> Perhaps a stupid question, but why do you want your compile folder to be
>> stored into Subversion? These files should not be stored in a version
>> control system!
>>
>>
> I actually dont know which files I should put into version control.
> The thing I want to accomplish is that when I check out a project
> I dont have to manually setup project specific settings like,
> Environment variable, Make definitions, GDB info etc.
>
> But It doesnt seem to be possible in a simple way.
>
> /T
|
|
|
| Re: svn: Debug and Release under versioncontrol [message #159078 is a reply to message #158984] |
Sat, 26 November 2005 06:01 |
| Eclipse User |
|
|
|
Originally posted by: toni.brkic.switchcore.com
Norbert Ploett wrote:
> Hi Toni,
> you must distinguish between a project's build settings which describe
> compiler, environment etc. for the build process and debug launch
> configurations which describe the setup for debugging sessions.
> The build configuration is stored it the project's base directory, in
> ..project, .cdtproject and (for managed make projects) .cdtbuild. They are
> hidden in the C/C++ Projects View but visible in the Navigator view. Put
> them under version control and you're done.
I tried this but you get problems if you put .project under version
control.
Since the .project contains the name of the workspace. Then I get
problems, since eclipse will get quite confused if I change the name of
my workspace name and checkin the changes.
Use Case with .project under version control:
I check out project/trunk into workspace trunk. Work there for
a while. Then I realize that i need to do a minor fix check
out project/trunk into workspace trunk2. Do my fix and checkin.
If developer two checks project/trunk into workspace trunk. He
will have trouble since .project hase the name setting to trunk2.
I really cant understand how you smoothly work with the combination
eclipse/subversion/cdt.
If .project didnt have the name attribute or you could put a relative
path there things would be much easier. I dont understand why it
is in there at all. Arent you supposed to have a one .project per
workspace.
Does somebody use the combination eclipse/subversion/cdt explain
how they set up things so that it works in a team.
> If you also want to share launch configurations, they are stored in the
> metadata. I have not done this before, putting metadata under version
> control is more tricky, since they also contain machine-specific and
> user-specific settings so you do this at your own risk. The launch
> configurations are stored as xml files in
> <workspace>.metadata.pluginsorg.eclipse.debug.core.launches
> Hope this helps
> Norbert
> "Toni Brkic" <tonib.brkic@switchcore.com> schrieb im Newsbeitrag
> news:dm4j6g$4j4$1@news.eclipse.org...
>> Kurt Dirix wrote:
>>> Perhaps a stupid question, but why do you want your compile folder to be
>>> stored into Subversion? These files should not be stored in a version
>>> control system!
>>>
>>>
>> I actually dont know which files I should put into version control.
>> The thing I want to accomplish is that when I check out a project
>> I dont have to manually setup project specific settings like,
>> Environment variable, Make definitions, GDB info etc.
>>
>> But It doesnt seem to be possible in a simple way.
>>
>> /T
|
|
|
|
|
|
|
| Re: svn: Debug and Release under versioncontrol [message #159195 is a reply to message #159164] |
Mon, 28 November 2005 09:06 |
| Eclipse User |
|
|
|
Hi Toni,
so you are talking about the project name. Hmmm, you can't easily use the
same project content under differing names.
> Use Case with .project under version control:
> I check out project/trunk into workspace trunk. Work there for a while.
> Then I realize that i need to do a minor fix check
> out project/trunk into workspace trunk2. Do my fix and checkin.
Let me rewrite your usecase to the way I would do it:
- Check out the project from the repository as project to
..../workspace1/project
- Work there for a while
- For the minor fix, switch to a new workspace, e.g. .../workspace2 (or,
alternatively, start another instance of eclipse which uses workspace2).
- Check out the project again from the repository as project, now to
..../workspace2/project
- Do the fix and checkin.
And later, of course, merge the differences :-)
In short: Don't try to work on different versions of the same project in a
single workspace.
Hope this helps.
Norbert
|
|
|
|
|
| Re: svn: Debug and Release under versioncontrol [message #159333 is a reply to message #159302] |
Tue, 29 November 2005 10:15 |
| Eclipse User |
|
|
|
Originally posted by: tonib.brkic.switchcore.com
Ok, so the reason is that the project is already shared.
Thought the grand parent meant that with share you would
share the project info.
Thanks for the help in this thread. But I dont
know if I should report it as bugreport but I dont
think that the projectname should be in the .project file.
As of now I think that it doesn't work very good
when sharing a project with several developers.
You can get it workable with work-arounds but it
is quite cumbersome.
I would think that the goal should be that
a developer can check out the a project and press
build, run and debug without manually having to
do things.
/T
Norbert Ploett wrote:
> Toni,
>
> now that's strange. I do it with subversion and never saw "share project"
> greyed (unless the project was already shared, in which case there are all
> those other nice context menu entries under Team :-)).
>
> Guess I can't help you here.
>
>
> Norbert
>
> "Toni Brkic" <tonib.brkic@switchcore.com> schrieb im Newsbeitrag
> news:dmf30r$ul0$1@news.eclipse.org...
>> Norbert Ploett wrote:
>>> Hi Kurt,
>>>
>>> is there any reason why you don't, afer creating the project, simply use
>>> from the context menu Team -> Share Project?
>>> Since you are also checking in .project I do not see any difference.
>>>
>>>
>>> Norbert
>>>
>>>
>> I guess that is what I would like to use. But in my projct
>> this option is greyed out.
>> Doesn't it work with subversion?
>>
>> /T
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07933 seconds
Home