How can configure CDT MBS to use different toolchains for different folders? [message #871636] |
Mon, 14 May 2012 15:34 |
camelia valuch Messages: 6 Registered: May 2012 |
Junior Member |
|
|
I am trying to create a custom toolchain using CDT's managed build system (version 7.0).
The only problem is that I need to use separate toolchains for different folders. One folder will be compiled using one compiler and another folder will be compiled with another one. The result will be linked together in the end into an executable thing.
I tried to use folderInfo to define a toolchain specific for every folder:
<folderInfo
exclude="true"
resourcePath="differentToolchain">
<toolChain
id="com.project.toolchain.toolChain5"
isAbstract="false">
<tool
command="build1"
commandLinePattern="${COMMAND}"
id="com.project.toolchain.tool4"
isAbstract="false">
<inputType
id="com.project.toolchain.inputType4"
sources="c">
</inputType>
<outputType
buildVariable="ELF_FILES"
id="com.project.toolchain.outputType3"
outputs="elf">
</outputType>
</tool>
</toolChain>
</folderInfo>
What I'm trying to achieve is have a toolchain for the whole project except for the given folder, where I want to apply the toolchain specified in the folderInfo tag. But in the current setup I have, the configuration toolchain gets applied to all folders including the one I excluded using folderInfo.
The tools (compiler actually) have as inputs all the .c files in the workspace.
Thanks!
|
|
|
Powered by
FUDForum. Page generated in 0.02705 seconds