diff options
author | bubnikv <bubnikv@gmail.com> | 2019-05-13 16:47:33 +0300 |
---|---|---|
committer | bubnikv <bubnikv@gmail.com> | 2019-05-13 16:47:33 +0300 |
commit | 253b57e4a3b4f6eab5d357b1a42806d368754209 (patch) | |
tree | 99c11b9a6595fd0248efd07e313af56a8816c413 /doc | |
parent | f1f003d56ccb16f1fdb3006b13fedabca3e6c6af (diff) |
Yet some renaming to PrusaSlicer
Diffstat (limited to 'doc')
-rw-r--r-- | doc/How to build - Mac OS.md | 2 | ||||
-rw-r--r-- | doc/How to build - Windows.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/How to build - Mac OS.md b/doc/How to build - Mac OS.md index 590f48db1..42a71e10d 100644 --- a/doc/How to build - Mac OS.md +++ b/doc/How to build - Mac OS.md @@ -44,7 +44,7 @@ Alternatively, if you would like to use XCode GUI, modify the `cmake` command to cmake .. -GXcode -DCMAKE_PREFIX_PATH="$PWD/../deps/build/destdir/usr/local" -and then open the `Slic3r.xcodeproj` file. +and then open the `PrusaSlicer.xcodeproj` file. This should open up XCode where you can perform build using the GUI or perform other tasks. ### Note on Mac OS X SDKs diff --git a/doc/How to build - Windows.md b/doc/How to build - Windows.md index 71f74c66d..242af9dab 100644 --- a/doc/How to build - Windows.md +++ b/doc/How to build - Windows.md @@ -44,8 +44,8 @@ Note that if you're building a 32-bit variant, you will need to change the `"Vis Conversely, if you're using Visual Studio version other than 2013, the version number will need to be changed accordingly. -If `cmake` has finished without errors, go to the build directory and open the `Slic3r.sln` solution file in Visual Studio. -Before building, make sure you're building the right project (use one of those starting with `slic3r_app_...`) and that you're building +If `cmake` has finished without errors, go to the build directory and open the `PrusaSlicer.sln` solution file in Visual Studio. +Before building, make sure you're building the right project (use one of those starting with `PrusaSlicer_app_...`) and that you're building with the right configuration, i.e. _Release_ vs. _Debug_. When unsure, choose _Release_. Note that you won't be able to build a _Debug_ variant against a _Release_-only dependencies package. |