| Re: [cdt-dev] RCP Debugger for Windows? |
|
Hi,
I'm a bit concerned about, how that discussion started and was going into strange directions from my point of view. GCC which you actually support currently is in my opinion not the problem. It's not only mingw and cygwin out there. I think, I stated this some time ago already, that e.g. at http://www.equation.com/servlet/equation.cmd?fa=fortran, they provide a GCC distribution of 32bit and 64bit for windows (even latest 5.1 versions and snapshots), and also include GDB and make. I guess, what your main problem is, is the build environment not being a UNIX shell like, but windows command prompt based. So, there is no rm -f *.o or similar things, but the internal builder will work quite nicely, and produce the same usable binaries, which can be debugged in CDT. Therefore, the most critical part here is actually, how to build the beast, not calling the tools or paths or debugging. The question is always, why you need a UNIX shell like environment on Windows, be it cygwin or mingw. Maybe we just need other build toolchains, that are more abstracting from the actual OS. e.g. scons or waf or cmake might be viable solution. But just keeping the UNIX like makefile based MBS build system is problematic. If you want to switch to VC++ support, is not an option for everybody. Where do you get the compiler from? Is it still distributed by Microsoft separately from Visual Studio in the SDK? I've heard, it's not included anymore, but I could be wrong. The other thing with VC++ is, that the compiler does e.g. not support C99. It's C90, maybe they'll put in some C11 in the near future. I'm not sure, if somebody downloads >500MB of community or express edition is then going to use Eclipse/CDT; my guess is, they are just using VS then. Regarding the Clang/LLVM, I wonder if they now start to support Windows or not. There have been releases of Clang/LLVM, where either there was no release for Windows, or it was missing major libraries (headers and libs), a point where I always rejected to even look at Clang/LLVM. Without the stdlib, how am I supposed to get a running binary. And then they provide maybe an major release of Clang/LLVM, but minor bugfixes do not provide a binary for windows, whatever the bugfix releases were about (the information is about lacking). Look into the 3.4, 3.5. A lot of users are not able to build the compiler themself, they want to install the update and that's it. That is like if you might use a Linux Fedora/Suse/Debian/Ubuntu.. or you use Gentoo. e.g. in my company (Automotive embedded software), we are thinking to change from VC++ based Cantata Unit testing to gcc-based unit testing. One thing is, that using Jenkins as CI tool, compiling the unit tests with gcc is much easier than with VC++ solutions. Our toolchain is currently based on makefiles, but we are changing to scons or similar environment. Regards, kessel Am 15.07.2015 um 18:31 schrieb Doug Schaefer:
|