directory structure

TWELITE SDK is prepared to store source code and other project files in a predetermined location based on the installation directory.
Directory names and file names, including the SDK installation directory, should be alphanumeric characters a-z A-Z 0-9 _ - and a period separating the extension . Do not include spaces, other special symbols, or multi-byte character strings (e.g., Japanese).
directory
content
.../MWSDK
The top-level directory of the TWELITE SDK.
.../MWSDK/ChipLib
Microcontoroller Library
.../MWSDK/License
Mono-Wireless Software Specification Agreement
.../MWSDK/MkFiles
makefile library
.../MWSDK/Tools
toolchain, programming tools, etc.
.../MWSDK/TWENET
TWELITE NET library
    .../????_libTWENET
libTWENETUtils souce codes
.../MWSDL/Wks_TWELITEE, Act_samples, Act_extras
workspace for apps, samples.
 Workspaces
The directory where the workspace is stored must be directly under the MWSDK, and the relative directory of the Makefile (described below) must not be changed.
Note: In MWSDK2021_09 and later, projects in other project folders can also run make, but you need to set MWSDK_ROOT.
.../MWSDK/{workspace dir}/{project dir}/Build/Makefile 
The workspace for building programs contains multiple projects, each of which is stored in Wks_TWELITE and builds a separate application.。
1
.../MWSDK/Wks_TWELITE/ProjectName1/...
2
.../MWSDK/Wks_TWELITE/ProjectName2/...
3
...
Copied!
The structure in the project is as follows: (Configuration varies by projec)
1
.../ProjectNameX/
2
       build/          : Storage location for generated binaries
3
           Makefile    : Generation rules
Copied!
Some sample projects may have a more complex structure. For example, multiple configurations, such as parent and child devices, may be maintained in a project.
​
​

前

Use with VSCode

次

How to build from the command line

最終更新 8mo ago

リンクのコピー

Workspaces