[xml] Update galician.xml

.github/dependabot.yml

@@ -0,0 +1,13 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+
+ # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"

.github/workflows/CI_build.yml

@@ -0,0 +1,64 @@
+name: CI_build
+
+on: [push, pull_request]
+
+jobs:
+  build:
+
+    runs-on: windows-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        build_platform: [x64, x86, ARM64]
+
+    steps:
+    - name: Checkout repo
+      uses: actions/checkout@v3
+
+    - name: Add msbuild to PATH
+      uses: microsoft/setup-msbuild@v1
+
+    - name: Add nmake
+      if: matrix.build_platform == 'ARM64'
+      uses: ilammy/msvc-dev-cmd@v1
+      with:
+          arch: amd64_arm64
+
+    - name: Add nmake
+      if: matrix.build_platform == 'x64' || matrix.build_platform == 'x86'
+      uses: ilammy/msvc-dev-cmd@v1
+      with:
+          arch: ${{ matrix.build_platform }}
+
+    - name: nmake libcurl
+      working-directory: curl/winbuild
+      run: |
+           nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static           MACHINE="${{ matrix.build_platform }}"
+           nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE="${{ matrix.build_platform }}"
+
+    - name: MSBuild of GUP exe
+      working-directory: vcproj
+      run: |
+           msbuild GUP.sln /m /p:configuration="Release" /p:platform="${{ matrix.build_platform }}"
+           msbuild GUP.sln /m /p:configuration="Debug"   /p:platform="${{ matrix.build_platform }}"
+
+    - name: Archive artifacts for x64
+      if: matrix.build_platform == 'x64'
+      uses: actions/upload-artifact@v3
+      with:
+          name: gup_exe_x64
+          path: bin64\
+
+    - name: Archive artifacts for x86
+      if: matrix.build_platform == 'x86'
+      uses: actions/upload-artifact@v3
+      with:
+          name: gup_exe_x86
+          path: bin\
+
+    - name: Archive artifacts for ARM64
+      if: matrix.build_platform == 'ARM64'
+      uses: actions/upload-artifact@v3
+      with:
+          name: gup_exe_arm64
+          path: binarm64\

.gitignore

@@ -24,6 +24,7 @@ ipch/
 *.opensdf
 *.sdf
 *.cachefile
+*.opendb
 
 #-- Backup & report files from converting an old project file to a newer
 #   Visual Studio version. Backup files are not needed, because we have git ;-)
@@ -51,8 +52,10 @@ UpgradeLog*.htm
 *.tmp_proj
 .builds
 *.pidb
+*.bak
 bin/
 bin64/
+binarm64/
 curl/build
 curl/builds
 
@@ -87,7 +90,6 @@ $RECYCLE.BIN/
 *.d
 *.o
 
-vcproj/GUP.sln
 curl/winbuild/CURL_OBJS.inc
 curl/winbuild/LIBCURL_OBJS.inc
 curl/winbuild/vc120.idb

README.md

@@ -1,16 +1,23 @@
-What is WinGup?
+What is WinGUp for Notepad++?
+--------------------------
+
+This project is the fork of [WinGUp](https://github.com/gup4win/wingup).
+WinGUp has been built for Notepad++'s need, but keep its functionality generic for being able to be used on any Windows application. With new built-in Plugins Admin in Notepad++, a more specific updater for Notepad++ is necessary. Hence this fork from the original WinGUp.
+
+
+What is WinGUp?
 ---------------
 
-WinGup is a Generic Updater running under Windows environment.
-The aim of WinGup is to provide a ready to use and configurable updater
+WinGUp is a Generic Updater running under Windows environment.
+The aim of WinGUp is to provide a ready to use and configurable updater
 which downloads a update package then installs it. By using cURL library
-and TinyXml module, WinGup is capable to deal with http protocol and process XML data.
+and TinyXml module, WinGUp is capable to deal with http protocol and process XML data.
 
 
-Why WinGup?
+Why WinGUp?
 -----------
 
-Originally WinGup was made for the need of Notepad++ (a generic source code editor under MS Windows).
+Originally WinGUp was made for the need of Notepad++ (a generic source code editor under MS Windows).
 During its conception, the idea came up in my mind: if it can fit Notepad++, it can fit for any Windows program.
 So here it is, with LGPL license to have no (almost not) restriction for integration in any project.
 
@@ -19,8 +26,8 @@ So here it is, with LGPL license to have no (almost not) restriction for integra
 How does it work?
 -----------------
 
-WinGup can be launched by your program or manually. It reads from a xml configuration file
-for getting the current version of your program and url where WinGup gets update information,
+WinGUp can be launched by your program or manually. It reads from a xml configuration file
+for getting the current version of your program and url where WinGUp gets update information,
 checks the url (with given current version) to get the update package location,
 downloads the update package, then run the update package (it should be a msi or an exe) in question.
 
@@ -29,47 +36,49 @@ downloads the update package, then run the update package (it should be a msi or
 Who will need it?
 -----------------
 
-Being LGPLed, WinGup can be integrated in both commercial (or close source) and open source project.
+Being LGPLed, WinGUp can be integrated in both commercial (or close source) and open source project.
 So if you run a commercial or open a source project under MS Windows and you release your program at
-regular intervals, then you may need WinGup to notice your users the new update.
+regular intervals, then you may need WinGUp to notice your users the new update.
 
 
 
 What do you need to use it?
 ---------------------------
 
-A url to provide the update information to your WinGup and an another url location
+A url to provide the update information to your WinGUp and an another url location
 to store your update package, that's it!
 
 
 
-How is WinGup easy to use?
+How is WinGUp easy to use?
 --------------------------
 
-All you have to do is point WinGup to your url update page (by modifying gup.xml), 
+All you have to do is point WinGUp to your url update page (by modifying gup.xml), 
 then work on your pointed url update page (see getDownLoadUrl.php comes with the release)
-to make sure it responds to your WinGup with the correct xml data.
+to make sure it responds to your WinGUp with the correct xml data.
 
 
 
 How to build it?
 ----------------
 
- 0. You have to build cURL before building WinGup:
- ```
-    a. Open VS2015 Native Tool Command for 32/64 bits
-    b. go to curl winbuild directory:
-       cd <your wingup source path>\curl\winbuild
-	c. compile cURL by using one of the following commands, according the mode and archetecture of wingup you want to build.
-       x64 release: nmake /f Makefile.vc mode=dll vc=14 RTLIBCFG=static MACHINE=x64
-       x64 debug: nmake /f Makefile.vc mode=dll vc=14 RTLIBCFG=static DEBUG=yes MACHINE=x64
-       x86 release: nmake /f Makefile.vc mode=dll vc=14 RTLIBCFG=static MACHINE=x86
-       x86 debug: nmake /f Makefile.vc mode=dll vc=14 RTLIBCFG=static DEBUG=yes MACHINE=x86
-```
- 1. Open [`vcproj\GUP.vcxproj`](https://github.com/gup4win/wingup/blob/master/vcproj/GUP.vcxproj)
+ * Step 1: You have to build cURL before building WinGUp:
+
+    1. Open VS2022 Native Tool Command for 32/64 bits. If you want to build for ARM, open a cmd, and run the following command:<br/>
+    `C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsamd64_arm64.bat`
+    2. go to curl winbuild directory:<br/>
+       `cd <your WinGUp source path>\curl\winbuild`
+    3. compile cURL by using one of the following commands, according the mode and architecture of WinGUp you want to build.
+       - x64 release: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=x64`
+       - x64 debug: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE=x64`
+       - x86 release: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=x86`
+       - x86 debug: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE=x86`
+       - ARM64 release: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=ARM64`
+       - ARM64 debug: `nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE=ARM64`
+
+ * Step 2: Open [`vcproj\GUP.sln`](https://github.com/gup4win/wingup/blob/master/vcproj/GUP.sln) with VS2022.
 
- 2. Build WinGup [like a normal Visual Studio project](https://msdn.microsoft.com/en-us/library/7s88b19e.aspx) with VS2015
-
+ * Step 3: Build WinGUp like a normal Visual Studio project.
 
 
 To whom should you say "thank you"?