Re: [cdt-dev] projects using multiple toolchains

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

I know this isn't going to be helpful, but it's issues like these that have driven me to do a new, much simpler build system. My hope is to make toolchain configuration automatic and seemless auto discovering as much as it can and minimizing the setup you need to do, especially if you're using an external build system like CMake or autoconf, etc.

In the short term, things like dealing with the missing LLVM plug-in seem to be bugs. Was there anything interesting in the log like an NPE? There might be some quick fixes we could do to avoid these issues.

On Mon, May 30, 2016 at 12:21 PM, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:

I know that it is not between RC3 and RC4 that these problems will be fixed, but I'm just curious if anyone else is concerned that multi-toolchains support is still weak.

This problem haunted me for years, and I saw little improvements.

Right now I'm building the CMSIS++ tests with multiple toolchains (clang/gcc, 32/64-bits, gcc5/gcc6, intel/arm, osx/linux, etc) and managing these multi-configurations projects is a nightmare.

For example I asked a friend to run the same tests on a different platform, and the first time he tried to open one of my multi-configuration projects he got no errors at all, but a totally empty project.

The culprit was the missing LLVM plug-in; without it none of the other existing configurations were visible.

Later on he tried to switch the toolchain from OS X GCC to Linux GCC, and the result was a totally broken project, the changed configuration was compromised, it was not possible to repair it.

And the list may probably grow.


Anyone else affected by these problems?

Regards,

Liviu

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev