From f1d283e941680a97d74a2fb7f6bcdd9490efc394 Mon Sep 17 00:00:00 2001
From: nancy.liao <huihui.liao@greentest.com.cn>
Date: 周四, 29 5月 2025 18:14:27 +0800
Subject: [PATCH] 根据具体需求 修改了一个强制性的版本匹配,否则license返回结果不正确
---
doc/usage/issue-licenses.md | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/usage/issue-licenses.md b/doc/usage/issue-licenses.md
index 47dcc23..83a7347 100644
--- a/doc/usage/issue-licenses.md
+++ b/doc/usage/issue-licenses.md
@@ -39,10 +39,10 @@
Once you have the hardware identifier you can issue the command:
```
-cd projects/DEFAULT #(or whatever your project name is)
+cd projects/DEFAULT #(or whatever your `lcc-project` is)
lcc license issue --client-signature XXXX-XXXX-XXXX -o licenses/{license-file-name}.lic
```
-usually this command is issued in the host machine where you compiled `licensecc`
+to create the license file (usually this command is issued in the host machine where you compiled `licensecc`).
## Full set of options
A good way to start exploring available options is the command: `lcc license issue --help`
--
Gitblit v1.9.1