lib/w64devkit
1
0
Fork 0
mirror of https://github.com/skeeto/w64devkit.git synced 2025-08-05 00:22:07 +03:00
Code Activity

Remove activate.bat (replaced by w64devkit.exe)

Browse Source
This commit is contained in:
Christopher Wellons
2021-09-25 14:26:55 -04:00
parent 0b8cc138c6
commit adf9aa7449
2 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Dockerfile
View File

@@ -401,8 +401,6 @@ RUN printf "id ICON \"$PREFIX/src/w64devkit.ico\"" >w64devkit.rc \
>>$PREFIX/COPYING.MinGW-w64-runtime.txt . \
&& cat /mingw-w64-v$MINGW_VERSION/mingw-w64-libraries/winpthreads/COPYING \
>>$PREFIX/COPYING.MinGW-w64-runtime.txt \
&& printf '@set PATH=%%~dp0bin;%%PATH%%\r\n@busybox sh -l\r\n' \
>$PREFIX/activate.bat \
&& echo $VERSION >$PREFIX/VERSION.txt
ENV PREFIX=${PREFIX}
CMD zip -qXr - $PREFIX

8
README.md
View File

@@ -32,10 +32,10 @@ internet connection during the first couple minutes of the build.
## Usage
The final .zip file contains tools in a typical unix-like configuration.
Unzip the contents anywhere. Inside is `w64devkit.exe` (or `activate.bat`)
that launches a console window with the environment configured and ready
to go. It is the easiest way to enter the development environment, and
requires no system changes.
Unzip the contents anywhere. Inside is `w64devkit.exe` that launches a
console window with the environment configured and ready to go. It is the
easiest way to enter the development environment, and requires no system
changes.
Alternatively, add the `bin/` directory to your path. For example, while
inside a console or batch script: