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

2021-07-19 Thread 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] MacOSX: Rexx-script to link ooRexx5

2021-07-19 Thread 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

2021-07-19 Thread 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] MacOSX: Rexx-script to link ooRexx5

2021-07-16 Thread Mark Hessling 
Yes oorexx-config is used by any package that wants to use ooRexx as
part of the package's configuration stage, prior to building the
package's binary files. All of my external function packages use it. 
The alternative is to use pkg-config, but that requires more setup on
the developer's machine.

Cheers, Mark

On 17/7/21 3:04 am, CV Bruce wrote:
> I believe oorexx-config is a Linux-ism that you can include in a make
> file to populate variables with information about where various parts
> of oorexx can be found.
> Bruce
>
> Sent by Magic!
>
>> On Jul 16, 2021, at 9:02 AM, Rick McGuire  wrote:
>>
>> 
>>
>>
>> On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson > > wrote:
>>
>> Dear Rony, just some thoughts.
>>
>> I did not run the script (yet) but is the intention to create
>> symlinks to /usr/local so as to avoid the need to modify the path?
>>
>> If the 2nd part is creating the steps necessary to „unlink" why
>> do you not create a shell script of those lines? After all the
>> user will not realize at the time of installation (linking) that
>> he might need them (much) later during an uninstall? (unlinking).
>> It would appear possible to create a static unlink script for the
>> default (/Applications/ooRexx5/bin,lib <-> /usr/local/bin,lib
>>
>> Can we hear from the developers what the skipped files (
>> callrexx1, callrexx2, libwpipe1.dylib, libwpipe2.dylib,
>> libwpipe3.dylib and oorexx-config.) are for? Can they be safely
>> removed from the installation on macOS? How does one go about it?
>>
>>
>> I'm not sure what oorexx-config is, but the others are the compiled
>> sample files. 
>>
>> Rick 
>>
>>
>> It is possible to delete these files from the (auto-generated)
>> script building the dmg in a post-process but that would be the
>> ugly way. IMO we should locate the places in CMakelists.txt where
>> those files are copied and fix the problem there.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>>
>>
>>
>>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher
>>> mailto:rony.flatsc...@wu.ac.at>>:
>>>
>>> Those who use ooRexx5 from Sourceforge on a Mac and who have
>>> followed the instructions will have
>>> ooRexx in "/Applications/ooRexx5".
>>>
>>> The enclosed Rexx script will create the link and remove
>>> commands that will make ooRexx5 available
>>> systemwide. Run it and copy & paste the output to create the
>>> links or remove them.
>>>
>>> If you have ooRexx5 installed somewhere else, adjust the script
>>> accordingly.
>>>
>>> ---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
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

-- 

* Mark Hessling, m...@rexx.org http://www.rexx.org/
* Author of THE, a Free XEDIT/KEDIT editor and, Rexx/SQL, Rexx/CURL, etc.
* Maintainer of Regina Rexx interpreter
* Use Rexx? join the Rexx Language Association: https://www.rexxla.org/ 


___
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

2021-07-16 Thread P.O. Jonsson 
> 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). 

I only use what make install produces (I merely pack the installation) so it is 
not me that is using the information in the wrong way, ANY installation of 
ooRexx for macOS will have these defects.

Let´s hunt them down (in cmakelists.txt) and fix them there.___
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

2021-07-16 Thread CV Bruce 
I believe oorexx-config is a Linux-ism that you can include in a make file to 
populate variables with information about where various parts of oorexx can be 
found.
Bruce

Sent by Magic!

> On Jul 16, 2021, at 9:02 AM, Rick McGuire  wrote:
> 
> 
> 
> 
>> On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:
>> Dear Rony, just some thoughts.
>> 
>> I did not run the script (yet) but is the intention to create symlinks to 
>> /usr/local so as to avoid the need to modify the path?
>> 
>> If the 2nd part is creating the steps necessary to „unlink" why do you not 
>> create a shell script of those lines? After all the user will not realize at 
>> the time of installation (linking) that he might need them (much) later 
>> during an uninstall? (unlinking). It would appear possible to create a 
>> static unlink script for the default (/Applications/ooRexx5/bin,lib <-> 
>> /usr/local/bin,lib
>> 
>> Can we hear from the developers what the skipped files ( callrexx1, 
>> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and 
>> oorexx-config.) are for? Can they be safely removed from the installation on 
>> macOS? How does one go about it?
> 
> I'm not sure what oorexx-config is, but the others are the compiled sample 
> files. 
> 
> Rick 
>> 
>> It is possible to delete these files from the (auto-generated) script 
>> building the dmg in a post-process but that would be the ugly way. IMO we 
>> should locate the places in CMakelists.txt where those files are copied and 
>> fix the problem there.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>> 
>> 
>> 
>>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher :
>>> 
>>> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
>>> instructions will have
>>> ooRexx in "/Applications/ooRexx5".
>>> 
>>> The enclosed Rexx script will create the link and remove commands that will 
>>> make ooRexx5 available
>>> systemwide. Run it and copy & paste the output to create the links or 
>>> remove them.
>>> 
>>> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
>>> 
>>> ---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
___
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

2021-07-16 Thread Rony G. Flatscher 
Dear P.O.,

it is just intended to help those who wish to make ooRexx globally available to 
learn the ln- and
rm-commands to do so. It will not be done automatically, one would need to copy 
the commands and
then paste them to execute them.  :)

Even if someone would forget deleting the symbolic links, they would not do any 
harm. To remove all
broken symbolic links, one could use one of the suggestions from 
,
 like:

sudo find /usr/local -type l -exec test ! -e {} \; -delete


On 16.07.2021 17:40, P.O. Jonsson wrote:
> I did not run the script (yet) but is the intention to create symlinks to 
> /usr/local so as to
> avoid the need to modify the path?

The script only creates the commands it does not run them. In order to execute 
them you would need
to copy the output in the Terminal to the clipboard and paste the commands from 
the clipboard to
have them execute.

> If the 2nd part is creating the steps necessary to „unlink" why do you not 
> create a shell script
> of those lines? After all the user will not realize at the time of 
> installation (linking) that he
> might need them (much) later during an uninstall? (unlinking). It would 
> appear possible to create
> a static unlink script for the default (/Applications/ooRexx5/bin,lib <-> 
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1, 
> callrexx2, libwpipe1.dylib,
> libwpipe2.dylib, libwpipe3.dylib and oorexx-config.) are for? Can they be 
> safely removed from the
> installation on macOS? How does one go about it?

Rexx comes with samples that demonstrate how to use C to interact with Rexx, on 
Windows you would
find them in "ooRexx\samples\api". So they can be safely left out for the bare 
bone interpreter.

---rony

>
>> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher > >:
>>
>> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
>> instructions will have
>> ooRexx in "/Applications/ooRexx5".
>>
>> The enclosed Rexx script will create the link and remove commands that will 
>> make ooRexx5 available
>> systemwide. Run it and copy & paste the output to create the links or remove 
>> them.
>>
>> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
>>
>> ---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

2021-07-16 Thread 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).

Rick

On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:

> Dear Rony, just some thoughts.
>
> I did not run the script (yet) but is the intention to create symlinks to
> /usr/local so as to avoid the need to modify the path?
>
> If the 2nd part is creating the steps necessary to „unlink" why do you not
> create a shell script of those lines? After all the user will not realize
> at the time of installation (linking) that he might need them (much) later
> during an uninstall? (unlinking). It would appear possible to create a
> static unlink script for the default (/Applications/ooRexx5/bin,lib <->
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1,
> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and
> oorexx-config.) are for? Can they be safely removed from the installation
> on macOS? How does one go about it?
>
> It is possible to delete these files from the (auto-generated) script
> building the dmg in a post-process but that would be the ugly way. IMO we
> should locate the places in CMakelists.txt where those files are copied and
> fix the problem there.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher  >:
>
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the
> instructions will have
> ooRexx in "/Applications/ooRexx5".
>
> The enclosed Rexx script will create the link and remove commands that
> will make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or
> remove them.
>
> If you have ooRexx5 installed somewhere else, adjust the script
> accordingly.
>
> ---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

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

2021-07-16 Thread Rick McGuire 
On Fri, Jul 16, 2021 at 11:41 AM P.O. Jonsson  wrote:

> Dear Rony, just some thoughts.
>
> I did not run the script (yet) but is the intention to create symlinks to
> /usr/local so as to avoid the need to modify the path?
>
> If the 2nd part is creating the steps necessary to „unlink" why do you not
> create a shell script of those lines? After all the user will not realize
> at the time of installation (linking) that he might need them (much) later
> during an uninstall? (unlinking). It would appear possible to create a
> static unlink script for the default (/Applications/ooRexx5/bin,lib <->
> /usr/local/bin,lib
>
> Can we hear from the developers what the skipped files ( callrexx1,
> callrexx2, libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and
> oorexx-config.) are for? Can they be safely removed from the installation
> on macOS? How does one go about it?
>

I'm not sure what oorexx-config is, but the others are the compiled sample
files.

Rick

>
> It is possible to delete these files from the (auto-generated) script
> building the dmg in a post-process but that would be the ugly way. IMO we
> should locate the places in CMakelists.txt where those files are copied and
> fix the problem there.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher  >:
>
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the
> instructions will have
> ooRexx in "/Applications/ooRexx5".
>
> The enclosed Rexx script will create the link and remove commands that
> will make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or
> remove them.
>
> If you have ooRexx5 installed somewhere else, adjust the script
> accordingly.
>
> ---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

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

2021-07-16 Thread P.O. Jonsson 
Dear Rony, just some thoughts.

I did not run the script (yet) but is the intention to create symlinks to 
/usr/local so as to avoid the need to modify the path?

If the 2nd part is creating the steps necessary to „unlink" why do you not 
create a shell script of those lines? After all the user will not realize at 
the time of installation (linking) that he might need them (much) later during 
an uninstall? (unlinking). It would appear possible to create a static unlink 
script for the default (/Applications/ooRexx5/bin,lib <-> /usr/local/bin,lib

Can we hear from the developers what the skipped files ( callrexx1, callrexx2, 
libwpipe1.dylib, libwpipe2.dylib, libwpipe3.dylib and oorexx-config.) are for? 
Can they be safely removed from the installation on macOS? How does one go 
about it?

It is possible to delete these files from the (auto-generated) script building 
the dmg in a post-process but that would be the ugly way. IMO we should locate 
the places in CMakelists.txt where those files are copied and fix the problem 
there.

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



> Am 16.07.2021 um 17:09 schrieb Rony G. Flatscher :
> 
> Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
> instructions will have
> ooRexx in "/Applications/ooRexx5".
> 
> The enclosed Rexx script will create the link and remove commands that will 
> make ooRexx5 available
> systemwide. Run it and copy & paste the output to create the links or remove 
> them.
> 
> If you have ooRexx5 installed somewhere else, adjust the script accordingly.
> 
> ---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] MacOSX: Rexx-script to link ooRexx5

2021-07-16 Thread Rony G. Flatscher 
Those who use ooRexx5 from Sourceforge on a Mac and who have followed the 
instructions will have
ooRexx in "/Applications/ooRexx5".

The enclosed Rexx script will create the link and remove commands that will 
make ooRexx5 available
systemwide. Run it and copy & paste the output to create the links or remove 
them.

If you have ooRexx5 installed somewhere else, adjust the script accordingly.

---rony


#!/usr/bin/env rexx
-- rgf, 2021-07-15: link/remove '/Applications/ooRexx5' to/from /usr/local/{bin|lib}
ooRexxDir="/Applications/ooRexx5/"
targetDir   ="/usr/local/"

say "# remove quarantine attribute from directory and its content, if necessary:"
say "sudo xattr -r -d com.apple.quarantine /Applications/ooRexx5"
say

do dir over "bin", "lib"
   srcDir=ooRexxDir || dir
   tgtDir=targetDir || dir
   say "# linking files from:" srcDir "to:" tgtDir
   call sysFileTree srcDir"/*", "files.", "FO"
   w=0 -- determine longest string
   do i=1 to files.0
   w=max(w,length(files.i))
   end
   do i=1 to files.0
  fn=filespec("name",files.i)
  if fn~startsWith("callrexx") | fn~startsWith("libwpipe") then iterate
  say "sudo ln -sfv" (files.i)~left(w) tgtDir"/"fn
   end
   say
end

say
say "# remove files"
do dir over "bin", "lib"
   srcDir=ooRexxDir || dir
   tgtDir=targetDir || dir
   say "# remove files from:" tgtDir
   call sysFileTree srcDir"/*", "files.", "FO"
   w=0 -- determine longest string
   do i=1 to files.0
   w=max(w,length(files.i))
   end
   do i=1 to files.0
  fn=filespec("name",files.i)
  if fn~startsWith("callrexx") | fn~startsWith("libwpipe") then iterate
  say "sudo rm -f" tgtDir"/"fn
   end
   say
end






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