I am working on a SWT project as part of a team. We continually break each other's construction environment because eclipse. Classpath file is checked in version control and we include separate SWT libraries for our machines.
Depending on who has done so, a classpath entry may be:
or
& lt; Classpathentry kind = "lib" path = "lib / swt / swt-carbon.jar" /> or
& lt; Classpathentry kind = "lib" path = "lib / swt / swt-gtk.jar" /> It appears that the libraries are mutually exclusive, that is, you can not include them once and SWT can bring it into work. So we have to filter them for any platform in any way ...
Anyone have any ideas on how to do this? My initial idea was to split it into "volunteer-swt" file (ignored by VCS), it automatically generates using the antioxidants and incorporates it into the main category, but it seems that eclipse division Does not support the .classpath file.
Our current work-place is, as long as we do not really change the dependency, it is to avoid doing a classpath, though it still means that many people have their own development environment It has to be cured every time. Classpath changes.
Any suggestion will be highly appreciated, unless it is "not to use eclipse" because it is not an option for this project :)
Eclipse lets you define the spacepace variables so that you can keep the .classpath, but each developer will configure its eclipse according to the platform. You can at least then make the version .classpath file. You have to change the directory structure where you store your SWT jar in something where the name of the jar does not change per platform. This menu can be found in: " Window-> Preferences-> Java-> Build Path "
SWTJARDIRECTORY / WIN32 / SWT.JAR Carbon / SWT. JAR GTK / SWT.JAR East.
SWT_PLATFORM = "SWTJARDIRECTORY / GTK", set by Developer in Eclipse . Classroom
SWT_PLATFORM / SWT.JAR 
Comments
Post a Comment