Bug 710917 - Segfault while parsing a C file
Another update for the build system

- .gitignore
src/unistd.h is not on src directory anymore (windows version is on winbuild directory)

- doxywizard.pro.in
consistency 0bj -> ../../objects

- Doxygen.sln
build doxygen 64 bit debug too

- Doxygen.vcproj
Config was missing (cannot be automatic due to the fact that there are 2 rules in 1 file), see also Doxywizard.vcproj

- Doxywizard.vcproj
consistency in respect to directories
$(QTDIR)/mkspecs/msvc2005 -> $(QTDIR)/mkspecs/msvc2008
settings part was present for x64 but not for Win32 (x64 not necessary for doxywizard)
Config_dw was missing (cannot be automatic due to the fact that there are 2 rules in 1 file), see also Doxygen.vcproj

- Version.rules
version.py does not need any arguments

- doxyindexer.vcproj
consistency in respect to directories

- doxysearch.vcproj
consistency in respect to directories
Bug 711097 - Compiler warnings because char is unsigned on ARM/PPC: "comparison is always false"
Merge branch 'feature/build1' of https://github.com/albert-github/doxygen into albert-github-feature/build1
Undo changes to doxywizard.pro.in
Bug 711787 - Long initialization line in C stops doxygen
An extra "breakpoint" in the input string has been created in the form of a , (comma), so for initialization lines the line will be shorter and the , (comma) will be copied later on.
Space missing in error message.
the word 'in' and the vale of filesOption were concatenated
More template and context updates
Added compile support for Mavericks
Bug 711723 - Comment /**/ confuses doxygen
Bug 711639 - [PATCH] #include does not work with absolute paths
Bug 710998 - latex_count=5 is not enough
Merge pull request #53 from albert-github/feature/bug_711787

Bug 711787 - Long initialization line in C stops doxygen
Merge pull request #54 from albert-github/feature/space_in_err_msg

Space missing in error message.
Merge branch 'master' of github.com:doxygen/doxygen
Removed redundant backslashes in regexp pattern
Bug 711004 - Vertical bars cannot be sent straight to makeindex
Debug output for lexical analyzer

In case of error messages like:
    input buffer overflow, can't enlarge buffer because scanner uses REJECT
it is not always directly clear from which lexical analyzer (.l file) this problem comes.
This patch helps to find these problems and does the following things:
- when using the option -d lex with doxygen each time a lexical analyzer is called at the start a line like the following line will be given:
    Entering lexical analyzer: pre.l (for: ..../file.c)
  and at the end:
    Finished lexical analyzer: pre.l (for: ..../file.c)
- in case the lexical analyzer has been translated with the -d option of lex / flex the above mentioned lines will be given as part of the lexical analyzer output (to stderr) and look like:
    --entering lexical analyzer: pre.l (for: ..../file.c)
    --finished lexical analyzer: pre.l (for: ..../file.c)
Merge pull request #55 from albert-github/feature/debug_lex

Debug output for lexical analyzer
Debug output for lexical analyzer

The previous commit (pull request) was missing the debug output possibility for config.l and partial for doctokinizer.l.
The later is called on different places by means of the generic definition doctokinizerYYlex, which is declared by means of YY_DECL.
To be able to add the debug output the YY_DECL had to be redefined to be a new function and the new function, with the debug output possibility, has to be called through the original function name.