Skip to content

Commit

Permalink
Tweaked README for OSX
Browse files Browse the repository at this point in the history
  • Loading branch information
gokr committed Jun 29, 2020
1 parent 736154d commit 386ff53
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@ This works on my Ubuntu 64 bit (after installing normal C tools needed):

0. Clone ORX with `git clone https://github.com/orx/orx.git`.
1. Run `setup.sh` in top level first, this pulls down more dependencies.
2. Build with `cd code/build/linux/gmake && make config=release64` (build also `debug64` and `profile64` to get those extra libraries)
3. Copy libraries **to a library path** with for example `cp -a ../../../bin/liborx*.so /usr/lib/`
2. Build with `cd code/build/linux/gmake && make config=release64` (build also `debug64` and `profile64` to get those extra libraries). Same on OSX but in `code/build/mac`.
3. Copy libraries **to a library path** with for example `sudo cp -a ../../../bin/liborx*.so /usr/lib/` on Linux and `sudo cp -a ../../../bin/liborx*.dylib /usr/local/lib/` on OSX.

For other platforms, or if you get into trouble, follow [official ORX instructions](https://wiki.orx-project.org/en/guides/beginners/downloading_orx) that give much more details!

Expand Down
2 changes: 1 addition & 1 deletion samples/sample1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@ Then run `nimble install` in this directory which will compile and install the b
After that you can run `sample1`. ESC quits. Pressing the key below ESC (may be different depending on your keyboard, on mine it's "§" but evidently "`" on others I guess) opens the ORX console.

# Compiling
A Nim debug build will use `liborxd.so`, a release build will use `liborx.so` and if you build with `nim c -d:profile` it will use `liborxp.so`.
A Nim debug build will use `liborxd.so|dylib|dll`, a release build will use `liborx.so|dylib|dll` and if you build with `nim c -d:profile` it will use `liborxp.so|dylib|dll`.

0 comments on commit 386ff53

Please sign in to comment.