I got to compile and I'm starting to debug it. The problem was that I was using "build.bat vc12 --debug" and in this case vcvarsall.bat complains about a missing argument. If I do "build.bat msvc --debug" it uses visual studio 2008 (vc9) which builds the b2.exe and the .PDB as expected. I'll tell you if I find anything interesting.


2014-03-22 14:45 GMT+01:00 Jose . <kasty.jose@gmail.com>:
The bug seems to be in the native implementation of GLOB, in bjam.exe. I would like to build the engine with msvc toolset in debug mode with .PDB symbols. How can I do that? Right now when linking bjam.exe we don't get a .PDB (with Jam0.exe we have it, but I guess that's the bootstrap process, a different animal, isn't it?).



2014-03-22 2:39 GMT+01:00 Steven Watanabe <watanabesj@gmail.com>:

AMDG

On 03/21/2014 05:45 PM, Jose . wrote:
> <snip>
> /C:/Jam/aaaa/b/c/file.txt  (see that "aaaa" is lower-case but "Jam" is not)
>
> I would understand that all characters are converted to lower-case for case
> insensitive matching, but some of them don't, which is weird. As I say, in
> small programs it seems to work ok, I only found it in bigger ones.
>

In theory, the underlying Jam functions normalize
paths to match the actual names in the filesystem.

> 2) This is probably worse: <install-source-root> doesn't seem to down-case
> before trying to match. Hence, the install rule results in this:
>
> common.copy C:\Jam\z\..\AaAa\b\c\file.txt
>
> when in fact it should look like this:
>
> common.copy C:\Jam\z\b\c\file.txt
>
>
> Any clue what happened and how to solve it? (at least problem 2)
>

You can hack it in path.relative-to (in util/path.jam)
by changing the comparison to $(split1[1]:L) = $(split2[1]:L).

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build