Dependency targets

From: Thomas Witt (witt_at_[hidden])
Date: 2001-11-22 06:40:02

Hi,

Dependency targets (<lib>) seem to be restricted to the current project. 
Currently errors like the following are generated for dependencies from other 
projects. 

---
warning: rulename $(gGENERATOR_FUNCTION($(target-type))) expands to empty 
string
warning: rulename $(gGENERATOR_FUNCTION($(target-type))) expands to empty 
string
don't know how to make 
<..!systems!ifc!signal/libIfcSignal.a/gcc-stlport/debug/runtime-link-dynamic>libIfcSignal.a
don't know how to make 
<..!systems!boost!libs!regex!build/libboost_regex.a/gcc-stlport/debug/runtime-link-dynamic>libboost_regex.a
--
I think they could be a convenient way to add libs from other boost build 
managed projects like
exe a.out : 
main.cpp 
<lib>$(BOOST_ROOT)/libs/regex/build/libboost_regex$(SUFLIB)
: : ;
This way always the correct lib is selected without the user having to fiddle 
with the "neverending" path generated by the build system. Large projects 
might not like to introduce this tight coupling but its convenient for 
smaller ones.
Thomas
-- 
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover
voice: [phone] - 4273, fax: [phone]
http://www.ive.uni-hannover.de