chiark / gitweb /
~ianmdlvl / cura.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 00938bc) | patch
Look for CuraEngine in ..../CuraEngine/build/CuraEngine[.exe]
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Sat, 6 Feb 2016 16:06:45 +0000 (16:06 +0000)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Sat, 6 Feb 2016 18:31:20 +0000 (18:31 +0000)
commit1cce2ae5e41c8305c81456eeaf625c172d76a0b1
treed762c37c85c138357a375398937bf76dd11e6211tree | snapshot
parent00938bc43ca4598ef725f0871502bdf76c2b8939commit | diff
Look for CuraEngine in ..../CuraEngine/build/CuraEngine[.exe]

If you clone CuraEngine inside cura, as the instructions suggest, this
is where the CuraEngine build ends up putting it.

With this, invoking ./dev-cura actually finds the engine in our build
tree.

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Cura/util/sliceEngine.py diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.