[cdt-dev] Toolchain updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] Toolchain updates

From: Mike Wrighton <mike.wrighton@xxxxxxxxxxxxxx>
Date: Mon, 18 May 2009 10:33:21 +0100
Delivered-to: cdt-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=MWL3LmizN8drsK26V4OCVI0c2EMwGFN/WSTtS6HnYM34LQfvwmDCXpCQP3ItoqThAu ggADuEkvj/oPkQ5cqNXOuVgR/G81V4AM4YghYZY2CzuyrsNEtbodd2nxhONLjZq663W9 25Vd60IKFG3QUdm59LyWcamMF5LmAtyIurn2E=
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

I was just wondering if there was a kind of migration API inside CDT
to update a project with a new toolchain? It's really just a new set
of include paths that I need - so being able to force a scan to pick
up new include paths on startup rather than storing them in the
workspace would be handy.

Mike

Follow-Ups:
- Re: [cdt-dev] Toolchain updates
  - From: James Blackburn

Prev by Date: [cdt-dev] Workspace wide include pathes
Next by Date: Re: [cdt-dev] Toolchain updates
Previous by thread: [cdt-dev] Workspace wide include pathes
Next by thread: Re: [cdt-dev] Toolchain updates
Index(es):
- Date
- Thread

Breadcrumbs