Home » Language IDEs » C / C++ IDE (CDT) » Use of Non-GNU C compiler with CDT
| Use of Non-GNU C compiler with CDT [message #72958] |
Thu, 05 June 2003 22:09  |
Eclipse User |
|
|
|
Originally posted by: mraner.ptsc.com
Hi all,
my company is evaluating open source IDEs for our proprietary chain of C
development tools (compiler, assembler, linker, debugger, emulator,
loader, etc.) for an embedded microprocessor. Eclipse looks like a good
foundation for creating a graphical user interface for our command line
based tools.
Our tools are not based on GCC and have a number of processor-specific
options that we would like to control through the IDE.
The obvious approach to integrate our C tools with Eclipse seems to be
extending CDT. However, I was wondering what type of compiler adapter
mechanism CDT provides. I am looking for a way to integrate different C
compilers in a fashion similar to that used by the cpptasks package for
Ant, where a common uniform compiler interface is implemented by a variety
of different compiler adapters.
Can anybody tell me how this can be best handled with CDT? I would also
appreciate any other suggestions about the integration of a proprietary C
tool chain with Eclipse.
Thanks a lot!
Mirko Raner
Software Engineer
PTSC
San Diego, CA
|
|
|
| Re: Use of Non-GNU C compiler with CDT [message #73820 is a reply to message #72958] |
Thu, 12 June 2003 15:39  |
| Eclipse User |
|
|
|
Originally posted by: m_josenhans.web.de
Mirko,
Such issues are usually handled with Makefiles. They are cryptic,
however flexible.
Here is link to the Gnu Make manual:
http://www.gnu.org/manual/make-3.77/html_chapter/make_toc.ht ml
http://www.gnu.org/manual/make-3.77/html_chapter/make_9.html #SEC81
Assumed targets are arm and intel.
Define the goal options 'arm' and 'intel' in the Makefile
gmake arm
gamke intel
See http://www.gnu.org/manual/make-3.77/html_chapter/make_9.html #SEC83
To delete the files before switching compilers have another goal 'clean'
in the Makefile:
gmake clean:
See http://www.gnu.org/manual/make-3.77/html_chapter/make_2.html #SEC11
Variables are needed to store the compiler type goal:
See http://www.gnu.org/manual/make-3.77/html_chapter/make_6.html #SEC56
A condition is needed to switch between compilers based on compiler
vairable:
See http://www.gnu.org/manual/make-3.77/html_chapter/make_7.html #SEC70
ifeq ($(CompilerType),arm)
set compiler variable 'CC' to name of arm compiler
else
set compiler variable 'CC' to name of intel compiler
endif
Combinations can be used:
gmake clean arm
Cleans and compiles for the arm compiler.
I have currently no applicable Makefile example here.
Br,
Michael
PS:
Use 'make'or 'gmake' depending on your platform. Check with 'gmake -h'
that you are using gnu make and not another make variant.
In Windows gnu make is used together with the gnu c-compiler of Cygwin
(www.cygwin.com).
> Hi all,
>
> my company is evaluating open source IDEs for our proprietary chain of C
> development tools (compiler, assembler, linker, debugger, emulator,
> loader, etc.) for an embedded microprocessor. Eclipse looks like a good
> foundation for creating a graphical user interface for our command line
> based tools.
> Our tools are not based on GCC and have a number of processor-specific
> options that we would like to control through the IDE.
> The obvious approach to integrate our C tools with Eclipse seems to be
> extending CDT. However, I was wondering what type of compiler adapter
> mechanism CDT provides. I am looking for a way to integrate different C
> compilers in a fashion similar to that used by the cpptasks package for
> Ant, where a common uniform compiler interface is implemented by a
> variety
> of different compiler adapters.
>
> Can anybody tell me how this can be best handled with CDT? I would also
> appreciate any other suggestions about the integration of a proprietary C
> tool chain with Eclipse.
>
> Thanks a lot!
>
> Mirko Raner
> Software Engineer
> PTSC
> San Diego, CA
>
>
|
|
|
| Re: Use of Non-GNU C compiler with CDT [message #75866 is a reply to message #72958] |
Wed, 16 July 2003 14:15 |
| Eclipse User |
|
|
|
Originally posted by: dschaefe.ca.ibm.com
Unfortunately, our current compiler/toolchain integrations are limited to
what the user can do with the makefiles for their projects. For CDT 1.2, we
are working on a UI layer that should hopefully simplify the creation of
makefiles and we'll be providing an extensibility mechanism to allow
toolchains to be plugged into that process.
In a following release, we will be looking at ways of allowing compiler
venders to extend the CDT's built-in parser for any language variations
thier compiler supports.
If you have any ideas, please feel free to share them on the cdt-core-dev
mailing list.
Cheers,
Doug Schaefer
"Mirko Raner" <mraner@ptsc.com> wrote in message
news:bbof3l$sda$1@rogue.oti.com...
> Hi all,
>
> my company is evaluating open source IDEs for our proprietary chain of C
> development tools (compiler, assembler, linker, debugger, emulator,
> loader, etc.) for an embedded microprocessor. Eclipse looks like a good
> foundation for creating a graphical user interface for our command line
> based tools.
> Our tools are not based on GCC and have a number of processor-specific
> options that we would like to control through the IDE.
> The obvious approach to integrate our C tools with Eclipse seems to be
> extending CDT. However, I was wondering what type of compiler adapter
> mechanism CDT provides. I am looking for a way to integrate different C
> compilers in a fashion similar to that used by the cpptasks package for
> Ant, where a common uniform compiler interface is implemented by a variety
> of different compiler adapters.
>
> Can anybody tell me how this can be best handled with CDT? I would also
> appreciate any other suggestions about the integration of a proprietary C
> tool chain with Eclipse.
>
> Thanks a lot!
>
> Mirko Raner
> Software Engineer
> PTSC
> San Diego, CA
>
>
|
|
|
| Re: Use of Non-GNU C compiler with CDT [message #76286 is a reply to message #75866] |
Fri, 18 July 2003 17:22 |
 Henning Riedel
Messages: 310
Registered: July 2009 |
Senior Member |
|
|
Doug Schaefer wrote:
> Unfortunately, our current compiler/toolchain integrations are limited to
> what the user can do with the makefiles for their projects. For CDT 1.2, we
> are working on a UI layer that should hopefully simplify the creation of
> makefiles and we'll be providing an extensibility mechanism to allow
> toolchains to be plugged into that process.
>
> In a following release, we will be looking at ways of allowing compiler
> venders to extend the CDT's built-in parser for any language variations
> thier compiler supports.
>
> If you have any ideas, please feel free to share them on the cdt-core-dev
> mailing list.
While we are at the topic, I don't know, if that ever got read by the
proper developers.
http://bugs.eclipse.org/bugs/show_bug.cgi?id=37124
That had been some thoughts of myself about it.
And as I just have been thinking on my current work, is there some
tutorial on how to extend CDT i.e., I thought about a doxygen extension,
though how do I get on the current function and inserting into the
current file?
Do I have to write an Plugin, or do I have to write just some classes,
jar them up and add something to an plugin.xml file? I'm pretty new to
Eclipse internals and how to extend Eclipse by own code, so please
forgive me the question.
|
|
|
Goto Forum:
Current Time: Sat Jul 27 15:55:17 GMT 2024
Powered by FUDForum. Page generated in 0.03396 seconds |
] 
Search
Help
Register
Login
Home
