did some experiment, I noticed already in the past the parsing (in the CB log tab) stopped at the same project in the workspace, it is not due to the fact it is a given Nth project, sicne other projects have been added to the workspace in front of the project where the parsing stopped upon.
First description of the workspace.
- one parser per workspace
- it contains 477 projects
- the log shows the pairs of AddProjectToParser/OnParserEnd, it show 76 pairs and then it ends with AddProjectToParser on the problematic project "FOO"
One thing to note about project FOO : it is a library project with only headers, so when building this project there's nothing to do.
Made this project FOO the active project in the workspace, that means it would become the first project to be parsed, the one which triggers the CreaterParser.
This does make a difference !!!
It is parsed and more projects (starting from the first one in the workspace are being added/parsed).
The results are better, but still extremely bad. Now 228 projects made it through the parsing step. Again it halts on project "BAR".
Special thing about this project "BAR" : it is a library project with only headers.
For further tests I made a workspace with 4 projects, one of them being "FOO" (it was the second one, and the first project being the active), in this case all did get parsed ...
EDIT : an 11 projects workspace containing FOO and BAR, all parsed ...