Shaun Jackman ([EMAIL PROTECTED]): > Keeping SWT and Eclipse in different source packages allows the two > packages to be maintained independently, which I think is a major > plus. For one, this allows SWT to be patched without having to rebuild > Eclipse and vice versa. An autoconf'ed SWT tarball that includes the > complete build script really would be ideal.
There's also a subtle difference between the SWT included with Eclipse and the standalone SWT. The Eclipse SWT .jar files are made as Eclipse plugins, with the .so files embedded in the jar to be extracted by osgi, and required to be in a certain location on the file system, etc. However, the source is the same, and Eclipse is robust enough that if you fix a bug in SWT it likely should be done for Eclipse too, and that there's already work done for compiling SWT as part of the Eclipse build process. -Billy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
