Remove obsolete stuffs

bin/notepad++/updater/README.md

@@ -0,0 +1,91 @@
+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
+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.
+
+
+Why WinGUp?
+-----------
+
+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.
+
+
+
+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,
+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.
+
+
+
+Who will need it?
+-----------------
+
+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.
+
+
+
+What do you need to use it?
+---------------------------
+
+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?
+--------------------------
+
+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.
+
+
+
+How to build it?
+----------------
+
+ * 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 directory, :<br/>
+       `cd <your WinGUp source path>\curl\` then run:
+       `buildconf.bat`
+    3. go to winbuild directory, which is under curl directory:<br/>
+       `cd winbuild`
+    4. 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.
+ 
+ * Step 3: Build WinGUp like a normal Visual Studio project.
+
+
+To whom should you say "thank you"?
+-----------------------------------
+
+Don HO
+<don.h@free.fr>