The build time to launch is longer than in the Defold Editor

[RisingSunStudios]

Hi!

Great extension! Seems to take a little longer to launch the games than when launching from the editor and I'm noticing every launch the output show this message:

No engine found at 'h:\Defold\proj-space-game\SpaceGame\build\x86_64-win32\dmengine.exe', extracting from the Defold to 'h:\Defold\proj-space-game\SpaceGame\build\launcher\dmengine.exe'

Seems to always be looking in "x86_64-win32" but then installs the engine to "launcher" so it will never find it where it first looks.

The game launches but presumably this may be affecting launch times a little?

[astrochili]

Hi!

Log messages No engine found at... are okay. This happens when there are no dependencies with C++ extensions in the project and the engine is not built on the Defold server, so there is no "vanilla" engine in the build folder and it is necessary to extract it from Defold Editor resources. When you add the first native extension, the engine file will appear in this path.

Perhaps the message could be made friendlier to not so fluffy 😃.

Unfortunately, this is not a reason of the game taking longer to launch. The reason is the difference between the build in the editor and the build with a bob.jar. The editor caches something cleverly and probably does something else I don't know about. It's a good point to ask the Defold team about the difference and maybe find ways to implement similar behaviour, I'll do it 👌

[astrochili]

If you don't mind, I'll rename the ticket so I don't lose the idea.

[astrochili]

What I found out.

Monitoring of changed files is not difficult to implement in VS Code. But at the moment there is no functionality in bob for partial build to pass this files list there. Thus, for a quick build, there is no solution other than building from the editor.