Use with VSCode

VSCode has a code interpretation (IntelliSense) feature that makes code editing more efficient. In addition, the task feature allows you to execute build commands from VSCode.

Open the project

In order to build the TWELITE app, you will need to open the project in Visual Studio Code.

The steps to open the project are as follows:

Build the app

To build the application, follow the steps below, running the make utility from VSCode. for details on make, refer to "How to Build" and "About Makefile".

For example, if you want to build a standard TWELITE app, select the VSCode task "Build App_Twelite_Master (BLUE)".

Since VSCode executes command line make, command line error messages are also output.

Switch code interpretation

You can switch between code interpretation for TWELITE BLUE and code interpretation for TWELITE RED. To switch between code interpretations, click on the location shown in the figure and select the TWELITE model for your development.

Switches the C definition specific to each type of TWELITE module.

It is not guaranteed that the code interpretation and compiler interpretation will match perfectly. In addition, some definitions may not be interpreted due to header file descriptions.

Switches the C definition specific to each type of TWELITE module.

It is not guaranteed that the code interpretation and compiler interpretation will match perfectly. In addition, some definitions may not be interpreted due to header file descriptions.

The header file to be loaded does not directly refer to the header file of the compiler or library, but refers to a copy under {SDK folder}/Tools/VSCode/include.

About JSON files

The above build and code interpretation are defined in the JSON file.

.vscode/c_cpp_properties.json

Define implicit and other definitions at build time, and specify the include folder.

If additional definitions are needed, duplicate or edit the entries for "name" : "TWELITE_BLUE" or "name" : "TWELITE_RED" in the existing files.

You will need to edit "name" "includePath" and so on. If you need a specific build definition, add an entry to "defines".

.vscode/tasks.json

Defining the build task.

If you want to add a new build definition, copy and edit an already existing entry. Each build task has an entry for windows, linux, and osx.

You will need to edit "label", "options", "cwd", and so on.

"tasks": [
{ 
  "label": "Build Samp_PingPong,PingPong (BLUE)",
  "type": "shell",
  ..
  "windows": {
     "command": "make",
     "args": [ "TWELITE=BLUE",  "clean", "all" ],
     "options": { "env": { "PATH": "${workspaceRoot}\\..\\..\\Tools\\MinGW\\msys\\1.0\\bin" } }
  },
  "problemMatcher": { "base": "$gcc", "fileLocation": [ "absolute" ] },
  "options": { "cwd": "${workspaceRoot}/PingPong/Build" }
},
..

The "options": { "cwd" ... } setting specifies the build folder.。
If you want to add a make argument, add an entry after TWELITE=XXX in "args".

Set to an existing build task

Add group": { "kind": "build", "isDefault": true } as shown in the following example. The task will become the default build definition and can be executed by [Task]>[Execute Build Task] or by using shortcut keys.

"tasks": [
{ 
  "label": "Build Samp_PingPong,PingPong (BLUE)",
  "type": "shell",
  ..
  "options": { "cwd": "${workspaceRoot}/PingPong/Build"},
  "group": { "kind": "build", "isDefault": true }
},
..

前へInstall TWELITE SDK (MWSDK)次へfolder structure

最終更新 2 年前