I have been playing with Boost Build on simple projects for a while,&nbsp; I though I would have a go at porting an existing complex project which use a very strange Makefile to use boost build instead.<br><br>This is the problem,&nbsp; the project uses pre built dynamic libraries which are arranged like this:
<br><br>/$(src_root_path)/$(library_name)/include/<br><br>with the binaries arranged like this<br><br>/$(bin_root_path)/$(library_name)/$(lib_version)/ <br><br>This runs on a UNIX platform and the paths of the shared objects are hardcoded into the executable&nbsp; ( &lt;dll-paths&gt; true ? )
<br><br>At the moment I have got it working on one example by using this as a rule<br><br>lib monkey_biz : : &lt;name&gt;monkey_biz.6.5<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;search&gt;$(bin_root_path)/6.5/lib_debug<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;include&gt;$(src_root_path)/monkey_biz/src ;
<br><br>(the debug and release versions of the libraries are in separate places too, but I think I can handle that!)<br><br>and repeating for every library, and adding this as a target later on.&nbsp; Now while this functions, it is ugly and I know (hope?!) boost build can do better.
<br><br>What I would like to do is have a list of (module_name,&nbsp; module_version)&nbsp; ,&nbsp; pass each onto a function which than creates the target as above, so that the jamfile itself can be clear and simple.&nbsp;&nbsp; Trouble is I&#39;m not sure where to start.&nbsp; Do I need to create a generator, or a class or something else.
<br><br>Any help is appreciated.<br><br>Chris<br><br><br>