Windows releases

Robert Eden <[email protected]> Wed, 27 Apr 2022 15:43:15 -0500
Newsgroups	gmane.comp.tv.xmltv.devel
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--===============8189573571196200135==
Content-Type: multipart/alternative;
 boundary="------------WegBSp0JW5TwL8z0ClmGiGlF"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------WegBSp0JW5TwL8z0ClmGiGlF
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

The normal way to build a full windows release is

Perl Makefile.PL PREFIX=/path/to/temp/xmltv-1.1.2-win32
make windows_dist
(answer question about is the README updated... maybe remove question 
from build?)
Copy xmltv.exe to /path/to/temp/xmltv-1.1.2-win32/xmltv.exe
zip it up
upload

The benefit over "bare" xmltv.exe is it includes TXT versions of all the 
man pages... in other words, documentation! :)

If we create an "action" for automating official releases (not just 
pre-release artifacts for testing), something similar should be done for 
windows.  I'm not sure how Nick has done previous releases, but Gary is 
a wizard in this regard! :)

I just confirmed that the windows_dist makefile works fine on linux. (it 
needed tweaks to "sort-of" work on Windows) and added 
xmltv-1.1.2-win32.zip to the release (based on the release tar, not 
current alpha)

Robert


--------------WegBSp0JW5TwL8z0ClmGiGlF
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font size="4">The normal way to build a full windows release is<br>
      <br>
      Perl Makefile.PL PREFIX=/path/to/temp/xmltv-1.1.2-win32<br>
      make windows_dist<br>
      (answer question about is the README updated... maybe remove
      question from build?)<br>
      Copy xmltv.exe to  </font><font size="4"><font size="4">/path/to/temp/xmltv-1.1.2-win32</font>/xmltv.exe<br>
      zip it up<br>
      upload<br>
      <br>
      The benefit over "bare" xmltv.exe is it includes TXT versions of
      all the man pages... in other words, documentation! :)<br>
      <br>
      If we create an "action" for automating official releases (not
      just pre-release artifacts for testing), something similar should
      be done for windows.  I'm not sure how Nick has done previous
      releases, but Gary is a wizard in this regard! :) <br>
      <br>
      I just confirmed that the windows_dist makefile works fine on
      linux. (it needed tweaks to "sort-of" work on Windows) and added
      xmltv-1.1.2-win32.zip to the release (based on the release tar,
      not current alpha)<br>
      <br>
      Robert<br>
      <br>
      <br>
    </font>
  </body>
</html>

--------------WegBSp0JW5TwL8z0ClmGiGlF--


--===============8189573571196200135==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8189573571196200135==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
xmltv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

--===============8189573571196200135==--