Mitch re-enabled a capability in changeset b1e7e65c842c to show users what modules are in and out of the build, at configure time.

Enabled modules = ['core', 'network', 'config-store', 'internet', 'propagation', 'point-to-point', 'csma', 'emu', 'bridge', 'tap-bridge', 'virtual-net-device', 'applications', 'nix-vector-routing', 'olsr', 'aodv', 'dsdv', 'click', 'openflow', 'mobility', 'wifi', 'netanim', 'stats', 'uan', 'spectrum', 'mesh', 'test', 'ns3tcp', 'ns3wifi', 'flow-monitor', 'wimax', 'lte', 'mpi', 'topology-read', 'energy', 'tools', 'visualizer']

However, doing this at configure time will not correctly display the implicit dependencies that will be picked up in the build; e.g.

./waf configure --enable-modules=mesh

yields:

Enabled modules = ['mesh']

This could be remedied by displaying the list of enabled modules at the end of the build process, but IIRC Mitch had this in a while ago but Gustavo removed it because of an Eclipse problem?

I'm wondering whether this could be remedied to show the list of actual modules built, either by doing something different at configure time to discover dependencies, or restoring this at the end of the build output.