We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a look at this makefile:
https://github.com/objeck/objeck-lang/blob/master/core/shared/make/Makefile.msys2-ucrt.amd64
Something really strange happened. The first time you run ./deploy_msys2-ucrt.sh it will present you this error and it will fail to build obc.exe:
./deploy_msys2-ucrt.sh
obc.exe
cp logger.a ../compiler; cp logger.a ../vm; cp logger.a ../release/WindowsLauncher/AppLauncher cp: cannot create regular file '../release/WindowsLauncher/AppLauncher': No such file or directory
Seems as simple as you are copying file into an nonexistent directory, isn't it?
But if you run ./deploy_msys2-ucrt.sh the second time, the error will mysteriously disappeared and you have obc.exe build as expected!
The text was updated successfully, but these errors were encountered:
fixed scriptbuild ebug�#153
ab04360
Should be fixed
Sorry, something went wrong.
0b5d650
fixed build script bug #153
1e8af92
No branches or pull requests
Have a look at this makefile:
https://github.com/objeck/objeck-lang/blob/master/core/shared/make/Makefile.msys2-ucrt.amd64
Something really strange happened. The first time you run
./deploy_msys2-ucrt.sh
it will present you this error and it will fail to buildobc.exe
:Seems as simple as you are copying file into an nonexistent directory, isn't it?
But if you run
./deploy_msys2-ucrt.sh
the second time, the error will mysteriously disappeared and you haveobc.exe
build as expected!The text was updated successfully, but these errors were encountered: