maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/tools/llvm-mt/single_file.test

30 lines
1020 B
Plaintext
Raw Normal View History

Implement parsing and writing of a single xml manifest file. Summary: Implement parsing and writing of a single xml manifest file. Subscribers: mgorny, llvm-commits, hiraditya Differential Revision: https://reviews.llvm.org/D35425 llvm-svn: 308679
2017-07-21 05:42:04 +08:00
REQUIRES: libxml2
UNSUPPORTED: windows
RUN: llvm-mt /manifest %p/Inputs/test_manifest.manifest /out:%t
Diffing against a file that is itself used in the test seems to be a bad idea, because it might get locked down and rendered unopenable. llvm-svn: 309142
2017-07-27 01:47:44 +08:00
RUN: FileCheck %s --input-file=%t
llvm-mt: Merge manifest namespaces. mt.exe performs a tree merge where certain element nodes are combined into one. This introduces the possibility of xml namespaces conflicting with each other. The original mt.exe has a hierarchy whereby certain namespace names can override others, and nodes that would then end up in ambigious namespaces have their namespaces explicitly defined. This namespace handles this merging process. llvm-svn: 311215
2017-08-19 08:37:41 +08:00
CHECK: <?xml version="1.0" encoding="UTF-8"?>
Diffing against a file that is itself used in the test seems to be a bad idea, because it might get locked down and rendered unopenable. llvm-svn: 309142
2017-07-27 01:47:44 +08:00
CHECK-NEXT: <assembly xmlns="urn:schemas-microsoft-com:asm.v1">
CHECK-NEXT: <trustInfo>
CHECK-NEXT: <security>
CHECK-NEXT: <requestedPrivileges>
CHECK-NEXT: <requestedExecutionLevel level="3" uiAccess="1"/>
CHECK-NEXT: </requestedPrivileges>
CHECK-NEXT: </security>
CHECK-NEXT: </trustInfo>
CHECK-NEXT: <dependency>
CHECK-NEXT: <dependentAssembly>
CHECK-NEXT: <assemblyIdentity program="displayDriver"/>
CHECK-NEXT: </dependentAssembly>
CHECK-NEXT: </dependency>
CHECK-NEXT: <compatibility>
CHECK-NEXT: <dependency>
CHECK-NEXT: <assemblyIdentity program="compatibilityCheck1"/>
CHECK-NEXT: </dependency>
CHECK-NEXT: <application>
CHECK-NEXT: <supportedOS Id="FooOS"/>
CHECK-NEXT: </application>
CHECK-NEXT: </compatibility>
CHECK-NEXT: </assembly>