[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Re: Conflicts on .project and other such files: how to keep them installation-independent

From: Jens Seidel <jensseidel_at_users.sourceforge.net>
Date: Fri, 18 Jul 2008 14:19:02 +0200

On Fri, Jul 18, 2008 at 01:31:59PM +0200, Hendrik Maryns wrote:
> Jens Seidel schreef:
> >On Fri, Jul 18, 2008 at 12:15:05PM +0200, Hendrik Maryns wrote:
> >>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.

> >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.

In this case I would suggest to add the default linker (or compiler)
setting $(USER_FLAGS) to .cproject and let user define this
variable (outside Eclipse) ...

To be honest I did not even understand how to handle config options in
Eclipse properly. Common options such as for code formatting should be
reused by all contributers and I noticed indeed that Eclipse sometimes
writes files in .settings/. Nevertheless the info it writes are not the
important ones and are probably not handled in my Subversion repository ...


To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-07-18 14:25:27 CEST

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.