The org.eclipse.equinox.executable.feature project contains the native C code for the Equinox launcher executable and library and is therefore also a CDT project.
But the configuration currently is outdated and not usable:
https://github.com/eclipse-equinox/equinox/blob/9b933ab0e894778e518d9500e3566456de7a757e/features/org.eclipse.equinox.executable.feature/.cproject
I tried to update it but failed.
@jonahgraham, could you help with fixing that configuration?
Maybe @akurtakov is also interested?
Since this project has the native code for three platforms, Linux, macOS and Windows, it's probably not possible to have them all three in one .cproject configuration and automatically/implicitly activate the one of the current platform?
If that's the case, we could do it like it used to be for SWT and have one .cproject configuration for linux, one for macos and one for win32 and let e.g. the Oomph setup 'activate' the correct one.
For Windows I'm not even sure which toolchain to use best? MS Visual-Studio C compiler? MSYS2? or something else? Since the CLI also uses MSVC, I think it would also make sense to use that in the IDE, if reasonably possible?
For Linux and macOS the toolchains are probably clear?
The
org.eclipse.equinox.executable.featureproject contains the native C code for the Equinox launcher executable and library and is therefore also a CDT project.But the configuration currently is outdated and not usable:
https://github.com/eclipse-equinox/equinox/blob/9b933ab0e894778e518d9500e3566456de7a757e/features/org.eclipse.equinox.executable.feature/.cproject
I tried to update it but failed.
@jonahgraham, could you help with fixing that configuration?
Maybe @akurtakov is also interested?
Since this project has the native code for three platforms, Linux, macOS and Windows, it's probably not possible to have them all three in one
.cprojectconfiguration and automatically/implicitly activate the one of the current platform?If that's the case, we could do it like it used to be for SWT and have one .cproject configuration for
linux, one formacosand one forwin32and let e.g. the Oomph setup 'activate' the correct one.For Windows I'm not even sure which toolchain to use best? MS Visual-Studio C compiler? MSYS2? or something else? Since the CLI also uses MSVC, I think it would also make sense to use that in the IDE, if reasonably possible?
For Linux and macOS the toolchains are probably clear?