New issue 33 by petri.tu...@gmail.com: Test LLVM plug-in on Mac OS X
http://code.google.com/p/llvm4eclipsecdt/issues/detail?id=33
Who has access to Mac could test plug-in on Mac OS X.
I've tested it on Mac OS X, but I can't get it to work with GNU make
builds. When I try to create a project using any of the clang/llvm-gcc
toolchains I get an internal error at:
org.eclipse.cdt.managedbuilder.llvm.ui.LlvmIsToolChainSupported.isSupported()
I think it does not work with the internal builder either.
I am fairly sure the reason is same as in issue 38. The development version
is aimed for CDT 8.x.
I have created a temporary solution.
I created a new update site for CDT 7.x supported version. Feel free to
test this plug-in now and if you find any issues please write them down
here.
Thanks for the quick reply. Unfortunately, with the version from the CDT7
update site I get a java.lang.NullPointerException when I try to change the
toolchain to llvm or when I try to create a fresh project using any of the
llvm toolchains.
Ok, I will look into it tomorrow. Thanks for letting me know. I am sorry
that it doesn't work like it should yet because currently this is mainly a
one man side project. I am trying my best to fix things in a timely manner
though but the 'stable' milestone is around December or so and hopefully
integrated as a part of CDT by then. Just hoping everything goes like
planned.
I tested the plug-in successfully on Linux (Ubuntu 10.10) with Eclipse
3.6.2 (Helios) and CDT 7.0.2.
I don't have access to Mac system so all I can think of is that either LLVM
with Clang/LLVM-GCC is not installed correctly or there is something wrong
with plug-in's Mac specific toolchain definition configurations. I can ask
another developer who has a Mac if he would like to test it.
I can take a look
I can create a fresh project with 1.0.2.201104221620 without getting an
exception. However, if I go to the project properties, Tool chain editor,
uncheck 'Display compatible toolchains only', then select LLVM, I get
java.lang.NullPointerException
at
org.eclipse.cdt.managedbuilder.internal.tcmodification.ConfigurationModification.getBuilderCompatibilityStatus(ConfigurationModification.java:101)
at
org.eclipse.cdt.managedbuilder.ui.properties.ToolChainEditTab.showErrorMessage(ToolChainEditTab.java:232)
at
org.eclipse.cdt.managedbuilder.ui.properties.ToolChainEditTab.updateData(ToolChainEditTab.java:200)
at
org.eclipse.cdt.managedbuilder.ui.properties.ToolChainEditTab.modifyToolchain(ToolChainEditTab.java:569)
at
org.eclipse.cdt.managedbuilder.ui.properties.ToolChainEditTab.access$0(ToolChainEditTab.java:558)
at
org.eclipse.cdt.managedbuilder.ui.properties.ToolChainEditTab$1.widgetSelected(ToolChainEditTab.java:111)
at
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3783)
...
That is a known bug. Similar than Issue 1. It would be great to get fixed
but I have no idea what is the reason behind that error. It is probably
related to toolchain compatibility because if you select another toolchain
then the LLVM disappears from the list.