I couldn't get this to work:<br><br>alias vprocn : ../../import/tns-r/import/aaavproc/vprocn.o : &lt;hptns-arch&gt;tnsr ;<br><br>lib ioa :<br>&nbsp;&nbsp;&nbsp; db.c<br>&nbsp;&nbsp;&nbsp; vprocn<br>&nbsp;&nbsp;&nbsp; ;<br><br>/usr/bin/bash -i -c "bjam hptnsr3d"<br>/cygdrive/c/mse/proj/boost-build/build/generators.jam:918: in ensure-type from module generators<br>error: target { ../../import/tns-r/import/aaavproc/vprocn.o. } has no type<br>/cygdrive/c/mse/proj/boost-build/build/generators.jam:1138: in generators.construct from module generators<br>/cygdrive/c/mse/proj/boost-build/build/targets.jam:1329: in construct from module object(typed-target)@161<br>/cygdrive/c/mse/proj/boost-build/build/targets.jam:1175: in object(typed-target)@161.generate from module object(typed-target)@161<br>/cygdrive/c/mse/proj/boost-build/build/targets.jam:764: in generate-really from module object(main-target)@202<br>/cygdrive/c/mse/proj/boost-build/build/targets.jam:737: in
 object(main-target)@202.generate from module object(main-target)@202<br>/cygdrive/c/mse/proj/boost-build/build/targets.jam:252: in object(project-target)@154.generate from module object(project-target)@154<br>/cygdrive/c/mse/proj/boost-build/build-system.jam:291: in load from module build-system<br>/cygdrive/c/mse/proj/boost-build/kernel/modules.jam:261: in import from module modules<br>/cygdrive/c/mse/proj/boost-build/kernel/bootstrap.jam:121: in boost-build from module<br>/cygdrive/c/mse/proj/boost-build/boost-build.jam:1: in module scope from module<br><br><br>Is bjam thrown by the fact that there is no local C or C++ source file present for vprocn.o?<br><br>I arrived at a solution to this by adding a feature and rule logic to my toolset that allows a given Jamfile in a fairly complex project tree to include property &lt;hptns-prebuilt&gt;vproc for a given exe or lib target.&nbsp; (I don't want to have to cut and paste a bunch of conditional alias statements to every Jamfile for
 this.)&nbsp; Based on a rule invoked in the Jamroot (hptns.register-prebuilt) that associates different vproc objects with different variants (variables = architecture, runtime-link), the toolset  determines which specific vproc[x].o object to include in the link when it sees &lt;hptns-prebuilt&gt;vproc in the link properties.&nbsp; <br><br>If there's a more straightforward way I could have solved this, it would be good to know.<br><br>Best regards,<br>Mark<br><br><br><br><b><i>Vladimir Prus &lt;ghost@cs.msu.su&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><file><hptns-arch><file><br>Well, the <file> features only matter for 'lib' rule. You can use this:<br><br>  alias vprocn : import/tns-r/import/aaavproc/vprocn.o : <hptns-arch>tnsr ;<br>  alias vprocn : <br><br></hptns-arch></file></file></hptns-arch></file></blockquote><br>