Community
Participate
Working Groups
It's hard for a newbie to know how to compile SWT from CVS. They need to check it out, muck around with Eclipse to allow it to show .dot files, and then copy the correct .classpath* file to .classpath. It would be possible to include a custom builder in the project (backed by a simple ant script) that would check for the existence of the .classpath file and if it were absent would copy the one that is appropriate to the current window system. This would save newbies a lot of grief.
It's so crazy, it might just work!
The trick now is to get it to just run once when you first check out, or at least not spam my console all the time when I save stuff like an auto-builder does. <target name="copy.classpath" unless="haveclasspath"> <copy file=".classpath_${osgi.ws}" tofile=".classpath"/> <eclipse.refreshLocal resource="." depth="infinite"/> </target> <target name="setup.classpath"> <available file=".classpath" property="haveclasspath"/> <antcall target="copy.classpath"/> </target>
I committed a custom builder, plus an ant task to run it. However, the problem is that the console output spams you as you are developing, even if the task does nothing. I tried having an alternate .project file and subbing it in, but this seems to cause more problems. I'd really like to get this fix in, but I'm not sure how to do it.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
