Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Creating an input file based on project references


I have got a new exported option type (currently called executables) which is successfully passing the executable file artifacts from one project to the next (the plumbing to achieve that was relatively significant). Now that I have the full set of executables in the 'final' project my tool needs further information about the structure of the workspace. Each executable may depend on one or more other executables and this is not encoded within the binaries.

So in addition to being able to access the artifacts (which gives me the ability to re-build when they change), I need this extra information.

Does that make sense?


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of James Blackburn
> Sent: 24 June 2010 15:08
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Creating an input file based on project references
> > Before running a tool I would like to write this file and then pass it
> as an
> > option to the tool.  The information needed to write the file will
> include
> > the project references and some details about the referenced projects.
> The
> > tool combines all the projects artifacts and produces a final binary.
> I take it the previous advice for extending the exports to include
> artifacts didn't work?
> James
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

Back to the top