Splits nimrod and lazarus files into separate directories.
This commit is contained in:
parent
46f652b93e
commit
116c54a8dd
9 changed files with 12 additions and 1 deletions
|
|
@ -1,4 +1,4 @@
|
||||||
# Backend for the Lazarus GUI
|
# Backend for the different user interfaces.
|
||||||
|
|
||||||
proc myAdd*(x, y: int): int {.cdecl, exportc.} =
|
proc myAdd*(x, y: int): int {.cdecl, exportc.} =
|
||||||
result = x + y
|
result = x + y
|
||||||
11
examples/cross_calculator/readme.txt
Normal file
11
examples/cross_calculator/readme.txt
Normal file
|
|
@ -0,0 +1,11 @@
|
||||||
|
The cross platform calculator illustrates how to use Nimrod to create a backend
|
||||||
|
called by different native user interfaces.
|
||||||
|
|
||||||
|
Since the purpose of the example is to show how the cross platform code
|
||||||
|
interacts with Nimrod the actual backend code is just a simple addition proc.
|
||||||
|
By keeping your program logic in Nimrod you can easily reuse it in different
|
||||||
|
platforms.
|
||||||
|
|
||||||
|
To avoid duplication of code, the backend code lies in a separate directory and
|
||||||
|
each platform compiles it with a different custom build process, usually
|
||||||
|
generating C code in a temporary build directory.
|
||||||
Loading…
Add table
Add a link
Reference in a new issue