openharmony/windowmanager
1
0
Fork 0
mirror of https://github.com/openharmony/windowmanager.git synced 2026-06-30 21:47:58 -04:00
Code Issues Packages Projects Releases Wiki Activity

修复资料问题

Browse Source 
Signed-off-by: xingyanan <xingyanan2@huawei.com>
Change-Id: Ic87ce123b696a58fb7218d39775fbb54b65e3d4f
This commit is contained in:
xingyanan
2022-03-26 12:17:00 +08:00
parent a00c4405af
commit 557ab0cc01
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sa_profile/4606.xml
+5 -5
View File
@@ -16,12 +16,12 @@
<process>foundation</process>
<systemability> <!--Declare a system ability and its profile-->
<name>4606</name> <!--Declare the name of system ability-->
<libpath>libwms.z.so</libpath> <!--Declare the path of .so file which includes the system ability; Note: 1 .so file have 1 to N system abilities. -->
<!--<depend></depend>--> <!--Declare the name of system abilities which the system ability depends on,using the system ability would start on demand. -->
<libpath>libwms.z.so</libpath> <!--Declare the path of .so file which includes the system ability; Note: 1 .so file has 1 to N system abilities. -->
<!--<depend></depend>--> <!--Declare the system abilities on which a system ability depends. These abilities would start on demand. -->
<!--<depend-time-out></depend-time-out> --> <!-- Check all dependencies are available before the timeout period ended. The MAX_DEPENDENCY_TIMEOUT is 60s. -->
<run-on-create>true</run-on-create> <!-- "true" means the system ability would start immediately, "false" means the system ability would start on demand. -->
<distributed>false</distributed> <!-- "true" means the system ability supports distributed scheduling while "false" is not.-->
<dump-level>1</dump-level> <!-- Declare the dump level. 1-high; 2-media; 3-low -->
<run-on-create>true</run-on-create> <!-- "true" means the system ability starts immediately, and "false" means the system ability starts on demand. -->
<distributed>false</distributed> <!-- "true" means the system ability supports distributed scheduling, and "false" means the opposite.-->
<dump-level>1</dump-level> <!-- Declare the dump level. 1-high; 2-medium; 3-low -->
<bootphase>CoreStartPhase</bootphase>
</systemability>
</info>
sa_profile/4607.xml
+5 -5
View File
@@ -16,12 +16,12 @@
<process>foundation</process>
<systemability> <!--Declare a system ability and its profile-->
<name>4607</name> <!--Declare the name of system ability-->
<libpath>libwms.z.so</libpath> <!--Declare the path of .so file which includes the system ability; Note: 1 .so file have 1 to N system abilities. -->
<!--<depend></depend>--> <!--Declare the name of system abilities which the system ability depends on,using the system ability would start on demand. -->
<libpath>libwms.z.so</libpath> <!--Declare the path of .so file which includes the system ability; Note: 1 .so file has 1 to N system abilities. -->
<!--<depend></depend>--> <!--Declare the system abilities on which a system ability depends. These abilities would start on demand. -->
<!--<depend-time-out></depend-time-out> --> <!-- Check all dependencies are available before the timeout period ended. The MAX_DEPENDENCY_TIMEOUT is 60s. -->
<run-on-create>true</run-on-create> <!-- "true" means the system ability would start immediately, "false" means the system ability would start on demand. -->
<distributed>false</distributed> <!-- "true" means the system ability supports distributed scheduling while "false" is not.-->
<dump-level>1</dump-level> <!-- Declare the dump level. 1-high; 2-media; 3-low -->
<run-on-create>true</run-on-create> <!-- "true" means the system ability starts immediately, and "false" means the system ability starts on demand. -->
<distributed>false</distributed> <!-- "true" means the system ability supports distributed scheduling, and "false" means the opposite.-->
<dump-level>1</dump-level> <!-- Declare the dump level. 1-high; 2-medium; 3-low -->
<bootphase>CoreStartPhase</bootphase>
</systemability>
</info>