[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-cvs-dev] Setting up shared multiplatform development environment


Mikael,
it seems to be impossible to do with Eclipse/CVS. I think CVS has only one facility to select which files to include in synchronization operations, it’s cvsignore. It’s not suitable for your case though.

I can tell you the way it's done in Eclipse itself since it contains platform dependent code. First of all the separation is made on the level of projects, not individual files. So, you have projects like org.eclipse.core.net, org.eclipse.core.net.win32.x86 and org.eclipse.core.net.linux.x86. This way you download common code and the one that corresponds to your platform but the decision is user made.

Regards
--------------------
Pawel Pogorzelski
Software Engineer
IBM SWG Krakow Lab, Poland

IBM Polska Sp. z o.o. oddzial w Krakowie
ul. Armii Krajowej 18
30-150 Krakow
tel. +48-12-628-9682

NIP: 526-030-07-24
Sad Rejonowy dla m.st.Warszawy, XIII Wydzial Gospodarczy KRS
KRS 0000012941, Kapital zakladowy: 33.000.000 PLN



"Mikael Hakman" <mhakman@xxxxxxxx>
Sent by: platform-cvs-dev-bounces@xxxxxxxxxxx

2009-02-26 11:28

Please respond to
"Eclipse CVS Integration developers list."        <platform-cvs-dev@xxxxxxxxxxx>

To
<platform-cvs-dev@xxxxxxxxxxx>
cc
Subject
[platform-cvs-dev] Setting up shared multiplatform development        environment





Hello,

I'm setting up shared multiplatform development environment. Eclipse/CVS
will be used on multiple platforms and clients to develop applications for
multiple platforms. I have difficult to figure out how to setup shared
projects. Perhaps you could help. Here is the situation.

A project consists of a number of platform independent and a few platform
dependent files. Platform dependent files consist of .project, .classpath,
.cproject etc. files and some other .java, .cpp etc. files. All files should
be versioned. When checked out (or updated) on platform A, only platform
independent and platform A files should appear (be updated) in the
workspace. The reverse should be done when checking in (committing). On
platform L only platform independent and platform L files should appear. On
platform W only platform independent and platform W files should be worked
on, etc. The set of platform independent files is the same across all
platforms (new files and directories may be added for all platforms). Sets
of platform dependent files may differ between platforms.

While setting up a project may be complex and take some time, checking out,
updating, and committing during normal development should be foolproof -
developers should focus on development, not on CVS issues.

Any help would be deeply appreciated.

/Mikael

_______________________________________________
platform-cvs-dev mailing list
platform-cvs-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-cvs-dev