#1343 dunecontrol should limit its dependecy check when --[only|module]=<mod> to dependecies of mod
Metadata
Property | Value |
---|---|
Reported by | Markus Blatt (markus@dr-blatt.de) |
Reported at | Aug 27, 2013 18:37 |
Type | Bug Report |
Version | Git (pre2.4) [autotools] |
Operating System | Unspecified / All |
Description
Currently dunecontrol checks whether all the module dependencies of all dune.module files found can be fullfilled. This seems to be overeager to me and should be limited to the files of interest if --module or --only option is given.
Just noticed this again, because dune-pdelab has a new dependency (typetree) that I have not yet on my disc. Command dunecontrol --module=dune-istl all
complains:
./dune-common/bin/dunecontrol --opts=../opts/shared.opts --module=dune-istl all
--- going to build dune-common dune-istl ---
--- calling all for dune-common ---
--- calling vcsetup for dune-common ---
--> Updating Git pre-commit hook with newer version
--- calling autogen for dune-common ---
ERROR: could not find module dune-typetree,
module is also unknown to pkg-config.
Maybe you need to adjust PKG_CONFIG_PATH!
dune-typetree is required by dune-pdelab
--- Failed to build dune-common ---
Terminating dunecontrol due to previous errors!