CN113220371A

CN113220371A - SDK access method, device, medium and electronic equipment

Info

Publication number: CN113220371A
Application number: CN202110592620.9A
Authority: CN
Inventors: 苗健; 裴子明
Original assignee: Beijing Youzhuju Network Technology Co Ltd
Current assignee: Beijing Youzhuju Network Technology Co Ltd
Priority date: 2021-05-28
Filing date: 2021-05-28
Publication date: 2021-08-06

Abstract

The present disclosure relates to an SDK access method, apparatus, medium, and electronic device, the method comprising: the method comprises the steps of obtaining an SDK package file, wherein the SDK package file comprises a script file and a plurality of SDK resource packages, and the script file is used for configuring a configuration file; determining a target SDK to be accessed corresponding to the SDK package file; decompressing the resource packet of the target SDK to obtain the resource file of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different; and configuring a configuration file according to the script file and the resource file of the target SDK so as to access the target SDK. Therefore, automatic configuration of related configuration files can be realized based on script files in the SDK package file, automatic access of the SDK is realized, high technical requirements for use of users are reduced, manual access workload can be effectively reduced, and accuracy of configuration file configuration is effectively guaranteed.

Description

SDK access method, device, medium and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to an SDK access method, apparatus, medium, and electronic device.

Background

With the Development of computer technology, in order to facilitate Software Development of developers, Software Development can be assisted by introducing a native SDK (Software Development Kit).

In the related art, in the software development process, if the function has a corresponding SDK, the SDK can be directly accessed without writing a code of the function. Normally, research and development personnel are required to manually access the SDK, and because the research and development personnel have limited contact and use on Android native codes and iOS native codes and configurations, the access to the Android native SDK and the iOS native SDK has higher technical requirements for the research and development personnel, and in the process, the problem that the SDK is introduced to an incorrect project directory position or configuration files are wrongly configured may occur, and in this case, a subsequently developed software package is not available.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

In a first aspect, the present disclosure provides an SDK access method, including:

the method comprises the steps of obtaining an SDK package file, wherein the SDK package file comprises a script file and a plurality of SDK resource packages, and the script file is used for configuring a configuration file;

determining a target SDK to be accessed corresponding to the SDK package file;

decompressing the resource packet of the target SDK to obtain resource files of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different;

and configuring a configuration file according to the script file and the resource file of the target SDK so as to access the target SDK.

In a second aspect, the present disclosure provides an SDK access apparatus, the apparatus comprising:

the system comprises an acquisition module, a configuration module and a management module, wherein the acquisition module is used for acquiring an SDK package file, the SDK package file comprises a script file and a plurality of SDK resource packages, and the script file is used for configuring a configuration file;

the first determining module is used for determining a target SDK to be accessed corresponding to the SDK package file;

the decompression module is used for decompressing the resource packet of the target SDK to obtain the resource files of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different;

and the first configuration module is used for configuring the configuration file according to the script file and the resource file of the target SDK so as to access the target SDK.

In a third aspect, the present disclosure provides a computer readable medium having stored thereon a computer program which, when executed by a processing apparatus, performs the steps of the method of the first aspect.

In a fourth aspect, the present disclosure provides an electronic device comprising:

a storage device having a computer program stored thereon;

processing means for executing the computer program in the storage means to carry out the steps of the method of the first aspect.

In the above technical solution, the SDK packet file is obtained, so that a target SDK to be accessed corresponding to the SDK packet file can be determined, then the resource packet of the target SDK is decompressed, the resource file of the target SDK is obtained, and then the configuration file can be configured according to the script file in the SDK packet file and the resource file of the target SDK, so as to access the target SDK. Therefore, by the technical scheme, automatic configuration of related configuration files can be realized based on script files in the SDK package files, automatic access of the SDK is realized, on one hand, a user does not need to analyze specific contents in the SDK, high technical requirements for use of the user are reduced, manual access workload can be effectively reduced, on the other hand, accuracy of configuration file configuration can be effectively guaranteed, the accessed SDK is prevented from being introduced to an incorrect directory position, effectiveness and usability of the accessed SDK are guaranteed, and support is provided for operation stability of a software package generated based on the accessed SDK. In addition, in the disclosure, the file directories corresponding to the resource files of different SDKs are different, so that possibility can be provided for accessing part of the SDKs, diversity and applicability of SDK access are ensured, and user experience is improved.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale. In the drawings:

fig. 1 is a flowchart of an SDK access method provided according to an embodiment of the present disclosure;

FIG. 2 is a schematic illustration of an import interface provided in accordance with an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a file directory provided in accordance with one embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a display interface provided in accordance with one embodiment of the present disclosure;

fig. 5 is a block diagram of an SDK access apparatus provided in accordance with an embodiment of the present disclosure;

FIG. 6 shows a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

Fig. 1 is a flowchart of an SDK access method according to an embodiment of the present disclosure, and as shown in fig. 1, the method includes:

in step 11, an SDK package file is obtained, where the SDK package file includes a script file and a plurality of resource packages of SDKs, and the script file is used to configure a configuration file.

The SDK package file may be a package file of an SDK meeting user requirements, that is, the package file contains SDKs required by a plurality of users.

In step 12, a target SDK to be accessed corresponding to the SDK package file is determined.

The SDK package file is generally generated according to the requirement of a certain partner of the development platform, and may be generated according to the requirement of a plurality of users in the partner. In a possible embodiment, all the SDKs in the SDK package file may be determined as the target SDK to be accessed, so that the accessed SDK may be directly applied when software development is performed on the subsequent SDKs based on access, which is convenient for users to use.

In another possible embodiment, the selected SDK from the SDK package file by the user may be determined as the target SDK in response to receiving a selection operation by the user. For example, an import interface may be displayed, in which all SDKs in the SDK package file may be displayed, as shown in fig. 2, all SDKs therein may be displayed. As described above, the SDKs in the SDK package file are generally generated according to the requirements of a plurality of users in the partner, and therefore, the user a can select the SDKs required by the user a, for example, the user a can select the Account SDK and the PaySDK to use the selected SDKs as the target SDKs; for another example, the user B may also select the SDK that he needs, such as selecting the Account SDK and PushSDK, to use the selected SDK as the target SDK. In this embodiment, different users can import the SDK according to their own needs, thereby avoiding resource waste. For files needing default import, a default selected mode can be adopted, such as files corresponding to the black solid frame in fig. 2, so that the operation of a user can be further saved.

In step 13, the resource packet of the target SDK is decompressed to obtain the resource file of the target SDK, where the file directories corresponding to the resource files of different SDKs are different.

After the target SDK is determined, the resource packet of the target SDK may be obtained from the SDK packet file, and then the resource packet may be decompressed according to the format of the resource packet, for example, the resource packet is in a zip format, and may be decompressed in an opening manner of a zip file, where the decompressing manner is a conventional manner in the art and is not described herein again.

It should be noted that, when decompressing the resource packet of the target SDK, it may be decompressed to a separate file directory for different SDKs, so that independence between different SDKs may be achieved.

In step 14, the configuration file is configured according to the script file and the resource file of the target SDK to access the target SDK.

The process of automatically configuring the configuration file can be realized by executing the script file, and the configuration file can be a configuration parameter necessary for accessing the target SDK, so that the configuration file can be automatically configured to realize direct application of the target SDK and realize access of the target SDK.

In one possible embodiment, the SDK package file is packaged by the development platform in the following manner:

and in response to receiving an SDK export request, respectively compressing the file directory of each SDK indicated in the export request to obtain a resource package corresponding to each SDK, wherein the resource file of each SDK is stored in the file directory under the preset directory of the development platform, and the file directories corresponding to the resource files of different SDKs are different.

The development platform may be a Unity platform, and a worker of the development platform may select a corresponding SDK to export according to a requirement of a partner, so as to trigger the SDK export request, where the export request may indicate the corresponding SDK.

The preset directory may be preset according to a requirement of the development platform, for example, when the Unity platform accesses an SDK under Android, and the unitsdk may be set as a preset directory, a script file may be set under the preset directory, for example, the script file is an lgpackagemanager.cs file shown in fig. 3, and a resource file of a plurality of SDKs may be stored under the preset directory. For example, a plurality of file directories may be created under the LightGameSDK directory, each file directory storing resource files of an SDK, as shown in fig. 3, and the resource files of an Account SDK may be stored under the file directory of an Account. The resource file of the Account SDK can comprise an aar file, a C # code for packaging Android native functions and the like, and the aar file is a binary archive file of an Android library project.

In the embodiment of the present disclosure, corresponding subdirectories may be respectively created under the file directory of an Account according to the requirement of the Unity platform, so as to store corresponding files in the subdirectories, for example, aar files may be stored under the subdirectory path of Account/plugs/Android, and C # codes may be stored under the subdirectory path of Account/plugs, so that the resource files of the SDK are stored under one file directory. The storage directory of the resource file can be set according to the requirements of the development platform in actual use, so that the development platform can acquire and access the resource file.

Correspondingly, if the SDKs indicated in the export request are Account SDKs, Pay SDKs, and Push SDKs, the Account file directory may be compressed, the obtained compressed packet may be used as a resource packet of the Account SDK, the Pay file directory may be compressed, the obtained compressed packet may be used as a resource packet of the Pay SDKs, the Push file directory may be compressed, and the obtained compressed packet may be used as a resource packet of the Push SDKs, thereby obtaining a resource packet corresponding to each SDK, and facilitating subsequent independent processing of each SDK.

And then, packaging the resource package and the script file corresponding to each SDK to obtain the SDK package file.

The resource package and the script file corresponding to the SDK may be packaged based on an export interface of the development platform to obtain an SDK package file, for example, the resource package and the script file may be packaged and exported based on a package export API provided by the Unity platform to obtain the SDK package file.

Therefore, by the technical scheme, the resource files of the SDK can be stored independently, so that when the corresponding package files are obtained, the resource files of each SDK can be compressed independently, data support is provided for independent processing of the SDK subsequently, meanwhile, the efficiency and accuracy of automatic packaging can be improved, and the usability of the SDK package files is ensured.

In one possible embodiment, an exemplary implementation of configuring the configuration file according to the script file and the resource file of the target SDK in step 14 is as follows, which may include:

and executing the script file to determine whether the resource file of the target SDK contains the configuration information corresponding to the target SDK.

The configuration information corresponding to the target SDK may be stored in the resource file in a backup information file manner. In this embodiment, the resource files of the target SDK may be sequentially accessed by executing the script file. For example, a file name or a storage path of the backup information file may be predetermined in the script file, and when the script file is executed, it may be determined whether a corresponding file exists by querying the file name or accessing the storage path, for example, the corresponding file name may be queried from the resource file, and if a file corresponding to the file name may be queried, it is determined that the resource file of the target SDK includes the configuration information corresponding to the target SDK, and the corresponding configuration information may be obtained from the queried file.

And then, under the condition that the resource file of the target SDK is determined to contain the configuration information corresponding to the target SDK, adding the configuration information into the configuration file corresponding to the configuration information.

There may be a plurality of configuration files, taking access to the SDK under the Android as an example, when the SDK is accessed, configuration may be correspondingly required to be performed on a strings. The configuration file that needs to be configured specifically may be determined according to the actual SDK, which is not limited in this disclosure.

In a possible embodiment, the configuration information of the target SDK in a plurality of configuration files is stored in the backup information file, for example, configuration information corresponding to different configuration files is identified by means of different tag annotations, for example, tag annotations may be added before and after the configuration information, and an intermediate part of the annotation contains parameter content to be configured, so that configuration information may be obtained from the backup file information based on the tag annotations, and a configuration file corresponding to the configuration information may be determined by the tag annotations. And copying and adding the configuration information into a corresponding configuration file to realize the automatic configuration of the configuration file.

In a possible embodiment, if the file corresponding to the file name is not queried, it indicates that the target SDK does not need to perform related configuration, and at this time, the target SDK may be directly skipped over to query the resource file of the next target SDK until the resource file of each target SDK is queried.

Therefore, according to the technical scheme, the relevant configuration of each target SDK can be sequentially inquired through executing the script file, when the configuration information of the target SDK is determined to exist, namely the target SDK needs to be configured, the configuration information can be added into the corresponding configuration file, and the automatic configuration of the configuration file is realized, so that the problem of path or parameter errors possibly caused by manual configuration can be avoided to a certain extent, the accuracy of the configuration file is ensured, and the validity and the stability of the accessed SDK application are ensured.

In a possible embodiment, an exemplary implementation manner of adding the configuration information to the configuration file corresponding to the configuration information is as follows, and the step may include:

determining whether a configuration file corresponding to the configuration information exists.

For example, a query may be made based on a file name of a configuration file to determine whether a configuration file corresponding to the configuration information exists. If the name of the configuration file corresponding to the determined configuration information is android manifest.

If the file is not inquired, the configuration file corresponding to the configuration information does not exist. In this case, if there is no configuration file corresponding to the configuration information, creating a configuration file corresponding to the configuration information according to a configuration file template in the SDK package file;

adding the configuration information to the created configuration file.

The SDK package file may include a configuration file module file directory, such as a Core directory shown in fig. 3, where the directory includes templates of various configuration files, that is, configuration files that do not include configuration information. Therefore, when the SDK is accessed, if the accessed engineering project does not include the relevant configuration file, the required configuration file can be directly obtained by copying according to the corresponding configuration file template, so that the configuration information is added to the created configuration file, and the automatic creation and configuration of the configuration file are realized.

It should be noted that, when adding the configuration information to the corresponding configuration file, the configuration information may be added in an overlay type addition manner, that is, if there is no configuration corresponding to the configuration information in the current configuration file, the configuration information is directly added to the configuration file; if the configuration corresponding to the configuration information exists in the current configuration file, the content corresponding to the configuration information in the configuration file needs to be deleted first, and then the configuration information is added to the configuration file. Therefore, the uniqueness and the real-time performance of the configuration information in the configuration file can be ensured, the configuration information in the configuration file is ensured to be the configuration information of the latest version, the matching between the accessed SDK and the configuration file is ensured, and the use requirements of users are met.

Therefore, by the technical scheme, automatic creation and configuration of the configuration file can be realized, the automatic processing level of the SDK access is further improved, the manual workload is saved, meanwhile, the error risk in the automatic configuration process of the configuration file is avoided, the completeness and the accuracy of the SDK access method are improved, and the user experience is further improved.

In an actual application scenario, the SDK requirements of the partner are not constant, for example, a certain game has access to an account function, an advertisement function, a push function, and a payment function, and each function is implemented by one SDK. Later, the requirement of the game changes, only one account function is needed, and the previous game software package contains excessive invalid SDKs. Based on this, the present disclosure also provides the following embodiments.

In a possible embodiment, the method further comprises:

and in response to receiving the deleting operation, deleting the file directory of the resource file of the SDK to be deleted corresponding to the deleting operation.

Following the example described above, after accessing the Account SDK and Pay SDK, the game software package generated based on the SDK comprises an account function and a payment function, and then when only the account function needs to be reserved due to the change of the game function, then the accessed Pay SDK can be selected to be deleted, as shown in fig. 4, the deletion operation can be triggered by clicking "Push-Remove", then the file directory corresponding to Pay can be deleted, so as to export the game software package again, the exported game software package will not contain the resource files of the Pay SDK, then the game software package may contain only the SDK it needs, thereby reducing invalid resources in the game software package, reducing the volume and resource occupation amount corresponding to the game software package, the running stability and efficiency of the game or the software are improved to a certain extent, the use scene is further widened, and the use experience of the user is improved.

In one possible embodiment, the method may further comprise:

and after deleting the file directory of the resource file of the SDK to be deleted, determining a target configuration file corresponding to the SDK to be deleted. The target configuration file is a configuration file configured when the SDK to be deleted is accessed, and as an example, the target configuration file may be determined by querying configuration information corresponding to the SDK to be deleted in the resource file of the SDK to be deleted, that is, each configuration file corresponding to the configuration information is used as the target configuration file. As another example, the configured configuration file may be recorded when the SDK is accessed, so that the target configuration file may be directly determined.

And deleting the configuration information corresponding to the SDK to be deleted in the target configuration file.

Therefore, according to the technical scheme, after the SDK is deleted, the relevant configuration corresponding to the SDK is deleted from the configuration file, so that on one hand, the matching between the SDK and the configuration file can be ensured, the invalid information of the generated software package is avoided, on the other hand, the influence of the configuration information of the deleted SDK on the operation of the software package is avoided, and the stability and the safety of the operation of the generated software package are ensured.

As described above, the needs of the partners may be constantly changing. In an application scenario, after a function SDK is deleted, the function SDK may need to be reapplied later. Based on the application scenario, the present disclosure also provides the following embodiments.

In one possible embodiment, the method may further comprise:

and creating a backup file corresponding to the resource file of each target SDK, wherein the file name of the backup file is not identifiable.

After the resource package of the target SDK is decompressed to obtain the resource file, the resource file may be copied and renamed to obtain a corresponding backup file, and the file name of the backup file is not recognizable, so that the backup file is not packaged into the software package, and the backup file does not affect the data resource in the software package generated based on the accessed SDK.

For example, a suffix character and the like that cannot be recognized by a development platform can be added to name the backup file when renaming the backup file, for example, for a Unity development platform, a suffix "-" name can be added after a file name of a resource file, so that not only can the matching between the resource file and the backup file be ensured, but also the resource file and the backup file can be distinguished, for example, Pay is the file name of the resource file, and Pay-is the file name of the corresponding backup file.

And then, in response to receiving the reduction operation, creating a new resource file corresponding to the SDK to be accessed according to the backup file corresponding to the resource file of the SDK to be accessed corresponding to the reduction operation.

The deletable and reducible SDKs can be displayed in the display interface through a menu, and then the user can select the SDK to be reduced through the display interface, as shown in fig. 4, when the user clicks "Pay-add-", the reduction operation can be triggered, and the SDK to be accessed corresponding to the reduction operation is the Pay SDK. As an example, a backup file Pay corresponding to the Pay SDK may be copied, the copied copy file is stored in a file directory corresponding to a resource file to be accessed to the SDK, and the copy file is renamed, for example, a file name of the copy file may be weighed and named as a recognizable name, and if an unrecognizable character in the recognizable name is deleted, a new resource file Pay is obtained.

The backup file and the corresponding resource file may be stored in the same file directory in parallel, or may be stored in another backup directory, and it is only necessary to ensure that the backup file can be accessed by the script file, which is not limited by the present disclosure.

And configuring a configuration file according to the script file and the new resource file so as to access the SDK to be accessed.

The manner of configuring the configuration file according to the script file and the new resource file is similar to the manner of configuring the configuration file according to the script file and the resource file of the target SDK, and is not described herein again.

Therefore, by the technical scheme, the deleted SDK can be restored by backing up the resource file to obtain the backup file. By setting the unidentifiable file name of the backup file, the local backup of the resource file of the SDK can be realized, the data resource of the software package generated based on the SDK can not be influenced, the dynamic access of the SDK is realized based on one SDK package file, the use requirement of a user is met, and the application range of the SDK access method is expanded.

The present disclosure also provides an SDK access apparatus, as shown in fig. 5, the apparatus 10 includes:

the acquiring module 100 is configured to acquire an SDK package file, where the SDK package file includes a script file and a plurality of resource packages of SDKs, and the script file is used to configure a configuration file;

a first determining module 200, configured to determine a target SDK to be accessed, corresponding to the SDK package file;

the decompression module 300 is configured to decompress the resource packet of the target SDK to obtain resource files of the target SDK, where file directories corresponding to resource files of different SDKs are different;

the first configuration module 400 is configured to configure a configuration file according to the script file and the resource file of the target SDK, so as to access the target SDK.

Optionally, the SDK package file is obtained by a development platform by packaging in the following manner:

in response to receiving an SDK export request, respectively compressing a file directory of each SDK indicated in the export request to obtain a resource package corresponding to each SDK, wherein the resource file of each SDK is stored in the file directory under a preset directory of the development platform, and the file directories corresponding to the resource files of different SDKs are different;

and packaging the resource package and the script file corresponding to each SDK to obtain the SDK package file.

Optionally, the first configuration module includes:

the execution submodule is used for executing the script file to determine whether the resource file of the target SDK contains the configuration information corresponding to the target SDK;

the first adding submodule is used for adding the configuration information into the configuration file corresponding to the configuration information under the condition that the resource file of the target SDK is determined to contain the configuration information corresponding to the target SDK.

Optionally, the first adding sub-module includes:

the first determining submodule is used for determining whether a configuration file corresponding to the configuration information exists or not;

the creating sub-module is used for creating a configuration file corresponding to the configuration information according to a configuration file template in the SDK package file under the condition that the configuration file corresponding to the configuration information does not exist;

and the second adding submodule is used for adding the configuration information to the created configuration file.

Optionally, the apparatus further comprises:

and the first deleting module is used for responding to the received deleting operation and deleting the file directory of the resource file of the SDK to be deleted corresponding to the deleting operation.

Optionally, the apparatus further comprises:

the first creating module is used for creating backup files corresponding to the resource files of each target SDK, wherein the file names of the backup files cannot be identified;

the second creating module is used for responding to the received restoring operation and creating a new resource file corresponding to the SDK to be accessed according to the backup file corresponding to the resource file of the SDK to be accessed corresponding to the restoring operation;

and the second configuration module is used for configuring the configuration file according to the script file and the new resource file so as to access the SDK to be accessed.

Optionally, the apparatus further comprises:

the second determining module is used for determining a target configuration file corresponding to the SDK to be deleted after deleting the file directory of the resource file of the SDK to be deleted;

and the second deleting module is used for deleting the configuration information corresponding to the SDK to be deleted in the target configuration file.

Referring now to FIG. 6, a block diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: the method comprises the steps of obtaining an SDK package file, wherein the SDK package file comprises a script file and a plurality of SDK resource packages, and the script file is used for configuring a configuration file; determining a target SDK to be accessed corresponding to the SDK package file; decompressing the resource packet of the target SDK to obtain resource files of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different; and configuring a configuration file according to the script file and the resource file of the target SDK so as to access the target SDK.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present disclosure may be implemented by software or hardware. The name of the module does not in some cases constitute a limitation to the module itself, and for example, the acquiring module may also be described as a "module that acquires an SDK package file".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Example 1 provides an SDK access method according to one or more embodiments of the present disclosure, wherein the method includes:

determining a target SDK to be accessed corresponding to the SDK package file;

Example 2 provides the method of example 1, wherein the SDK package file is packaged by a development platform in the following manner:

Example 3 provides the method of example 1, wherein the configuring a configuration file according to the script file and the resource file of the target SDK, according to one or more embodiments of the present disclosure, includes:

executing the script file to determine whether the resource file of the target SDK contains the configuration information corresponding to the target SDK;

and adding the configuration information to a configuration file corresponding to the configuration information under the condition that the resource file of the target SDK is determined to contain the configuration information corresponding to the target SDK.

Example 4 provides the method of example 3, wherein the adding the configuration information to a configuration file corresponding to the configuration information, according to one or more embodiments of the present disclosure, includes:

determining whether a configuration file corresponding to the configuration information exists;

if the configuration file corresponding to the configuration information does not exist, creating the configuration file corresponding to the configuration information according to a configuration file template in the SDK package file;

adding the configuration information to the created configuration file.

Example 5 provides the method of example 1, wherein the method further comprises:

Example 6 provides the method of example 5, wherein the method further comprises:

creating a backup file corresponding to the resource file of each target SDK, wherein the file name of the backup file cannot be identified;

in response to receiving a restoring operation, creating a new resource file corresponding to the SDK to be accessed according to a backup file corresponding to the resource file of the SDK to be accessed corresponding to the restoring operation;

Example 7 provides the method of example 5, wherein the method further comprises:

after deleting the file directory of the resource file of the SDK to be deleted, determining a target configuration file corresponding to the SDK to be deleted;

Example 8 provides an SDK access apparatus, according to one or more embodiments of the present disclosure, wherein the apparatus comprises:

and the configuration module is used for configuring the configuration file according to the script file and the resource file of the target SDK so as to access the target SDK.

Example 9 provides a computer readable medium having stored thereon a computer program that, when executed by a processing apparatus, performs the steps of the method of any of examples 1-7, in accordance with one or more embodiments of the present disclosure.

Example 10 provides, in accordance with one or more embodiments of the present disclosure, an electronic device comprising:

a storage device having a computer program stored thereon;

processing means for executing said computer program in said storage means to carry out the steps of the method of any of examples 1-7.

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims

1. a SDK access method, is characterized in that, described method comprises:

Obtain the SDK package file, wherein the SDK package file includes a script file and resource packages of multiple SDKs, and the script file is used to configure the configuration file;

Determine the target SDK to be accessed corresponding to the SDK package file;

Decompress the resource package of the target SDK to obtain the resource file of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different;

The configuration file is configured according to the script file and the resource file of the target SDK to access the target SDK.

2. method according to claim 1, is characterized in that, described SDK package file is packaged and obtained by development platform in the following manner:

In response to receiving the SDK export request, the file directory of each SDK indicated in the export request is respectively compressed, and a resource package corresponding to each SDK is obtained, wherein the resource file of each SDK is stored in the developer. In the file directory under the preset directory of the platform, the file directory corresponding to the resource files of different SDKs is different;

The resource package and script file corresponding to each of the SDK are packaged to obtain the SDK package file.

3. The method according to claim 1, wherein the configuration file is configured according to the script file and the resource file of the target SDK, comprising:

Execute the script file to determine whether the resource file of the target SDK contains the configuration information corresponding to the target SDK;

When it is determined that the resource file of the target SDK contains configuration information corresponding to the target SDK, the configuration information is added to the configuration file corresponding to the configuration information.

4. The method according to claim 3, wherein the adding the configuration information to a configuration file corresponding to the configuration information comprises:

If there is no configuration file corresponding to the configuration information, create a configuration file corresponding to the configuration information according to the configuration file template in the SDK package file;

The configuration information is added to the created configuration file.

5. The method according to claim 1, wherein the method further comprises:

In response to receiving the deletion operation, the file directory of the resource file of the SDK to be deleted corresponding to the deletion operation is deleted.

6. The method according to claim 5, wherein the method further comprises:

Create a backup file corresponding to the resource file of each of the target SDKs, wherein the file name of the backup file is not recognizable;

In response to receiving the restore operation, create a new resource file corresponding to the SDK to be accessed according to the backup file corresponding to the resource file of the SDK to be accessed corresponding to the restore operation;

The configuration file is configured according to the script file and the new resource file to access the SDK to be accessed.

7. The method according to claim 5, wherein the method further comprises:

After deleting the file directory of the resource file of the SDK to be deleted, determine the target configuration file corresponding to the SDK to be deleted;

Delete the configuration information corresponding to the SDK to be deleted in the target configuration file.

8. An SDK access device, wherein the device comprises:

an acquisition module for acquiring an SDK package file, wherein the SDK package file includes a script file and resource packages of multiple SDKs, and the script file is used to configure the configuration file;

a first determining module, configured to determine the target SDK to be accessed corresponding to the SDK package file;

a decompression module, configured to decompress the resource package of the target SDK to obtain the resource file of the target SDK, wherein the file directories corresponding to the resource files of different SDKs are different;

The first configuration module is configured to configure the configuration file according to the script file and the resource file of the target SDK, so as to access the target SDK.

9. A computer-readable medium on which a computer program is stored, characterized in that, when the program is executed by a processing device, the steps of the method according to any one of claims 1-7 are implemented.

10. An electronic device, comprising:

a storage device on which a computer program is stored;

A processing device, configured to execute the computer program in the storage device, to implement the steps of the method of any one of claims 1-7.