-
Notifications
You must be signed in to change notification settings - Fork 33
package.json.en
All path is (and must) relative to current kendryte-package.json
You must select this before any other operation, change this during development will reset other settings to defaults.
There are three choices:
- Library: if you want to share a library, and it's open-source.
- Prebuilt Library: same as above but closed-source.
- Executable: if you want to create an executable program.
Only allow to use: 0-9, a-z, -(minus), _(underscore)
You should name your library like: ${userName}_${libraryName}
, it should match your github repo (if any).
Simple informational field, Only usefull if you publish your library.
Set your prebuilt library file path. This is only visible if your project type is
Other visible fileds see below
These fields will invisible from Prebuilt
project, it does not need compile.
Raw arguments passthrough to these programs. One argument each line. (separator is not a space char, but a newline!)
You can set several folders (one per line), you will able to use #include
relative to these folders.
This will limited to your code, do not affect projects who include your code as library.
Set which file(s) will be compiled. One file each line. Must use /
but not \
as path separator.
You can use glob, eg:
-
src/*.c
to match all.c
file insidesrc
folder. -
lib/**/*.c
like1.
But also include all it's child folders. -
main.c
match onlymain.c
in project root folder.
You can set a ld file if you do not use SDK.
Create user configurable #define
in your project. Mainly used for source-code library. Because people who include your library can change this without modify your code.
You can set two kined of constants:
-
string:
MOTD_STRING:str=hello world
-
other:
IS_DEBUG:any=1
The only different isstr
will add double quote around the value. Currently,:any
cannot be omitted.