Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
build [2025/05/31 19:32] adminbuild [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.
  
Line 12: Line 12:
  
 === 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: Install GNU Make ==== ==== 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. - 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:\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 ==== ==== 3. Create a Makefile ====
Line 34: Line 34:
 Here’s a working example: Here’s a working example:
  
-```make+<code> 
 +make
 SRC_DIR ?= D:/data/lll_officework SRC_DIR ?= D:/data/lll_officework
 DST_DIR ?= D:/Project/gitwinch/build/artifacts DST_DIR ?= D:/Project/gitwinch/build/artifacts
Line 46: Line 47:
  if not exist $(subst /,\\,$(DST_DIR)) mkdir $(subst /,\\,$(DST_DIR))  if not exist $(subst /,\\,$(DST_DIR)) mkdir $(subst /,\\,$(DST_DIR))
  copy $(subst /,\\,$(SRC_DIR))\$*.txt $(subst /,\\,$(DST_DIR)) /y  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]] [[advanced?do=export_xhtml|Advanced uses]] | [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]]
  
build.1748712730.txt.gz · Last modified: by admin