Differences

This shows you the differences between two versions of the page.

--- build [2025/05/28 19:51] – created cherin
+++ build [2025/07/29 17:34] (current) – admin
@@ Line 1: / Line 1: @@
-====== Git Winch Build Automation using GNU Make ======
+====== Git Winch Build Automation ======
 === 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.
 === Why is it useful? ===
-- Ensures repeatable and automatic post-push actions (like copying updated files).
+- 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.
 === 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.
+**Caution**\\
+If you have an anti-virus installed, make sure that it allows the execution of the `build.bat` file.
 === How does it work? ===
@@ Line 19: / Line 21: @@
 ==== 0. Prerequisite: Install GNU Make ====
-- Download `make.exe` (Windows 32-bit) from a trusted GNU source.
+- Download `make.exe` (Windows 32-bit) from https://gnuwin32.sourceforge.net/packages/make.htm \\
-- Place it in `C:\apps\make` (or any preferred location).
+- Place it in `C:\apps\make` (or any preferred location).\\
 - Add this path to your **System PATH environment variable** so `make` can be used globally.
-==== 1. Create a Build Folder ====
+==== 1. Create an Artifacts Folder ====
 Decide where you want the processed files to be collected.
-Example: `D:\Project\GroupInGit\build\txt`
+Example: `D:\Project\gitwinch\build\artifacts`
 ==== 2. Define Source Folder ====
-Your working folder (e.g., `D:\data\lll_officework`) is where files are pushed from Git Winch.
+Your working folder (e.g., `D:\data\lll_officework`) is where files are pushed from //Git Winch//.
 ==== 3. Create a Makefile ====
 Write a makefile (ASCII format) named, for example, `makefile.lll.txt`. Place it anywhere accessible.
-Here’s a minimal working example:
+Here’s a working example:
-```make
+<code>
+make
 SRC_DIR ?= D:/data/lll_officework
-DST_DIR ?= D:/Project/GroupInGit/build/txt
+DST_DIR ?= D:/Project/gitwinch/build/artifacts
 FILES = $(notdir $(wildcard $(SRC_DIR)/*.txt))
@@ Line 47: / Line 50: @@
 	if not exist $(subst /,\\,$(DST_DIR)) mkdir $(subst /,\\,$(DST_DIR))
 	copy $(subst /,\\,$(SRC_DIR))\$*.txt $(subst /,\\,$(DST_DIR)) /y
+</code>
+----
+[[advanced?do=export_xhtml|Advanced uses]] | [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]]

Git Winch Guide

Differences

Page Tools