Messed up windows deployment

[tmheath]

My Problem

I fixed this in a prior release a long time ago, the launch process has changed since then.
I updated the fork I'd used and where it pointed the launcher still had the old filenames.
I don't understand where the launching details were moved to or otherwise how they are
generated at build to be renamed as they are in the download. If I'm given the info then
I'll submit a PR to the proper repo. Without these fixes, lem will only launch from the local
directory and when called from an existing command prompt will close that command
prompt.

Problems

The most recent SDL2 Windows release downloaded with lem.bat both closing the terminal when called via terminal which is annoying if not run from a start menu or double clicked. I've deleted the exit command from the file to fix this, behavior via other launch methods remain unchanged.

There is also a bug in the current version fixed by adding %~dp0 in front of the calling line to the exe filename, this change enabled launching via start menu as prior to this the launcher would just crash.

The modified launcher

@echo off
set PATH=%~dp0lib;%PATH%
start "" "%~dp0lem-internal.exe"

From

@echo off
set PATH=%~dp0lib;%PATH%
start "" "lem-internal.exe"
exit

Hoping to use common lisp for a small side project in personal life, excited to try getting involved with this again.