Re: [Oorexx-devel] Building the Documentation for ooRexx

[Gil Barmwater]

I just had a quick look at setup.rex and noted two problems.  The first 
is that the program is trying to download fop-2.4 while the current 
version is 2.6.  The second is that the "mirror" used to obtain the zip 
file is now "refusing" connections.  So I will do some debugging as time 
permits and update SF with a working setup.rex.  Thanks again for 
letting us know about this issue.


Gil

On 7/19/2021 8:49 AM, Gil Barmwater wrote:

On 7/19/2021 7:32 AM, Jean Louis Faucher wrote:
Just to share that I was able to build all the pdf/html files with 
MacPorts under MacOs High Sierra.

My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different 
for MacPorts.


I switched to Gil’s toolkit because rexxpg and rexxref no longer 
build with Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style 
Sheets” in sources.txt gives interesting informations.


I tested the setup under Windows.


Not having run setup in quite a while, I'll take a look at it later 
today and report back.  Thanks for the "heads up"!


Gil B.


The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with 
https://archive.apache.org/dist/xmlgraphics/fop/binaries/ 




Jean-Louis



On 19 May 2020, at 19:56, P.O. Jonsson > wrote:


Dear developers,

I have ported Gils tools for building the documentation to macOS and 
to Ubuntu Linux.


I have followed Gil´s logics as far as I could and the names of the 
scripts are in essence the same and the way to use them as well.


For macOS I could make the build run on local files so it is just as 
fast as the Windows version. For Ubuntu I failed this so the Ubuntu 
version rely on an internet connection and is substantially slower. 
But the output for PDF and HTML is (as far as I can judge) identical 
for all three build processes. So at least this constitutes a proof 
of concept for building on all platforms.


Different from on Windows it was not possible for me to make a 
self-contained version of the build tools, neither on macOS nor on 
Linux. I have set out what tools need to be installed in a file 
WhatISHere.txt and explained how to install them + I have  briefly 
explained he build process. Since the readme for Windows is so 
complete I refer to it for the deeper understanding of the build 
process.


Further I have set up a Dropbox folder Jenkinsshare 
 where 
I have put zipped copies of the scripts. To try them out copy either 
one o*f oorexxdocs-macOS.zip* or *oorexxdocs-Ubuntu.zip* to a local 
folder, unzip and follow the instructions in *WhatIsHere.txt*. 
Feedback is welcome.


Jenkinsshare 
 also 
contains 3 complete sets of the documentation (Win/macOS/Ubuntu 
Linux), please have a look and let us know what you think.


Jenkinsshare is intended as a platform for sharing files during 
development. Gil, myself and Rony use it for sharing work on the 
documentation. JenkinsShare is owned by Jenkins and present on the 
master and my Jenkins slaves. Any developer who wants permanent 
access can send me a mail and I will set it up. It is NOT a 
replacement for SVN/Sourceforge, just a quick way of sharing data. 
Since the folder is shared by many I ask you to be moderate when 
putting data there.


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



___
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
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rick McGuire]

Are you checking for those files after a build and a make install, or are
you checking for an install from a built installer (eg, rpm, deb, windows
installer)? Those files get built and I'm guessing that a make install
probably copies them. They are not specified for inclusion in the package
builds in CMakeLists.txt. If your installer is just using the results of
make install to build the package, then it is not using the install
information built by CMakeLists.txt. CMakeLists.txt uses a series of
install() statements to identify which build artifacts are to be installed
and where they should be installed. This creates a file in the cmake
directory called cmake_install.cmake which is a cmake script that
identifies what files are to be installed (and what component they are part
of). These scripts are used for the various CPack options and also by the
Windows NSIS installer.  The compiled samples like callrxnt are not
included in the installation definitions.

Rick

Rick

On Mon, Jul 19, 2021 at 11:14 AM P.O. Jonsson  wrote:

> Ok, so I checked rev 12280 on some Linux installations (Raspberry Pi,
> Debian, Linux Mint, Fedora, CentOS) and they all show the same 2 CallRexx
> and 3 Libwpipe files in the installed /bin directory, so it is not just
> macOS/Darwin thingy, it is a generic fault (if it is a fault) for the
> *nixes.
>
> I could not find oorexx-config in ANY installation so I guess this is a
> local file on Rony´s computer, maybe from the „fat binary“ exercise? It is
> not present in any of the installations I looked at. None.
>
> Windows is entirely different from the rest of the installations and there
> are some Callrxnt.exe etc files in the installed ooRexx (I only looked at
> the 64-bit version) but I must assume that they are intentionally there
> since the Windows installer is *properly* using CMakelists.txt, right?
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 16.07.2021 um 18:04 schrieb Rick McGuire :
>
> btw, if you were properly using the information from CMake.txt to build
> the .dmg, you would not be having this problem, since all of the install()
> statements identify which elements of the build should go where. That
> information is used by all of the other installer types (including the
> Windows one, which is done without CMake builtin CPack support).
>
>
> ___
> 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

Re: [Oorexx-devel] MaxOS: Java can load libBSF4ooRexx.dylib, ooRexx cannot

[Rony G. Flatscher]

Bonsoir Jean-Louis,

today I finished up a new version of BSF4ooRexx that should work in this 
use-case. You can get it
from
<https://sourceforge.net/projects/bsf4oorexx/files/beta/20200928/BSF4ooRexx_install_v641-20210719-beta.zip/download>.
(This version got tested against MacOS, Linux and Windows.)

If you test this version in your environment then please let me know of any 
difficulties or problems
that you encounter. (This version of BSF4ooRexx is still supposed to be usable 
against ooRexx 4.1
and higher, however 5.0 is *strongly* advised due to its stable 
multithreadingness. For that reason
some JavaFX samples will deny being run on ooRexx prior to 5.0. This is another 
reason for me to ask
for a release version of ooRexx 5.0 beta *as is*, as it is much stabler, faster 
and powerful than
any earlier version of ooRexx.)

---rony


On 18.07.2021 00:02, Jean Louis Faucher wrote:
> Gute nacht Rony
>
> I have an atypical configuration where I use DYLD_LIBRARY_PATH to locate the 
> BSF4OORexx library.
> This is because I don’t “install” BSF4OORexx, I just unzip the delivery, copy 
> and rename the
> libraries to bsf4oorex/install/64
> With this configuration, your test cases are working (not saying this is the 
> solution).
>
>
> If I don’t set DYLD_LIBRARY_PATH, I get the same error than yours.
>
> I compared the output of the next command in both cases
> DYLD_PRINT_LIBRARIES="1" DYLD_PRINT_APIS="1" rexx -e "call bsf.cls”
>
> In the working session:
> dlopen(librexxapi.dylib, 0x0001)
>   dlopen(librexxapi.dylib) ==> 0x10936da50
> dlopen(libBSF4ooRexx.dylib, 0x0001)
> dyld: loaded:
> /local/rexx/bsf4oorexx/BSF4ooRexx_install_v641-20210715-beta/bsf4oorexx/install/64/libBSF4ooRexx.dylib
> dyld: loaded:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre/lib/server/libjvm.dylib
> dyld: loaded: /usr/lib/libstdc++.6.0.9.dylib
>
> In the not working session:
> dlopen(librexxapi.dylib, 0x0001)
>   dlopen(librexxapi.dylib) ==> 0x10dd4a990
> dlopen(libBSF4ooRexx.dylib, 0x0001)
>   dlopen() failed, error: 'dlopen(libBSF4ooRexx.dylib, 1): image not found'
> dlopen(/usr/lib/libBSF4ooRexx.dylib, 0x0001)
>   dlopen() failed, error: 'dlopen(/usr/lib/libBSF4ooRexx.dylib, 1): image not 
> found'
>    919 *-* ::routine xBSF                   PUBLIC   EXTERNAL "LIBRARY 
> BSF4ooRexx BSF            
>     "
>      1 *-* call bsf.cls
> Error 98 running 
> /local/rexx/bsf4oorexx/BSF4ooRexx_install_v641-20210715-beta/bsf4oorexx/BSF.CLS
> line 919:  Execution error.
> Error 98.903:  Unable to load library "BSF4ooRexx".
>
> I find "/usr/lib” in one file:
> SysLibrary.cpp
>
>     // try loading directly
>     libraryHandle = dlopen(nameBuffer, RTLD_LAZY);
>     // if not found, then try from /usr/lib
>     if (libraryHandle == NULL)
>     {
>         sprintf(nameBuffer, "/usr/lib/lib%s%s", name, ORX_SHARED_LIBRARY_EXT);
>         libraryHandle = dlopen(nameBuffer, RTLD_LAZY);
>
> The part to investigate is how to make the first dlopen work without using 
> DYLD_LIBRARY_PATH:
> If I put libBSF4ooRexx.dylib in the lib folder of oorexx then it works 
> (RPATH).
> If I put libBSF4ooRexx.dylib in the current directory then it works (see man 
> dlopen).
> I don’t know if other solutions are possible for the first dlopen
>
> The other solution could to add “/usr/local/lib” as 2nd fallback.
> But that brings the question of order.
> Maybe a more general solution would be to use an environment variable like 
> REXX_LIBRARY_PATH.
> We have already REXX_PATH for locating the rexx files.
>
>
> Jean-Louis
>
>> On 17 Jul 2021, at 21:56, Rony G. Flatscher > <mailto:rony.flatsc...@wu.ac.at>> wrote:
>>
>> On MacOSX the BSF4ooRexx library is named "libBSF4ooRexx.dylib".
>>
>> Testing the changes in the BSF4ooRexx installation scripts and then testing 
>> the resulting
>> installations surfaced a problem on MacOSX: libBSF4ooRexx.dylib can be 
>> loaded via Java and used
>> successfully.
>>
>> However, loading "libBSF4ooRexx.dylib" via ooRexx is not successful. To be 
>> precise, the
>>
>> ::routine xbsf PUBLIC EXTERNAL "LIBRARY BSF4ooRexx BSF"
>>
>> fails with the execution error:
>>
>> Error 98.903: Unable to load library "BSF4ooRexx".
>>
>> Here two rexxtry.rex sessions, the first one is run with "rexxj.sh 
>> /usr/local/bin/rexxtry.rex"
>> which loads a Java program that will load the BSF4ooRexx library to then 
>> execute
>> /usr/local/bin/rexxtry.rex. This is followed by a "rexx rexxtry.rex" session 

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[Rony G. Flatscher]

On 19.07.2021 17:13, P.O. Jonsson wrote:
> Ok, so I checked rev 12280 on some Linux installations (Raspberry Pi, Debian, 
> Linux Mint, Fedora,
> CentOS) and they all show the same 2 CallRexx and 3 Libwpipe files in the 
> installed /bin
> directory, so it is not just macOS/Darwin thingy, it is a generic fault (if 
> it is a fault) for the
> *nixes.
>
> I could not find oorexx-config in ANY installation so I guess this is a local 
> file on Rony´s
> computer, maybe from the „fat binary“ exercise? It is not present in any of 
> the installations I
> looked at. None.

Yes, now I recall: this was a file that Enrico sent with a minimized (cleansed) 
version of the
Makefile to create a fat BSF4ooRexx library. (Actually, I updated the older 
Makefile and use that as
it does not have a dependency on oorexx-config. As I rarely have to compile 
BSF4ooRexx.cc I keep
forgetting such dependencies myself which causes some time-losses and 
frustrations on my side on a
regular basis. :) )

> Windows is entirely different from the rest of the installations and there 
> are some Callrxnt.exe
> etc files in the installed ooRexx (I only looked at the 64-bit version) but I 
> must assume that
> they are intentionally there since the Windows installer is /properly/ using 
> CMakelists.txt, right?

Whenever an overhaul of CMake is in the works one thing I would like to propose 
is to also allow for
creating a "stick" version of the ooRexx interpreter and make that downloadable 
as well. It would
have the benefit that anyone interested can download it and get it running on 
the target system
without installation. (A first excercise in that direction was done for last 
year's Rexx symposium.
It would use an already installed version of ooRexx and with the help of a 
little Rexx script create
a stick version of the Windows, Linux and MacOS version.)

---rony

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

Re: [Oorexx-devel] MacOSX: Rexx-script to link ooRexx5

[P.O. Jonsson]

Ok, so I checked rev 12280 on some Linux installations (Raspberry Pi, Debian, 
Linux Mint, Fedora, CentOS) and they all show the same 2 CallRexx and 3 
Libwpipe files in the installed /bin directory, so it is not just macOS/Darwin 
thingy, it is a generic fault (if it is a fault) for the *nixes.

I could not find oorexx-config in ANY installation so I guess this is a local 
file on Rony´s computer, maybe from the „fat binary“ exercise? It is not 
present in any of the installations I looked at. None.

Windows is entirely different from the rest of the installations and there are 
some Callrxnt.exe etc files in the installed ooRexx (I only looked at the 
64-bit version) but I must assume that they are intentionally there since the 
Windows installer is properly using CMakelists.txt, right?

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



> Am 16.07.2021 um 18:04 schrieb Rick McGuire :
> 
> btw, if you were properly using the information from CMake.txt to build the 
> .dmg, you would not be having this problem, since all of the install() 
> statements identify which elements of the build should go where. That 
> information is used by all of the other installer types (including the 
> Windows one, which is done without CMake builtin CPack support). 

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

Re: [Oorexx-devel] Building the Documentation for ooRexx

[Gil Barmwater]

On 7/19/2021 7:32 AM, Jean Louis Faucher wrote:
Just to share that I was able to build all the pdf/html files with 
MacPorts under MacOs High Sierra.

My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different for 
MacPorts.


I switched to Gil’s toolkit because rexxpg and rexxref no longer build 
with Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style 
Sheets” in sources.txt gives interesting informations.


I tested the setup under Windows.


Not having run setup in quite a while, I'll take a look at it later 
today and report back.  Thanks for the "heads up"!


Gil B.


The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with 
https://archive.apache.org/dist/xmlgraphics/fop/binaries/ 




Jean-Louis



On 19 May 2020, at 19:56, P.O. Jonsson > wrote:


Dear developers,

I have ported Gils tools for building the documentation to macOS and 
to Ubuntu Linux.


I have followed Gil´s logics as far as I could and the names of the 
scripts are in essence the same and the way to use them as well.


For macOS I could make the build run on local files so it is just as 
fast as the Windows version. For Ubuntu I failed this so the Ubuntu 
version rely on an internet connection and is substantially slower. 
But the output for PDF and HTML is (as far as I can judge) identical 
for all three build processes. So at least this constitutes a proof 
of concept for building on all platforms.


Different from on Windows it was not possible for me to make a 
self-contained version of the build tools, neither on macOS nor on 
Linux. I have set out what tools need to be installed in a file 
WhatISHere.txt and explained how to install them + I have  briefly 
explained he build process. Since the readme for Windows is so 
complete I refer to it for the deeper understanding of the build process.


Further I have set up a Dropbox folder Jenkinsshare 
 where 
I have put zipped copies of the scripts. To try them out copy either 
one o*f oorexxdocs-macOS.zip* or *oorexxdocs-Ubuntu.zip* to a local 
folder, unzip and follow the instructions in *WhatIsHere.txt*. 
Feedback is welcome.


Jenkinsshare 
 also 
contains 3 complete sets of the documentation (Win/macOS/Ubuntu 
Linux), please have a look and let us know what you think.


Jenkinsshare is intended as a platform for sharing files during 
development. Gil, myself and Rony use it for sharing work on the 
documentation. JenkinsShare is owned by Jenkins and present on the 
master and my Jenkins slaves. Any developer who wants permanent 
access can send me a mail and I will set it up. It is NOT a 
replacement for SVN/Sourceforge, just a quick way of sharing data. 
Since the folder is shared by many I ask you to be moderate when 
putting data there.


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



___
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

Re: [Oorexx-devel] Building the Documentation for ooRexx

[Jean Louis Faucher]

Just to share that I was able to build all the pdf/html files with MacPorts 
under MacOs High Sierra.
My version of FOP is old (v1.1) but it worked.
P.O., thank you for the very clear instructions, it was easy to follow.
It took 1 hour 10 min on my old laptop Mid 2010.

I had just to put in comment this line:
export XML_CATALOG_FILES=/usr/local/etc/xml/catalog
in doc2fo.sh and doc2html.sh
because the variable is already defined and its value is different for MacPorts.

I switched to Gil’s toolkit because rexxpg and rexxref no longer build with 
Publican (at least for me).
Gil, thank you for this toolkit. The section "DocBook DTD and Style Sheets” in 
sources.txt gives interesting informations.

I tested the setup under Windows.
The URL for FOP  seems not working, don’t know if it”s temporary.
I replaced it with https://archive.apache.org/dist/xmlgraphics/fop/binaries/


Jean-Louis



> On 19 May 2020, at 19:56, P.O. Jonsson  wrote:
> 
> Dear developers,
> 
> I have ported Gils tools for building the documentation to macOS and to 
> Ubuntu Linux.
> 
> I have followed Gil´s logics as far as I could and the names of the scripts 
> are in essence the same and the way to use them as well.
> 
> For macOS I could make the build run on local files so it is just as fast as 
> the Windows version. For Ubuntu I failed this so the Ubuntu version rely on 
> an internet connection and is substantially slower. But the output for PDF 
> and HTML is (as far as I can judge) identical for all three build processes. 
> So at least this constitutes a proof of concept for building on all platforms.
> 
> Different from on Windows it was not possible for me to make a self-contained 
> version of the build tools, neither on macOS nor on Linux. I have set out 
> what tools need to be installed in a file WhatISHere.txt and explained how to 
> install them + I have  briefly explained he build process. Since the readme 
> for Windows is so complete I refer to it for the deeper understanding of the 
> build process.
> 
> Further I have set up a Dropbox folder Jenkinsshare 
>  
> where I have put zipped copies of the scripts. To try them out copy either 
> one of oorexxdocs-macOS.zip or oorexxdocs-Ubuntu.zip to a local folder, unzip 
> and follow the instructions in WhatIsHere.txt. Feedback is welcome.
> 
> Jenkinsshare 
>  
> also contains 3 complete sets of the documentation (Win/macOS/Ubuntu Linux), 
> please have a look and let us know what you think.
> 
> Jenkinsshare is intended as a platform for sharing files during development. 
> Gil, myself and Rony use it for sharing work on the documentation. 
> JenkinsShare is owned by Jenkins and present on the master and my Jenkins 
> slaves. Any developer who wants permanent access can send me a mail and I 
> will set it up. It is NOT a replacement for SVN/Sourceforge, just a quick way 
> of sharing data. Since the folder is shared by many I ask you to be moderate 
> when putting data there.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> ___
> 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