Dear Gil,

The problem follows from the fact that the downloading of the documentation is 
hardcoded into a script on the Windows build machine. I changed this to use 
5.1.0 documentation already end of last year (after the release of 5.0.0) but 
when moving the build process to a new Windows build machine I copied the old 
version of the script by mistake and it went unnoticed since there are very few 
changes to the documentation :-(. This has all been corrected now and I have 
confirmed that the Windows build uses 5.1.0 documentation. The reason this is 
not visible on sourceforge is because the upload script keeps track of what 
versions have already been build, I need to delete the latest version o 
sourceforge and upload again. In any case any new commit will trigger a fresh 
rebuild that should have the correct version of the documentation also on 
Windows.

Here is an excerpt from the lates build attempt:

Remote file is newer, retrieving.

--2023-08-25 10:38:55--  
https://kumisystems.dl.sourceforge.net/project/oorexx/oorexx-docs/5.1.0beta/rexxextensions.pdf
 
<https://kumisystems.dl.sourceforge.net/project/oorexx/oorexx-docs/5.1.0beta/rexxextensions.pdf>
Connecting to kumisystems.dl.sourceforge.net 
(kumisystems.dl.sourceforge.net)|148.251.120.111|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 330878 (323K) [application/octet-stream]
Saving to: 'rexxextensions.pdf'

     0K .......... .......... .......... .......... .......... 15%  986K 0s
    50K .......... .......... .......... .......... .......... 30% 8,74M 0s
   100K .......... .......... .......... .......... .......... 46% 1,93M 0s
   150K .......... .......... .......... .......... .......... 61% 2,32M 0s
   200K .......... .......... .......... .......... .......... 77% 7,73M 0s
   250K .......... .......... .......... .......... .......... 92% 2,07M 0s
   300K .......... .......... ...                             100% 6,80M=0,1s

2023-08-25 10:38:56 (2,32 MB/s) - 'rexxextensions.pdf' saved [330878/330878]

We should amend the script to take the download path (or part of it) as input 
so it could be changed from the command line.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 26.08.2023 um 20:25 schrieb Gilbert Barmwater <gi...@bellsouth.net>:
> 
> I suspect that the problem resides with the build process for the Windows 
> installer - NSIS.  It incorporates the PDF documentation into the .exe file 
> and should be using the files from .../oorexx-docs/5.1.0beta/.  Although that 
> directory now contains new versions of the PDFs, the r12722 Windows builds do 
> not contain them.  Can someone look at how the docs are obtained for 
> inclusion into the NSIS installers?  Thanks!
> 
> On 8/16/2023 11:20 AM, Rony G. Flatscher wrote:
>> On 15.08.2023 17:46, Rony G. Flatscher wrote:
>>> Using the latest 64-bit version of ooRexx 
>>> (oorexx-5.1.0-12718.windows.x86_64.exe) I noticed that Jean Louis' commits 
>>> to the documentation [r12715] for his enhancements to the WindowsClipboard 
>>> class is not reflected in the documentation that gets installed with 
>>> r12718! Instead it seems that the GA version of the documentation gets 
>>> distributed with it.
>> 
>> It seems that since February no new documentation for 5.1.0beta got uploaded 
>> to <https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.1.0beta/>.
>> 
>> ---rony
>> 
>> 
>> 
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to