From 972c51086152bd45aef4eb17c099fa3472a19d04 Mon Sep 17 00:00:00 2001 From: Andreas Rumpf Date: Sat, 23 Aug 2008 11:32:48 +0200 Subject: deleted web and dist --- doc/mytest.cfg | 20 ++++++++++++++++++++ doc/steps.txt | 24 ++++++++++++++++++++++++ 2 files changed, 44 insertions(+) create mode 100644 doc/mytest.cfg create mode 100644 doc/steps.txt (limited to 'doc') diff --git a/doc/mytest.cfg b/doc/mytest.cfg new file mode 100644 index 000000000..be1118c46 --- /dev/null +++ b/doc/mytest.cfg @@ -0,0 +1,20 @@ +# This is a comment. +; this too. + +[Common] +cc=gcc # '=' and ':' are the same +--verbose + +[Windows] +isConsoleApplication=False ; another comment + +[Posix] +isConsoleApplication=True + +key1: "in this string backslash escapes are interpreted\n" +key2: r"in this string not" +key3: """triple quotes strings +are also supported. They may span +multiple lines.""" + +--"long option with spaces": r"c:\myfiles\test.txt" diff --git a/doc/steps.txt b/doc/steps.txt new file mode 100644 index 000000000..89339377b --- /dev/null +++ b/doc/steps.txt @@ -0,0 +1,24 @@ +============================== +First steps after installation +============================== + +This document explains how to *use* the Nimrod compiler. +Open your favourite text editor and type (or download it +`here `_): + +.. code-block:: nimrod + :file: ../tests/hallo.nim + +Save this file as ``hallo.nim`` somewhere (I refer to the location as +``$yourloc``). Now open a console and call the Nimrod compiler:: + + nimrod compile --run $yourloc/hallo + +The ``--run`` switch tells Nimrod that it should run the generated +executable after successful compilation. If things don't work, +check if Nimrod's ``bin`` directory is in your path environment +variable. On Windows the directory ``dist\llvm-gcc4.2\bin`` may +also be required in your path. + +Note that Nimrod produced a standalone native executable in +``$yourloc`` that you can run without the Nimrod compiler. -- cgit 1.4.1-2-gfad0