Commits on Jan 21, 2016

1. Publish debug file (PDB) of binding.node …

   To ensure proper debugging of problems of Windows,
   publish PDB debug file along with the binary.
   
   In order to keep paths to the source files clean apply
   the technique described by John Robbins in
   "PDB Files: what every developer must know"
   http://www.wintellect.com/devcenter/jrobbins/pdb-files-what-every-developer-must-know
   and build node-sass in the "S:\node_modules\node-sass"
   
   During debugging, source files can be referenced
   via the virtual "S:" drive.
   
   This allows users and developers to assign S: drive to the project
   root ("node_modules") and access source files without having to redefine
   source paths.
   
   Artifact names are generated in a nice, Lisp-styled functional PowerShell
   hidden in a YAML folded scalar!
   
   Add node 5 to the PR testing build.

   

   saper committed Jan 21, 2016
   8 Configuration menu

   • View commit details
   • Copy full SHA for 05d2d08
   • Browse repository at this point

   Copy the full SHA

   05d2d08 View commit details

   Browse the repository at this point in the history

2. Microsoft linker should generate checksum …

   Use /RELEASE option of LINK.EXE

   

   saper committed Jan 21, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for 36769d7
   • Browse repository at this point

   Copy the full SHA

   36769d7 View commit details

   Browse the repository at this point in the history

3. xcode_settings are for mac only …

   No need to wrap the section in a conditional

   

   saper committed Jan 21, 2016
   Configuration menu

   • View commit details
   • Copy full SHA for f37d9a5
   • Browse repository at this point

   Copy the full SHA

   f37d9a5 View commit details

   Browse the repository at this point in the history