kore-doc

The kore documentation found under https://docs.kore.io/
Commits | Files | Refs | README | git clone https://git.kore.io/kore-doc.git

commit dc8c0d82fbe4c4166e7d7c8df0c61945d37b7d1e
parent 7b8de4cece2f8c4daba2b732fd7dfc14df398bb1
Author: Joris Vink <joris@coders.se>
Date:   Wed, 28 Nov 2018 23:29:23 +0100

shuffle

Diffstat:
applications/building.md | 24------------------------
applications/integrated_tools.md | 27+++++++++++++++++++++++++++
2 files changed, 27 insertions(+), 24 deletions(-)

diff --git a/applications/building.md b/applications/building.md @@ -4,30 +4,6 @@ Kore provides a flexible way of building your applications through the **conf/bu This file contains build flavors that dictate CFLAGS and LDFLAGS. -The **kodev** tool will pickup the following environment variables if set: - -**CFLAGS** -> Any additional compiler flags. - -**LDFLAGS** -> Any additional linker flags. - -**KORE_PREFIX** -> The prefix where kore was installed. - -**KORE_SOURCE** -> Path where to find kore source, overrides **kore_source** from build.conf. - -**KORE_FLAVOR** -> Flavor to use, overrides **kore_flavor** from build.conf. - -**KORE_OBJDIR** -> The directory where the .o files will be placed. - -**KODEV_OUTPUT** -> The directory where the resulting binary is placed. - - Flavors can be switched using the **flavor** command: ``` diff --git a/applications/integrated_tools.md b/applications/integrated_tools.md @@ -72,3 +72,30 @@ $ See the [Running](/applications/running.md) section on how to start your Kore application in the background for production purposes. +### Environment Variables + +The **kodev** tool will pickup the following environment variables if set: + +**CFLAGS** +> Any additional compiler flags. + +**LDFLAGS** +> Any additional linker flags. + +**KORE_PREFIX** +> The prefix where kore was installed. + +**KORE_SOURCE** +> Path where to find kore source, overrides **kore_source** from build.conf. + +**KORE_FLAVOR** +> Flavor to use, overrides **kore_flavor** from build.conf. + +**KORE_OBJDIR** +> The directory where the .o files will be placed. + +**KODEV_OUTPUT** +> The directory where the resulting binary is placed. + + +