hangar-tech/biofriction-wp-theme
hangar-tech
/
biofriction-wp-theme
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
biofriction-wp-theme/node_modules/node-gyp/gyp/tools
History
jorge-vitrubio a7910c81a8 moved to new repo 2021-10-26 14:18:09 +02:00
..
Xcode moved to new repo 2021-10-26 14:18:09 +02:00
emacs moved to new repo 2021-10-26 14:18:09 +02:00
README moved to new repo 2021-10-26 14:18:09 +02:00
graphviz.py moved to new repo 2021-10-26 14:18:09 +02:00
pretty_gyp.py moved to new repo 2021-10-26 14:18:09 +02:00
pretty_sln.py moved to new repo 2021-10-26 14:18:09 +02:00
pretty_vcproj.py moved to new repo 2021-10-26 14:18:09 +02:00

README 

pretty_vcproj:
  Usage: pretty_vcproj.py "c:\path\to\vcproj.vcproj" [key1=value1] [key2=value2]

  They key/value pair are used to resolve vsprops name.

  For example, if I want to diff the base.vcproj project:

  pretty_vcproj.py z:\dev\src-chrome\src\base\build\base.vcproj "$(SolutionDir)=z:\dev\src-chrome\src\chrome\\" "$(CHROMIUM_BUILD)=" "$(CHROME_BUILD_TYPE)=" > orignal.txt
  pretty_vcproj.py z:\dev\src-chrome\src\base\base_gyp.vcproj "$(SolutionDir)=z:\dev\src-chrome\src\chrome\\" "$(CHROMIUM_BUILD)=" "$(CHROME_BUILD_TYPE)=" > gyp.txt

  And you can use your favorite diff tool to see the changes.

  Note: In the case of base.vcproj, the original vcproj is one level up the generated one.
        I suggest you do a search and replace for '"..\' and replace it with '"' in original.txt
        before you perform the diff.