GSDK-Hub V2.6 User Guide
Function Description
Log in
GSDK-Hub login and GDev Platform share the same account system, and both use Feishu/Lark to log in. If there is no corresponding account, please contact GDev Platform.
Link CPID
There are two types of CPID, one is the Nuverse studio, and the other is the application ID for accessing Nuverse services. Each Hub user must bind one, so that Nuverse data members can accurately obtain the Hub users, so as to achieve accurate push and upgrade communication.
Currently supported studio IDs include: Oasis, Youai, Mutong, 101, Jiangnan, Game Tech Center (for internal members of Game Tech Center). If your studio is not listed here, please contact Nuverse members.
Function list
Introduction
After the GSDK is transformed into components, it becomes a collection of functions. The information displayed in the function list is the list of core functions supported by GSDK. This information is the basic function of later version management and build management. In the function list, each function contains the following information.
| Column Name | Description | Additional Information |
|---|---|---|
| component name | component's name | |
| Component ID | Component Key, globally unique | |
| Platforms | Dual-Ended / Android / iOS / Windows | Some components exist, only single-ended. Such as Thanos |
| Region | General / Domestic / Overseas | |
| Starting version | Which GSDK version does the component exist from | |
| Deprecated version | From which GSDK version the component is deprecated | |
| Description | A brief description of the component |
Version List
Example
SDKbuild
Select the desired version from the version list to enter the SDK configuration generation page.
Sample Page
You can select the required components/modules by yourself, or click "Import Historical Configuration" to select the required component/module combination from the historical configurations.
There may be differences in the composition of the SDK between the historical version and the target version. You can compare the differences between versions and change the selected components/modules yourself.
After the component/module is selected, click "Generate build configuration", and the selected structure will be saved in the user record, which can be used to obtain the content of the SDK in the subsequent process.
Configuration list
Introduction
The configuration list records all configuration build records of the consumer. Each build record includes: GSDK version of the package body, region information, platform information, component collection, build time, and build-related operations.
For each configuration record, GSDK-Hub provides some management operations. as follows
- Delete: delete personal build records
- Notes: Add Notes information to the build record to facilitate recording memories
- build: For iOS/Unity, it is necessary to obtain the required dynamic library according to the information in real time.
- Download: For iOS/Unity, the package is on the CDN and can be downloaded locally
- Export: For iOS/Unity, export the download package to the specified location
- Detailed: view the standard DSL display of this record
- View Gradle configuration: For Android, according to the selected configuration, you will actually get a Gradle configuration suggestion file
Example
Supplementary instructions
The build of Android is to produce a configuration of the corresponding components, so the build delay is 0.
The build of iOS is to generate a dynamic library of corresponding components in real time, and it usually takes 2-10 minutes to wait
Unitybuild will produce a UnityPackage of the corresponding components in real time, and generally need to wait for 5-20 minutes
If the same build configuration has been recorded before, the cache will be reused, and the build delay is 0
Why is it a dynamic library?
- The dynamic library can be loaded on demand in the true sense, and the package size can be minimized.
- Thoroughly solve the symbol conflict problem.
- Technology: Does not affect the text section of the game app.
- GSDK symbol table manage in GGame Tech Center
Download after the build is complete
View Android gradle
You can copy the gradle and copy it to the game project
Engineering Records
Introduction
This function is mainly to record local projects for automatic integration of SDK. Each record includes: basic information of the project (project name, path), type (Xcode Project/Unity project), target (SDK needs to be integrated into the target of Xcode Project), etc.
For project records, GSDK-Hub provides some management operations. as follows
- Delete: delete project records (only delete records, will not affect the local project)
- Modify: modify the basic information of the project, Notes, etc.
- Integration: For iOS/Unity projects, select the self-build SDK for automatic integration
Example
Project list:
Select the SDK:
Start integration:
Setup
Account Settings
Display account information, you can log out
Cache Management
The SDK download/integration will be cached locally. In order to save space, the cache can be cleared here without affecting the integrated projects.
Update Management
You can view the latest GSDK-Hub version
Feedback
If you have any problems or have any suggestions for GSDK-Hub, welcome to feedback
Command Line Mode
GSDK-Hub supports command line mode, which can be used for automatic integration.
The windows version can be run directly on the command line after installation; the mac version needs to be installed before use:
At the same time, you need to ensure that GSDK-Hub has successfully logged in, and then you can execute the gsdkhub command on the terminal:
The current version supports two subcommands:
- pack: Build according to the DSL file and save it to the specified directory
- gradle: Generate gradle code snippets according to the DSL file and save them to the specified file
The DSL files in it can be exported from the GSDK-Hub GUI mode:
The exported DSL file can be distributed to other members of the project team and used in CLI mode. like:
build:
gsdkhub pack --dsl ~/Desktop/dsl.json --output .
** Generate gradle configuration: **
gsdkhub gradle --dsl ~/Desktop/dsl.json --output ./gradle.snippet
GSDK-PC build
GSDK Hub version 2.6.0 starts to support PC-side build
Unitybuild:
- Taking overseas 3.18.0.0 build as an example, click Generate build configuration (generally not supported for now)
- Check Windows support and select the PCSDK version number (for specific access version numbers, please consult TPMmembers)
- Select the normal version for overseas official packages; select the version with the suffix -steam for overseas steam channel packages
- Components are selected according to the actual needs of the project
- The build type is selected according to the actual project needs
- In the configuration list, build according to the generated configuration (build -> download -> export SDK)
Native build:
- Select the baseline version number: (Consult TPMmembers for the specific version number)
- bytedance defaults to the official channel package
- steam channel package select steam option
- Just export the SDK in the configuration list
