I have been doing a bunch of tutorials and now I’m stuck with a problem when doing the Runner tutorial.
Somehow the Spine Extension (or any other extension?) makes the build process fail for me.
To build an empty project - no errors.
If I add the Spine extension (the latest zip in Dependencies + Fetch Libraries) into an empty project, I can also build without an error. I have noticed that a folder build/x86_64-win32 is created with some files in it, dmengine.exe among others.
As soon as I make the slightest change in the project like adding a Game object or comment in a script, I get Launching New Local Engine failed with reference to the build/x86_64-win32 folder, which now is empty.
If I remove the extension by removing it from Dependencies (+Fetch), I can build errorfree again.
Any suggestions?
I’m on the latest version of Defold, have tried earlier versions of the extension, same behaviour.
Ok, it seems it has to do with me having the project folder mirrored on Google Drive. When testing outside Google Drive or when syncing to Google Drive is paused building works fine. I find it odd however that this only applies when using the Spine Extension (or any other extension?) and after making a change in the project.
If anyone has a simple explanation to this I would be glad but in any case I’ll continue outside Google Drive. And start to learn about git.
Sorry for spamming this forum, but it seems like Google Drive is disrupting the build process when there are extensions in the project, as it then uses a system-specific folder (ie x86_64-win32/) that is created (and overwrites a possible old one) every time Build is done.
I still would like to use Google Drive for practical reasons. Is there a way to tell Defold to use a build folder on some other location, instead of inside the project folder?
