Re: [cdt-dev] MBS tool filtering based on directories?

[Enrico Ehrich <newsgroups@xxxxxxxxxx>]

Andrea,

I have a similar use case  for my projects (using two different arm 
controllers).
I think the best way is to set up 2 different projects and make a 
dependency between it.

So a have a "main" and a "sub" projects. In  the main project you use 
the generated sub-project elf-file to link with the main elf file.

This way works fine for me and you can still use the MBS. =)

ciao
Enrico

Andrea Michelotti wrote:
> Hi Doug,
> thank you for you fast reply.
> I don't know if I understood well what you mean, but I need to build a
> single elf image for a core that has inside a controller (ARM) and a
> DSP(Magic), both of them have their own compilers and generate elf
> linkable objects at the end of the chain there is the xx-elf-ld that
> links all the objects together. So I would like to show an unique
> configuration.
> I'm new using CDT/MBS and navigating the code of MBS it seemed to me
> that the tool selection is easily done by file extensions.
> I was wondering if it could be useful to add an extension in "input
> source type" to select tool sources also by using a dir entry name, to
> support splitting of sources of the same type on different tools.
> thanks
> best regards
> Andrea Michelotti
>
> On Mon, 2008-05-12 at 05:25 -0700, Schaefer, Doug wrote:
>   
> > I'd say the recommended way to do this is to have different build
> > configs with different tool chains, and exclude the directories you
> > don't want built from each of the configs. You can do that from the
> > properties on the folder.
> >
> > Any other ideas? Sounds like good information for the user docs...
> >
> > Doug. 
> >
> >     
> > > -----Original Message-----
> > > From: cdt-dev-bounces@xxxxxxxxxxx 
> > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrea Michelotti
> > > Sent: Monday, May 12, 2008 8:01 AM
> > > To: cdt-dev@xxxxxxxxxxx
> > > Subject: [cdt-dev] MBS tool filtering based on directories?
> > >
> > > Hi all,
> > > is there a straightforward method to build a toolchain that 
> > > selects tools by using directory name other than file extensions?
> > > I would like to build an unique compilation chain for two 
> > > different processors with their own C-compilers. I want to 
> > > keep the "natural"
> > > extension ".c" for C-sources. The "input" sources are kept 
> > > into two different target-directories and I would like to 
> > > select the right "tool"
> > > by using the directory name.
> > >
> > > thanks
> > > Regards
> > > Andrea Michelotti
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > >