| Using custom C compilers [message #1407350] |
Tue, 12 August 2014 11:57 |
 rogger rogger
Messages: 1
Registered: August 2014 |
Junior Member |
|
|
I am creating a plugin containing a toolchain having 2 paths:
PathA: C compiler, C Linker
PathB: C compiler, C Linker
PathA compiler should pick scen_*.c files
PathB compiler should pick master_*.c files
To achieve this. each compiler has defined inputType & outputType (using contentTypes)
However, even master_*.c files are built by PathA compiler.
I have added the relevant code snippet below; appreciate any pointers to help.
PathA:
<tool
command="gcc"
id="coolengine.nonnative.c.compiler"
isAbstract="false"
name="%Toolname.coolengine.nonnative.compiler.c"
outputFlag="-o">
<inputType
buildVariable="SCEN_C_SRCS"
id="coolengine.nonnative.c.compiler.input"
name="%Toolname.coolengine.nonnative.c.compiler.input"
primaryInput="true"
sourceContentType="com.eclipse.cdt.icelero.toolchain.cooleng.nonnativec.content">
</inputType>
....
</tool>
<content-type
base-type="org.eclipse.core.runtime.text"
file-extensions="c"
file-names="scen_*.c"
id="com.eclipse.cdt.icelero.toolchain.cooleng.nonnativec.content"
name="%Toolname.coolengine.nonnative.c.content"
priority="high">
</content-type>
PathB:
<tool
command="gcc"
id="master.nonnative.c.compiler"
isAbstract="false"
name="%Toolname.master.nonnative.compiler.c"
natureFilter="cnature"
outputFlag="-o">
<inputType
buildVariable="MASTER_C_SRCS"
id="master.nonnative.c.compiler.input"
name="%Toolname.master.nonnative.c.compiler.input"
primaryInput="true"
sourceContentType="com.eclipse.cdt.icelero.toolchain.master.nonnativec.content">
</inputType>
....
</tool>
<content-type
base-type="org.eclipse.core.runtime.text"
file-extensions="c"
file-names="master_*.c"
id="com.eclipse.cdt.icelero.toolchain.master.nonnativec.content"
name="%Toolname.master.nonnative.c.content"
priority="high">
</content-type>
|
|
|
Powered by
FUDForum. Page generated in 0.01381 seconds
] 
Search
Help
Register
Login
Home
