Not sure I completely understand the question, but I think what you’re after is the -dx flag (i.e. set the debug output level to x)

To see what g++ is doing, you only need debug level 2 so when you run bjam, just add this -d2 somewhere on your command line.

Debug levels go up to 9 (in case you need to see what else is happening)…

 

Cheers,

K.

 


From: boost-build-bounces@lists.boost.org [mailto:boost-build-bounces@lists.boost.org] On Behalf Of
Sent: 05 May 2006 10:29
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] some questions about using bjam in my own project

 

Hi Phillip,

 

I have switched to use bjam v2 for my project building. It seems much easier and more mannals than v1. Thanks for your advice.

 

But do you know how to turn on the g++ command line when compiling cpp file like what make does? Even if the cpp file compiled successfully.

 

Thank

Budingc


> Date: Wed, 3 May 2006 08:18:25 -0400
> From: phil@apago.com
> To: boost-build@lists.boost.org
> Subject: Re: [Boost-build] some questions about using bjam in my own project
>
>  wrote:
> >
> > Hi, all,
> >
> > I want to use bjam in my own project, so I write the following Jamfiles:
> >
> >
> [deleted]
> >
> > Could someone tell me how to resolve it?
> >
> > And is there successful story that using bjam in other projects rather
> > than boost?
> >
>
> Unfortunately, I can't help you with that project, since I've never
> really used v1. You might want to look at v2, especially since boost
> 1.34 is going to use v2 instead of v1.
>
> I use v2 to build 9 programs (1 COM object and 2 Windows GUI programs)
> on Windows and 6 of them on AIX, Solaris, and Mac OS X. Together, they
> use about 2 dozen libraries (some ours, some third-party).
>
> Phillip
>

 


使用 MSN Messenger