summary refs log tree commit diff stats
diff options
context:
space:
mode:
-rw-r--r--examples/cross_calculator/nimrod_commandline/nimrod.cfg4
-rw-r--r--examples/cross_calculator/nimrod_commandline/readme.txt7
-rw-r--r--examples/cross_todo/nimrod_commandline/nimrod.cfg4
-rw-r--r--examples/cross_todo/nimrod_commandline/readme.txt7
4 files changed, 16 insertions, 6 deletions
diff --git a/examples/cross_calculator/nimrod_commandline/nimrod.cfg b/examples/cross_calculator/nimrod_commandline/nimrod.cfg
new file mode 100644
index 000000000..c1aedcf6a
--- /dev/null
+++ b/examples/cross_calculator/nimrod_commandline/nimrod.cfg
@@ -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"
diff --git a/examples/cross_calculator/nimrod_commandline/readme.txt b/examples/cross_calculator/nimrod_commandline/readme.txt
index 45c1a30af..5430e7b47 100644
--- a/examples/cross_calculator/nimrod_commandline/readme.txt
+++ b/examples/cross_calculator/nimrod_commandline/readme.txt
@@ -4,6 +4,7 @@ cross-calculator sample.
 The commandline interface can be used non interactively through switches, or
 interactively when running the command without parameters.
 
-Compilation 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 nimcalculator.nim'.
diff --git a/examples/cross_todo/nimrod_commandline/nimrod.cfg b/examples/cross_todo/nimrod_commandline/nimrod.cfg
new file mode 100644
index 000000000..c1aedcf6a
--- /dev/null
+++ b/examples/cross_todo/nimrod_commandline/nimrod.cfg
@@ -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"
diff --git a/examples/cross_todo/nimrod_commandline/readme.txt b/examples/cross_todo/nimrod_commandline/readme.txt
index 17820a7d3..b4362b8c5 100644
--- a/examples/cross_todo/nimrod_commandline/readme.txt
+++ b/examples/cross_todo/nimrod_commandline/readme.txt
@@ -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'.