[Boost-build] Problem with "built_tool" example

Subject: [Boost-build] Problem with "built_tool" example
From: Phillip Seaver (phil_at_[hidden])
Date: 2010-05-11 08:19:49

I noticed this with my own code that builds a tool then uses it.  With
MSVC, it uses both the .exe and the .pdb on the command line.  Here's
part of what "bjam -d2" in the "example/built_tool" directory:

> Jamfile</I:/tmp/bb_test/boost-build/example/built_tool/core>.tblgen
> core\bin\msvc-8.0\debug\threading-multi\a.c
>
>    
> I:\tmp\bb_test\boost-build\example\built_tool\tblgen\bin\msvc-8.0\debug\threading-multi\tblgen.exe
> I:\tmp\bb_test\boost-build\example\built_tool\tblgen\bin\msvc-8.0\debug\threading-multi\tblgen.pdb
> > core\bin\msvc-8.0\debug\threading-multi\a.c

It doesn't affect the example program, since tblgen.exe doesn't use
command-line arguments, but mine does.  As a work-around, I can just use
$(COMMAND[1]) instead of $(COMMAND) in the action, but I was wondering
if there was a cleaner way.

I tested with the latest nightly zip ("SVN Revision 61893   May 10
17:45:19 MSD 2010") but with my bjam executable, since I was having
problems building with the nightly.  I'll send a separate email about that.

Thanks,

Phillip