XMLTVexeBuild - Revision history

Rmeden at 01:46, 11 March 2022

2022-03-11T01:46:25Z

Rmeden: tested procedure, made a few tweaks.

2022-03-11T01:34:02Z

tested procedure, made a few tweaks.

Rmeden at 01:21, 11 March 2022

2022-03-11T01:21:19Z

Rmeden at 19:37, 2 October 2021

2021-10-02T19:37:56Z

Rmeden: redoing instructions for xmltv.exe

2021-10-02T19:37:02Z

redoing instructions for xmltv.exe

Rmeden at 06:57, 6 August 2014

2014-08-06T06:57:40Z

Rmeden at 06:56, 6 August 2014

2014-08-06T06:56:28Z

Rmeden: Created page with " DRAFT, NOT FINISHED == How to build XMLTV.EXE == First, let's be clear.. this is not cheap nor easy. Building XMLTV.EXE requires purchasing [http://www.activestate.co..."

2014-08-06T06:40:25Z

Created page with "** DRAFT, NOT FINISHED ** == How to build XMLTV.EXE == First, let's be clear.. this is not cheap nor easy. Building XMLTV.EXE requires purchasing [http://www.activestate.co..."

New page

** DRAFT, NOT FINISHED **

== How to build XMLTV.EXE ==

First, let's be clear.. this is not cheap nor easy. Building XMLTV.EXE requires purchasing [http://www.activestate.com/perl-dev-kit ActiveState's Perl Developer Kit] for about US$300. Most people can easily live with the Windows distribution and [http://alpha-exe.xmltv.org Alpha EXE]. Those that need to modify a script, I suggest running a [[XMLTVWindowsBuild Native Windows Build]].

For many years, this was black magic... I (Robert) had a PC where I had all the necessary modules working and I didn't touch it except to build XMLTV.EXE. That version of perl was very old.. but it kept working. Perl modules were obtained via ppm, cygwin, and more places than I could remember. It wasn't reproducible. The time had come to modernize and thanks to [[http://strawberryperl.com/ Strawberry Perl]] reproducible.

So, let's begin..

----

1. First follow the [[https://metacpan.org/pod/perldist_strawberry Procedure to Build your own Strawberry Perl]]
I used c:\strawberryport for my Portable Strawberry
I used c:\strawberry_build for my build directory
I used c:\strawberry for my output directory
I used C:\strawberryport\perl\site\lib\auto\share\dist\Perl-Dist-Strawberry\32bit-5.18.2.1.pp to build

1. Install [[http://strawberryperl.com/releases.html Strawberry Perl Portable Edition]] I put mine in c:\strawberryport

2. I recommend removing any other Perl or GCC stuff from your Path. It may not be needed, but It's safer.

3. Execute "c:\strawberryport\portableshell.bat" to open a command shell with the right environment variables.

4. Execute "perldist_strawberry"

@@ Line 8: / Line 8: @@
 # Follow instructions in [[XMLTVWindowsBuild]] to get a working xmltv under windows.
 # Install these modules
 #: cpan PAR::Packer
 #: cpan App::PP::Autolink

@@ Line 17: / Line 17: @@
 # CPAN
 # look PAR::Packer
-# edit myldr/boot.c
+# edit myldr/boot.c  (near line 198)
-#: boot.c:188
 #:   rc = my_mkdir(stmpdir, 0700);
 #:   // 2021-01-18 rmeden hack to print a message on first run

@@ Line 8: / Line 8: @@
 # Follow instructions in [[XMLTVWindowsBuild]] to get a working xmltv under windows.
 # Install these modules
-#: cpan Par::Packer
+#: cpan PAR::Packer
 #: cpan App::PP::Autolink
 # execute "gmake xmltv.exe" from your xmltv directory.
@@ Line 16: / Line 16: @@
 The first time XMLTV.EXE is executed, it will take a long time.  For my XMLTV.EXE I add modified Par::Packer to add a warning
 # CPAN
-# look Par::Packer
+# look PAR::Packer
 # edit myldr/boot.c
 #: boot.c:188

@@ Line 6: / Line 6: @@
 ----
-# Follow instructions in [XMLTVWindowsBuild] to get a working xmltv under windows.
+# Follow instructions in [[XMLTVWindowsBuild]] to get a working xmltv under windows.
 # Install these modules
 #: cpan Par::Packer

@@ Line 1: / Line 1: @@
 == How to build XMLTV.EXE ==
-First, let's be clear.. this is not cheap nor easy.  Building XMLTV.EXE requires purchasing [http://www.activestate.com/perl-dev-kit ActiveState's Perl Developer Kit] for about US$300.   Most people can easily live with the Windows distribution and [http://alpha-exe.xmltv.org Alpha EXE].  Those that need to modify a script, I suggest running a [[XMLTVWindowsBuild]] Native Windows Build.
+Previously, xmltv.exe was built using Activestate's Perl Development Kit. (about $300).  That has been discontinued, and I was able to build xmltv.exe using the free PAR::Packer module!
-−
-−
-−
-For many years, this was black magic... I (Robert) had a PC where I had all the necessary modules working and I didn't touch it except to build XMLTV.EXE.  That version of perl was very old.. but it kept working.  Perl modules were obtained via ppm, cygwin, and more places than I could remember.  It wasn't reproducible.  The time had come to modernize and thanks to [[http://strawberryperl.com/ Strawberry Perl]] reproducible.
-−
-−
-So, let's begin..
-−
 ----
-. First follow the [[https://metacpan.org/pod/perldist_strawberry  Procedure to Build your own Strawberry Perl]]
+# Follow instructions in [XMLTVWindowsBuild] to get a working xmltv under windows.
-   I used c:\strawberryport  for my Portable Strawberry
+# Install these modules
-   I used c:\strawberry_build for my build directory
+#: cpan Par::Packer
-   I used c:\strawberry for my output directory
+#: cpan App::PP::Autolink
-   I used C:\strawberryport\perl\site\lib\auto\share\dist\Perl-Dist-Strawberry\32bit-5.18.2.1.pp to build
+# execute "gmake xmltv.exe" from your xmltv directory.
-−
-. Once I had could build a stock working Strawberry Perl I was ready to modify it!
-−
-. Perl's Makefile.mk needs to be modified.  C:\strawberry_build\download  should have your official perl distribution in it. Copy the perl-5.x/win32/makefile.mk file from the perl TGZ file to c:\strawberryport\win32_makefile.mk
-−
-. Make this change to your custom win32_makefile.mk
-   old: LINK_FLAGS	= $(LINK_DBG) -L"$(INST_COREDIR)" -L"$(CCLIBDIR)"
-   new: LINK_FLAGS	= $(LINK_DBG) -L"$(INST_COREDIR)" -L"$(CCLIBDIR)" -static-libgcc -static-libstdc++ -static -lpthread
-−
-. Make your own *.pp file based on 32bit-5.18.2.1.pp. (I used xmltv.pp, the name doesn't matter)
-−
-. Edit the xmltv.pp (or whatever you called it)
-   In the "InstallPerlCore" step, there should be a "Patch" section.  Tell it to replace makefile.mk with your modified version
-   'win32_makefile.mk' => 'win32/makefile.mk',
-−
-. Build Strawberry using your custom job
-   perldist_strawberry -job xmltv.pp
-−
-. You should have a working perl at c:\strawberry!
-. Install ActiveState's Perl Dev Kit  and give it a shot (add c:\strawberry to your path)
+That's it!
-. Follow the [[XMLTVWindowsBuild]] Native Windows Build instructions to build a working XMLTV. (test it locally of course!)
+The first time XMLTV.EXE is executed, it will take a long time.  For my XMLTV.EXE I add modified Par::Packer to add a warning
 == Good Luck ==

@@ Line 3: / Line 3: @@
 == How to build XMLTV.EXE ==
-First, let's be clear.. this is not cheap nor easy.  Building XMLTV.EXE requires purchasing [http://www.activestate.com/perl-dev-kit ActiveState's Perl Developer Kit] for about US$300.   Most people can easily live with the Windows distribution and [http://alpha-exe.xmltv.org Alpha EXE].  Those that need to modify a script, I suggest running a [[XMLTVWindowsBuild Native Windows Build]].
+First, let's be clear.. this is not cheap nor easy.  Building XMLTV.EXE requires purchasing [http://www.activestate.com/perl-dev-kit ActiveState's Perl Developer Kit] for about US$300.   Most people can easily live with the Windows distribution and [http://alpha-exe.xmltv.org Alpha EXE].  Those that need to modify a script, I suggest running a [[XMLTVWindowsBuild]] Native Windows Build.
@@ Line 42: / Line 42: @@
 . Install ActiveState's Perl Dev Kit  and give it a shot (add c:\strawberry to your path)
-. Follow the [[XMLTVWindowsBuild Native Windows Build]] instructions to build a working XMLTV. (test it locally of course!)
+. Follow the [[XMLTVWindowsBuild]] Native Windows Build instructions to build a working XMLTV. (test it locally of course!)
 . If XMLTV works, and PerlApp works, you should be able to build xmltv!