Replaces shell scripts with nimrod configuration files.
This should make compilation more cross platform friendly.
This commit is contained in:
parent
6cfbfc43a4
commit
d98826271a
4 changed files with 16 additions and 6 deletions
4
examples/cross_todo/nimrod_commandline/nimrod.cfg
Normal file
4
examples/cross_todo/nimrod_commandline/nimrod.cfg
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
# Nimrod configuration file.
|
||||
# The file is used only to add the path of the backend to the compiler options.
|
||||
|
||||
path="../nimrod_backend"
|
||||
|
|
@ -13,6 +13,7 @@ in your user's data directory. To cope with an empty database, a special
|
|||
generation switch can be used to fill the database with some basic todo entries
|
||||
you can play with.
|
||||
|
||||
Compilation of the interface is fairly easy, just include the path to the
|
||||
backend in your compilation command. A basic build.sh is provided for unix like
|
||||
platforms with the correct parameters.
|
||||
Compilation is fairly easy despite having the source split in different
|
||||
directories. Thanks to the nimrod.cfg file, which adds the ../nimrod_backend
|
||||
directory as a search path, you can compile and run the example just fine from
|
||||
the command line with 'nimrod c -r nimtodo.nim'.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue