copy Cygwin Toolchain [message #999237] |
Fri, 11 January 2013 11:01  |
Eclipse User |
|
|
|
Hi,
I have an ancient (2.95) GCC version (cross-compiler) running under Cygwin that I would like to use from Eclipse/CDT (3.7.2/Indigo). It's installed in a different location, with it's own Cygwin DLL's and shell and other utils (vs the default C:/Cygwin).
Is there a straightforward way to simply copy the existing Cygwin toolchain definition and modify the paths to point to this other toolchain? I'm going through the Managed Build System Extensibility Document now, but I'm thinking it's way overkill... Ideally, I'd be able to just have it show up as another toolchain in existing projects, like the Cygwin, MinGW and Visual Studio toolchains do now.
Thanks,
Taz
|
|
|
|
|
Re: copy Cygwin Toolchain [message #1001163 is a reply to message #1000946] |
Wed, 16 January 2013 02:13  |
Eclipse User |
|
|
|
Hi,
I am not quite sure what are these switches used for, but we also using some tricks:
We use MinGW toolchain, but with a different compiler and linker. This compiler and linker also not dealing with the default options and switches, so we deselected or disabled all options for the compiler (GCC C Compiler) and for the linker (MinGW Linker) and use only the Other flag and Linker flag properties to define the switches that our compiler and linker is using.
We also defined Pre-build steps and Post-build steps under Project Properties->C/C+ Build->Settings->Build Steps.
In the pre-build phase (it is a bat file actually) we `prepare` our source in a way that the compiler can use them.
In the post-build (also a bat file) we `pack` the compiled and linked project in a way that our target hardware understands.
With these we let Eclipse handle the compile and link, and all other steps (pre- and post) are done with bat files.
Hope this helps.
|
|
|
Powered by
FUDForum. Page generated in 0.03576 seconds