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>

diff --git a/Cura/util/sliceEngine.py b/Cura/util/sliceEngine.py
index 5d434cf8f9e7fc5ad9a48c3da2651f7fdb1d9294..d07af3367ed059034e6c95d95c1dc5832ee99656 100644 (file)
--- a/Cura/util/sliceEngine.py
+++ b/Cura/util/sliceEngine.py
@@ -43,6 +43,9 @@ def getEngineFilename():
                full_filename = os.path.abspath(os.path.join(base_search_path, '/'.join(['..'] * n), 'CuraEngine', search_filename))
                if os.path.isfile(full_filename):
                        return full_filename
+               full_filename = os.path.abspath(os.path.join(base_search_path, '/'.join(['..'] * n), 'CuraEngine', 'build', search_filename))
+               if os.path.isfile(full_filename):
+                       return full_filename
        if os.path.isfile('/usr/bin/CuraEngine'):
                return '/usr/bin/CuraEngine'
        if os.path.isfile('/usr/local/bin/CuraEngine'):