Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-04-02 01:03:36

On Thursday 31 January 2008 21:01:50 Gary Kratkin wrote:
> "Johan Nilsson" <r.johan.nilsson_at_[hidden]> wrote in message
> news:fnqfdu$2hr$
> >
> > "Gary Kratkin" <gary_at_[hidden]> skrev i meddelandet
> > news:fnp6ai$dhr$
> >> [I posted a similar message on boost.users without reply]
> >>
> >> I'm a bjam neophyte trying to generate .pdb files for the static library
> >> targets of a complete boost build. My idea was to pass -Fd in the
> >> relevant
> >> actions blocks, something like this:
> >
> > Did you try something like:
> >
> > bjam debug-symbols=on debug-store=database
> >
> > / Johan
> Thanks Johan,
> debug-store=database worked, where <debug-store>database didn't. That's an
> improvement.
> The problem remains that for static libs, /Fd isn't specified on the compile
> command. The result is a vc90.pdb placed in the directory from which the
> build command is executed. For DLL targets, when /DEBUG is specified the
> linker's default behavior is to create a PDB in the output directory as
> dll-base-name.pdb. For LIB targets the linker does no such thing, so it's
> necessary to create the PDB from the compiler with the correct name. My
> problem is figuring out the base name of the LIB target within the
> actions-compile blocks.

Is this question still unresolved? If yes, then figuring the base name of LIB
target, inside the 'archive' action, can be done as:


(returns filename + suffix, without path), or


returns just name, without path or suffix.

- Volodya

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at