KODEV(1)
β¨ NAME β¨
kodev β the Kore project management tool, bestie π
πΈ SYNOPSIS πΈ
kodev [OPTION] ...
π DESCRIPTION π
okay so this whole page is about the app management tools for building and running a Kore project. that's it, that's the vibe.
if you're here for the technical interface and the C bindings, you want kore(3) instead β that's where all those functions and structures get described. not here. go look. π«Ά
Kore projects can be managed with the following OPTIONS, and yes we're going through every single one:
createβ makes a brand new application skeleton with whatever name you hand it. it'll spin up a whole new directory with every file you need to start hacking. the GENERATED FILES section below has the receipts. π±buildβ builds the application. more deets in BUILDING. π¨runβ starts the application in the foreground, main character style. see RUNNING. πreloadβ reloads the application. it's literally just a shortcut for sendingSIGHUPto the parent process (check outkore_pid). π¨infoβ shows you info about the application config, namely: active flavor, output type, Kore features, Kore source and Kore binary. the whole β¨situationβ¨.cleanβ cleans up the build files. bye bye clutter π§Ήflavorβ switches between build flavors, and the argument you pass is the new flavor. π¦helpβ shows the help synopsis. when in doubt π
π GENERATED FILES π
run create and you get a bunch of new files dropped under a directory matching the application name you specified. slay.
These files are:
conf/build.confβ the build configuration.conf/app.confβ the Kore application configuration.src/app.cβ the initial placeholder source code.cert/server.pemβ the self-signed auto-generated x509 certificate.cert/key.pemβ the key matching the self-signed x509 certificate.dh2048.pemβ the 2048-bit DH parameters used by TLS.
Those files are:
kore.confβ the Kore application configuration.handlers.pyβ the initial placeholder python page handler.__init__.pyβ the python initialization code. sets up the kore listener, etc.cert/server.pemβ the self-signed auto-generated x509 certificate.cert/key.pemβ the key matching the self-signed x509 certificate.dh2048.pemβ the 2048-bit DH parameters used by TLS.
π₯ BUILDING π₯
running the build command builds your application. how that actually happens is up to the conf/build.conf configuration file. that file supports these directives, and we're listing all of them:
single_binary [yes|no]β set it toyesand the build system produces a single binary containing both your application code AND the Kore code, so you can distribute your app way more easily. set it tonoand you get a standard dynamically linked library that gets loaded into Kore at runtime instead. pick your fighter. πkore_source [path]β must be set to point to the a Kore source code directory. only used if thesingle_binaryoption is set toyes.- Example:
kore_source=/home/joris/src/kore
- Example:
kore_flavor [build options]β defines the build arguments for building Kore. only used if thesingle_binaryoption is set toyes.- Example:
kore_flavor=NOTLS=1
- Example:
cflagsβ standard CFLAGS used when compiling the application source code.ldflagsβ standard LDFLAGS used when linking the application source code.
heads up bestie: thebuildcommand obeys the environment variablesCCandCXXπ
π RUNNING π
executing the run command starts your application in the foreground. periodt.
which binary it actually executes depends on whether the single_binary flag was set in the build configuration:
- if
single_binarywas enabled,runexecutes the binary produced by the build system. - if
single_binarywas not enabled,runexecutes the$PREFIX/bin/korebinary.
and in both cases, the run command passes the -fnr command line options to the binary. every time. no exceptions. β
π¦ EXAMPLES π¦
changing the flavor of the build:
$ kodev flavor osx
building your application:
$ kodev build
π REPORTING BUGS, CONTRIBUTING && MORE π
if you run into any bugs, or you've got suggestions or patches, please contact me at joris@coders.se π
more information can be found at https://kore.io/
π AUTHOR π
Kore developed by Joris Vink joris@coders.se
Manpage authored by Guy Nankivell guynankivell@gmail.com
π LICENCE π
usage of this software is provided under the ISC license which may be found, with the source, at https://github.com/jorisvink/kore
and that's the whole thing, babes β this was the kodev page from the General Commands Manual (section 1, as the footer confirms π). ty for reading, go build something iconic, mwah πβ¨
π¦ where this page comes from
- debian bookworm: kore 4.1.0-6+b1 Β· ISC
- nixos 26.05: kore 4.2.3
- nixpkgs unstable: kore 4.2.3
- ubuntu jammy: kore 4.1.0-6 Β· ISC
- ubuntu noble: kore 4.1.0-6 Β· ISC
- ubuntu resolute: kore 4.2.3-2 Β· ISC
- ubuntu stonking: kore 4.2.3-2build1 Β· ISC
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms