This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| build [2025/05/28 20:50] – cherin | build [2025/05/31 19:39] (current) – [0. Prerequisite: Install GNU Make] admin | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| === What is it? === | === What is it? === | ||
| - | Git Winch includes a lightweight build automation capability designed for users who want to perform actions after a successful file push. While originally created for non-technical teams, it also supports technical use-cases like triggering builds for software development or office automation tasks. | + | //Git Winch// includes a lightweight build automation capability designed for users who want to perform actions after a successful file push. While originally created for non-technical teams, it also supports technical use-cases like triggering builds for software development or office automation tasks. |
| This system uses a simple `build.bat` file and GNU Make to selectively process updated files after every successful push. | This system uses a simple `build.bat` file and GNU Make to selectively process updated files after every successful push. | ||
| === Why is it useful? === | === Why is it useful? === | ||
| - | - Ensures repeatable and automatic post-push actions. | + | - Ensures repeatable and automatic post-push actions.\\ |
| - | - Reduces errors from manual post-processing. | + | - Reduces errors from manual post-processing.\\ |
| - | - Helps both technical and non-technical users organize file workflows with minimal effort. | + | - Helps both technical and non-technical users organize file workflows with minimal effort.\\ |
| - Ideal for setting up automated build folders or staging areas for server deployment. | - Ideal for setting up automated build folders or staging areas for server deployment. | ||
| === When does it run? === | === When does it run? === | ||
| - | This build process runs automatically **after a successful push** from Git Winch. The `build.bat` file in the repository is triggered and can invoke GNU Make to execute post-push file actions. | + | This build process runs automatically **after a successful push** from //Git Winch//. The `build.bat` file in the repository is triggered and can invoke GNU Make to execute post-push file actions. |
| === How does it work? === | === How does it work? === | ||
| Line 18: | Line 18: | ||
| ==== 0. Prerequisite: | ==== 0. Prerequisite: | ||
| - | - Download `make.exe` (Windows 32-bit) from a trusted GNU source. | + | - Download `make.exe` (Windows 32-bit) from https:// |
| - | - Place it in `C: | + | - Place it in `C: |
| - Add this path to your **System PATH environment variable** so `make` can be used globally. | - Add this path to your **System PATH environment variable** so `make` can be used globally. | ||
| Line 27: | Line 27: | ||
| ==== 2. Define Source Folder ==== | ==== 2. Define Source Folder ==== | ||
| - | Your working folder (e.g., `D: | + | Your working folder (e.g., `D: |
| ==== 3. Create a Makefile ==== | ==== 3. Create a Makefile ==== | ||
| Line 34: | Line 34: | ||
| Here’s a working example: | Here’s a working example: | ||
| - | ```make | + | < |
| + | make | ||
| SRC_DIR ?= D:/ | SRC_DIR ?= D:/ | ||
| DST_DIR ?= D:/ | DST_DIR ?= D:/ | ||
| Line 46: | Line 47: | ||
| if not exist $(subst /, | if not exist $(subst /, | ||
| copy $(subst /, | copy $(subst /, | ||
| + | |||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | [[advanced? | ||