Skip to content

Commit 1271f9a

Browse files
committed
Add build instructions
1 parent 8a04275 commit 1271f9a

File tree

1 file changed

+32
-0
lines changed

1 file changed

+32
-0
lines changed

README.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# flowsolver
2+
3+
Solves Flow (aka Numberlink) puzzles using the Z3 constraint solver.
4+
5+
## building
6+
7+
Depends on Raylib and Z3.
8+
9+
To generate build files, you can run CMake normally:
10+
```
11+
mkdir build
12+
cd build
13+
cmake .. # Add your preferred CMake options here, such as -G or -DCMAKE_BUILD_TYPE
14+
```
15+
16+
And then run whatever generator you configured CMake to use.
17+
18+
### on windows without vcpkg
19+
20+
When building on Windows without VcPkg, you will need to point CMake to Z3, and
21+
create Raylib CMake files for CMake to point at. To create the Raylib files, it
22+
should be OK to copy the Z3 `lib/cmake/` files and modify the version code and
23+
the library handling code. As a general rule:
24+
- `z3::libz3` -> `raylib`
25+
- `bin/libz3.dll` -> `lib/raylib.dll`
26+
- `lib/libz3.lib` -> `lib/raylib.lib`
27+
- `MAJOR.MINOR.BUGFIX.TWEAK` (z3) -> `MAJOR.MINOR.BUGFIX` (raylib)
28+
29+
Then, you can point CMake to these files, by setting `CMAKE_PREFIX_PATH` to
30+
`${z3_dir}\lib\cmake\z3;${raylib_dir}\lib\cmake\raylib`.
31+
32+
Once Raylib ships with MSVC CMake files, this shouldn't need to be done.

0 commit comments

Comments
 (0)