Fika-Tarkov/mods/Raid Review/user/mods/raid_review__0.3.0/node_modules/node-gyp/gyp/tools
Rage 404890ecbb Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
..
Xcode Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
emacs Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
README Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
graphviz.py Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
pretty_gyp.py Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
pretty_sln.py Adding Mods w/Symlink 2025-01-02 20:23:50 -05:00
pretty_vcproj.py Adding Mods w/Symlink 2025-01-02 20:23:50 -05: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)=" > original.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.