Jens Seidel schreef:
> On Fri, Jul 18, 2008 at 12:15:05PM +0200, Hendrik Maryns wrote:
>> In news://news.gmane.org:email@example.com I asked how to
>> keep .project files non-platform dependent. Nobody answered, so I ask
>> again. The reason is that I have some very inexperienced students
>> working on a project with me and they are totally confused with the
>> conflict resolving stuff. Worst of all: since they need slightly
>> different settings, it are always the .project and .cproject files which
>> differ. For now, I told them to just ignore those and always just mark
>> resolved, so they keep their own versions, but this also means they do
>> not pick up useful settings changes which would work on their system as
>> So once again: how do you handle this? Are there tricks to separate the
>> installation-dependent parts. Note that this even applies for different
>> flavors of Linux.
> I try to report moved stanzas in project files (see e.g. Eclipse bug
> reports #192690 and #239917) and I think the situation improved already.
Yes, that is a problem as well. Thanks for the bug.
> Nevertheless it is still far from being perfect and I often tend to
> ignore changes in .cproject and .project as well. If I really need to
> commit a change I first compare the old and new files and try to
> manually move line to reduce the diff size. It's no fun.
Same thing here.
> To obtain a slight system independence I use environment variables
> to refer to include and library paths such as $(CGAL_ROOT)/include.
I do this as well, but there I noticed that e.g. $JDK_HOME is defined on
openSUSE linux, but not on Ubuntu, so my colleague needs to use LIBS=-I…
in her make arguments.
Ask smart questions, get good answers:
Received on 2008-07-18 13:32:26 CEST