> That may sound like a pretty bad answer though, and feels even worse > now that I'm typing it. I've been thinking that the correct answer is > to have SWT packages created from the full eclipse sources like > Michael's packages do, and then ideally we'll do a proper autoconf > framework for all of Eclipse. However, it now seems glaringly obvious > that I should probably just sit down and do an autoconf'ed source > .tar.gz of just SWT, since it would help both you and anyone else > wanting to do plain SWT packages, or compile SWT/GTK+ on other > architectures.
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. Cheers, Shaun
