| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| Xcode/ | 12-May-2024 | - | 260 | 231 | ||
| emacs/ | 12-May-2024 | - | 2,575 | 2,476 | ||
| README | D | 12-May-2024 | 837 | 15 | 10 | |
| graphviz.py | D | 12-May-2024 | 2.9 KiB | 103 | 64 | |
| pretty_gyp.py | D | 12-May-2024 | 4.7 KiB | 158 | 107 | |
| pretty_sln.py | D | 12-May-2024 | 5 KiB | 172 | 117 | |
| pretty_vcproj.py | D | 12-May-2024 | 9.5 KiB | 338 | 217 |
README
1pretty_vcproj: 2 Usage: pretty_vcproj.py "c:\path\to\vcproj.vcproj" [key1=value1] [key2=value2] 3 4 They key/value pair are used to resolve vsprops name. 5 6 For example, if I want to diff the base.vcproj project: 7 8 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 9 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 10 11 And you can use your favorite diff tool to see the changes. 12 13 Note: In the case of base.vcproj, the original vcproj is one level up the generated one. 14 I suggest you do a search and replace for '"..\' and replace it with '"' in original.txt 15 before you perform the diff.