Add CMAKE_GENERATOR to schema scanner build

Command line configuration with MinGW on Windows was failing
in schemaScanner.cmake because the generator wasn't getting
passed through to the build of the scanner. This commit adds
the generator to the scanner build command and fixes #295.
Merge pull request #296 from jasondegraw/master

Add CMAKE_GENERATOR to schema scanner build
Python keywords are replaced by keyword_ (underscore), this fixes a few associated outputs to avoid invalid Python code
map special characters \x9 \xA \xD in EXPRESS literals to Python \t \n \r
update REPEAT / looping statement outputs
add simple support for logical XOR output, assumes parameters are already boolean types
fix some NameErrors due to ordering of the output classes / types
add simple sort to Linked_List implementation
first fix for Python MRO issue
Merge pull request #298 from cshorler/ap203e2_fixes

Ap203e2 fixes
Install schema headers in locations that match the build tree hierarchy, so include directives will work both with in-build-tree and installed stepcode layouts.
Need the NO_REGISTRY flag for the static version of this target as well.
Only set a property on lazy_test-static if it is present as a target.
Until we reach a final decision on what to do about the schema_scanner, handle the .exe case
Apply BRL-CAD change r58172 from tbrowder2 - correct grammar
Apply BRL-CAD change r58222 from tbrowder2 - added FIXME to warn of error with tightned standards
Apply BRL-CAD change r58523 from n_reed - include ios header for std::ios namespace; fixes 'symbol not found' in exp2cxx on os x
Apply BRL-CAD change r58740 from tbrowder2 - fix typo
Suppress CMake warning 26 - need to figure out the 'right' approach eventually, but for now this is needed with CMake 3.0
Apply BRL-CAD change r61065 - The insertion mechanism for the sortedMaster array performed very badly in the case where a large file has a batch of low-id-number entities towards the end of the file.  Tossing in std::map in place of that array avoids the bad corner case, but we may pay a performance penalty in other situations - depending on what the bottle necks are, this may be work revisiting.  For now, this seems to work well enough.