Bug 1944 – feature request: ./waf configure detects invalid module

Bug 1944 - feature request: ./waf configure detects invalid module


Summary:	feature request: ./waf configure detects invalid module

Status:	NEW

Product:	ns-3
Classification:	Unclassified
Component:	build system
Version:	pre-release
Hardware:	PC Linux

Importance:	P5 enhancement
Assigned To:	Gustavo J. A. M. Carneiro

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-07-07 12:17 EDT by Tom Henderson
Modified:	2014-07-07 12:17 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tom Henderson 2014-07-07 12:17:09 EDT

when './waf configure --enable-modules" is provided with an invalid module name, the configuration succeeds,  but the build fails with a more cryptic error.  e.g.

./waf configure --enable-modules=invalidmodulename

// succeeds

./waf build
Waf: Entering directory `/path/to/ns-3-dev/build'
Could not find a task generator for the name 'ns3-invalidmodulename'

A user has requested that './waf configure' instead detect this and print out a more helpful error message.

maybe something that called get_tgen_by_name() for each module at the end of configure, and caught the exception with a helpful error message, would work.