Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344218

Summary:	Enhance the configure command to allow added options from other plug-ins
Product:	[Tools] CDT	Reporter:	Corey Ashford <cjashfor>
Component:	cdt-autotools	Assignee:	Jeff Johnston <jjohnstn>
Status:	NEW ---	QA Contact:	Jeff Johnston <jjohnstn>
Severity:	enhancement
Priority:	P3	CC:	akurtakov, cdtdoug
Version:	8.1.0
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:

Description Corey Ashford

2011-04-28 18:57:47 EDT

Build Identifier: M20110210-1200

As the autotools feature works now, the options to the configure command can
be modified after the autotools project has been created.  However, there is
no mechanism by which another plug-in can provide additional options to the configure command.

This would be desirable for user's build environment that use gcc toolchains
that come from a non-standard directory, and more to the point, that aren't
necessarily on the user's search path (via the $PATH env. var.)


Reproducible: Always

Steps to Reproduce:
This is a fairly serious issue for us, since we are constructing an SDK which
includes the autotools feature, but uses an alternative GNU toolchain located
in directory that is not on most user's search path.

Comment 1 Corey Ashford

2011-04-28 19:06:49 EDT

I have developed an extension point that allows other plug-ins to contribute options to the configure command line.  The options provided would only be the initial values for the project, and the user could modify them if necessary through a new field in the Advanced options.

Due to legal reasons, I cannot yet post a patch for this because we are working on obtaining permission to contribute to the autotools project, but I would like to know if you think that adding this sort of extension point is the right way to go, or maybe you have some other long-term strategy in mind?