Request to change default compiler to ecj in windows script NetRexxC.bat
Locked
Request to change default compiler to ecj in windows script NetRexxC.bat
 
|
René and other interested parties --
Due to some recent issues with classpaths and NetRexx translator scripts (such as nrc) that have been reported on the list, I would like to slightly modify the batch script (NetRexxC.bat) which we provide for Windows systems. This change will make the Eclipse compiler the default compiler when available. The Windows environment variable "netrexx_java" that we currently use in the script to pass a compiler selection will still override the default just as it now does. However changing the default compiler to ecj allows the script to automatically add module NetRexxF.jar to the Java classpath and hopefully eliminates many of the problems with locating a Java compiler encountered by those not familiar with use of the classpath options and the environment variable. NetRexxF.jar is automatically located from the sibling \lib directory if not already found in the classpath. The net effect of this change is that adding the NetRexx "\bin" directory to the Windows PATH will be ALL that is needed to compile and run NetRexx programs for anyone using the "nrc" or "NetRexxC" scripts. Non Windows users are not affected. If NetRexxC.bat is moved or copied to a PATH directory, then NetRexxF.jar must still be added to the classpath just as previously required in order to be located. Current usage is not affected by this change. If there are no objections, I will add this change to the repository trunk. In order for members to test it before the 3.03GA release, it will be necessary to refresh the RC2 distribution or build a new RC3 distribution and publish it. Some changes to the QuickStart Guide installation section (3.4) may be needed. These three common steps to setup use of NetRexx with ecj from script nrc can now be reduced to just the first step: 1) Add NetRexx \bin directory to Windows PATH 2) Add NetRexxF.jar to the Java CLASSPATH 3) Create netrexx_java environment variable with value -Dnrx.compiler=ecj -- Kermit Kiser _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Kermit,
I agree. If you check it in I will put a RC3 online tomorrow. Best regards, René. On 31 mei 2014, at 20:42, Kermit Kiser <[hidden email]> wrote: > René and other interested parties -- > > Due to some recent issues with classpaths and NetRexx translator scripts (such as nrc) that have been reported on the list, I would like to slightly modify the batch script (NetRexxC.bat) which we provide for Windows systems. This change will make the Eclipse compiler the default compiler when available. > > The Windows environment variable "netrexx_java" that we currently use in the script to pass a compiler selection will still override the default just as it now does. However changing the default compiler to ecj allows the script to automatically add module NetRexxF.jar to the Java classpath and hopefully eliminates many of the problems with locating a Java compiler encountered by those not familiar with use of the classpath options and the environment variable. NetRexxF.jar is automatically located from the sibling \lib directory if not already found in the classpath. > > The net effect of this change is that adding the NetRexx "\bin" directory to the Windows PATH will be ALL that is needed to compile and run NetRexx programs for anyone using the "nrc" or "NetRexxC" scripts. Non Windows users are not affected. If NetRexxC.bat is moved or copied to a PATH directory, then NetRexxF.jar must still be added to the classpath just as previously required in order to be located. Current usage is not affected by this change. > > If there are no objections, I will add this change to the repository trunk. In order for members to test it before the 3.03GA release, it will be necessary to refresh the RC2 distribution or build a new RC3 distribution and publish it. Some changes to the QuickStart Guide installation section (3.4) may be needed. These three common steps to setup use of NetRexx with ecj from script nrc can now be reduced to just the first step: > > 1) Add NetRexx \bin directory to Windows PATH > 2) Add NetRexxF.jar to the Java CLASSPATH > 3) Create netrexx_java environment variable with value -Dnrx.compiler=ecj > > -- Kermit Kiser > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by Kermit Kiser
That sounds like a good thing to me Kermit, but I'm hardly the expert
on these things. What I don't understand is that every other software package I've installed seems to add a directory or two to my PATH variable, so why aren't we? "Best practices" is a moving target, and I'm not happy with PATH-cruft, but it would seem to be a reasonable "get the user up and running" approach. With proper documentation we could offer alternative installation schemes. Or is this a matter of (vainly) trying to craft a single installation process for all possible platforms? -Chip- On 5/31/2014 2:42 PM Kermit Kiser said: > René and other interested parties -- > > Due to some recent issues with classpaths and NetRexx translator > scripts (such as nrc) that have been reported on the list, I would > like to slightly modify the batch script (NetRexxC.bat) which we > provide for Windows systems. This change will make the Eclipse > compiler the default compiler when available. > > The Windows environment variable "netrexx_java" that we currently use > in the script to pass a compiler selection will still override the > default just as it now does. However changing the default compiler to > ecj allows the script to automatically add module NetRexxF.jar to the > Java classpath and hopefully eliminates many of the problems with > locating a Java compiler encountered by those not familiar with use of > the classpath options and the environment variable. NetRexxF.jar is > automatically located from the sibling \lib directory if not already > found in the classpath. > > The net effect of this change is that adding the NetRexx "\bin" > directory to the Windows PATH will be ALL that is needed to compile > and run NetRexx programs for anyone using the "nrc" or "NetRexxC" > scripts. Non Windows users are not affected. If NetRexxC.bat is moved > or copied to a PATH directory, then NetRexxF.jar must still be added > to the classpath just as previously required in order to be located. > Current usage is not affected by this change. > > If there are no objections, I will add this change to the repository > trunk. In order for members to test it before the 3.03GA release, it > will be necessary to refresh the RC2 distribution or build a new RC3 > distribution and publish it. Some changes to the QuickStart Guide > installation section (3.4) may be needed. These three common steps to > setup use of NetRexx with ecj from script nrc can now be reduced to > just the first step: > > 1) Add NetRexx \bin directory to Windows PATH > 2) Add NetRexxF.jar to the Java CLASSPATH > 3) Create netrexx_java environment variable with value -Dnrx.compiler=ecj > > -- Kermit Kiser > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Chip,
it is Java so we would be short of the target if the installer is platform dependent. I agree with Kermit that the platform dependent startup script is the right place for this change. I would think we should not add things to peoples paths - it is the gliding slope of registries, signed installers, etc. Have a separate script do that and and have that asking for permission would be my limit. Also, the jar of worms that is opened with that - bash or tcsh or zsh, .profile or .bash_profile or .tcshrc, cmd.exe or charms, quicklinks, cygwin, uwin, PowerShell, can you tell me which path? best regards, René. On 31 mei 2014, at 21:04, Chip Davis <[hidden email]> wrote: > That sounds like a good thing to me Kermit, but I'm hardly the expert on these things. What I don't understand is that every other software package I've installed seems to add a directory or two to my PATH variable, so why aren't we? > > "Best practices" is a moving target, and I'm not happy with PATH-cruft, but it would seem to be a reasonable "get the user up and running" approach. With proper documentation we could offer alternative installation schemes. > > Or is this a matter of (vainly) trying to craft a single installation process for all possible platforms? > > -Chip- > > On 5/31/2014 2:42 PM Kermit Kiser said: >> René and other interested parties -- >> >> Due to some recent issues with classpaths and NetRexx translator >> scripts (such as nrc) that have been reported on the list, I would >> like to slightly modify the batch script (NetRexxC.bat) which we >> provide for Windows systems. This change will make the Eclipse >> compiler the default compiler when available. >> >> The Windows environment variable "netrexx_java" that we currently use >> in the script to pass a compiler selection will still override the >> default just as it now does. However changing the default compiler to >> ecj allows the script to automatically add module NetRexxF.jar to the >> Java classpath and hopefully eliminates many of the problems with >> locating a Java compiler encountered by those not familiar with use of >> the classpath options and the environment variable. NetRexxF.jar is >> automatically located from the sibling \lib directory if not already >> found in the classpath. >> >> The net effect of this change is that adding the NetRexx "\bin" >> directory to the Windows PATH will be ALL that is needed to compile >> and run NetRexx programs for anyone using the "nrc" or "NetRexxC" >> scripts. Non Windows users are not affected. If NetRexxC.bat is moved >> or copied to a PATH directory, then NetRexxF.jar must still be added >> to the classpath just as previously required in order to be located. >> Current usage is not affected by this change. >> >> If there are no objections, I will add this change to the repository >> trunk. In order for members to test it before the 3.03GA release, it >> will be necessary to refresh the RC2 distribution or build a new RC3 >> distribution and publish it. Some changes to the QuickStart Guide >> installation section (3.4) may be needed. These three common steps to >> setup use of NetRexx with ecj from script nrc can now be reduced to >> just the first step: >> >> 1) Add NetRexx \bin directory to Windows PATH >> 2) Add NetRexxF.jar to the Java CLASSPATH >> 3) Create netrexx_java environment variable with value -Dnrx.compiler=ecj >> >> -- Kermit Kiser >> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> >> > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Well, I agree with the platform-independence issue as an ideal. But
successfully installing NetRexx is obviously just a little more complicated than many users are capable of / willing to deal with. Perhaps we could provide a universal installer that terminates with the invocation of a provided "installation verification" routine, which would run 'enviroscan' to validate access to Java, then determine the host platform, add \bin to the PATH if appropriate and do any other platform-dependent housekeeping, then compile and execute a sample program. With sufficient diagnostic messages from the IVP, it would be much easier to deal with the subset of the installation problems that are not obvious to the user and end up on the discussion list. Fundamentally, a Windows user want to: 1. Click on an icon on a webpage to start the download 2. Open a NotePad window and enter 'Say "Hello, JavaWorld"' and Save it. 3. Open a Command window and enter 'nrx hello', and see the text on the screen. The more steps we make them go through to get to step 3, the fewer users will be immediately successful and continue to explore the language. Creation of the IVP is left as an exercise for the reader, of course... ;-) -Chip- On 5/31/2014 3:49 PM René Jansen said: > it is Java so we would be short of the target if the installer is platform dependent. I agree with Kermit that the platform dependent startup script is the right place for this change. I would think we should not add things to peoples paths - it is the gliding slope of registries, signed installers, etc. Have a separate script do that and and have that asking for permission would be my limit. > > Also, the jar of worms that is opened with that - bash or tcsh or zsh, .profile or .bash_profile or .tcshrc, cmd.exe or charms, quicklinks, cygwin, uwin, PowerShell, can you tell me which path? > > On 31 mei 2014, at 21:04, Chip Davis <[hidden email]> wrote: > >> That sounds like a good thing to me Kermit, but I'm hardly the expert on these things. What I don't understand is that every other software package I've installed seems to add a directory or two to my PATH variable, so why aren't we? >> >> "Best practices" is a moving target, and I'm not happy with PATH-cruft, but it would seem to be a reasonable "get the user up and running" approach. With proper documentation we could offer alternative installation schemes. >> >> Or is this a matter of (vainly) trying to craft a single installation process for all possible platforms? >> >> -Chip- >> >> On 5/31/2014 2:42 PM Kermit Kiser said: >>> René and other interested parties -- >>> >>> Due to some recent issues with classpaths and NetRexx translator >>> scripts (such as nrc) that have been reported on the list, I would >>> like to slightly modify the batch script (NetRexxC.bat) which we >>> provide for Windows systems. This change will make the Eclipse >>> compiler the default compiler when available. >>> >>> The Windows environment variable "netrexx_java" that we currently use >>> in the script to pass a compiler selection will still override the >>> default just as it now does. However changing the default compiler to >>> ecj allows the script to automatically add module NetRexxF.jar to the >>> Java classpath and hopefully eliminates many of the problems with >>> locating a Java compiler encountered by those not familiar with use of >>> the classpath options and the environment variable. NetRexxF.jar is >>> automatically located from the sibling \lib directory if not already >>> found in the classpath. >>> >>> The net effect of this change is that adding the NetRexx "\bin" >>> directory to the Windows PATH will be ALL that is needed to compile >>> and run NetRexx programs for anyone using the "nrc" or "NetRexxC" >>> scripts. Non Windows users are not affected. If NetRexxC.bat is moved >>> or copied to a PATH directory, then NetRexxF.jar must still be added >>> to the classpath just as previously required in order to be located. >>> Current usage is not affected by this change. >>> >>> If there are no objections, I will add this change to the repository >>> trunk. In order for members to test it before the 3.03GA release, it >>> will be necessary to refresh the RC2 distribution or build a new RC3 >>> distribution and publish it. Some changes to the QuickStart Guide >>> installation section (3.4) may be needed. These three common steps to >>> setup use of NetRexx with ecj from script nrc can now be reduced to >>> just the first step: >>> >>> 1) Add NetRexx \bin directory to Windows PATH >>> 2) Add NetRexxF.jar to the Java CLASSPATH >>> 3) Create netrexx_java environment variable with value -Dnrx.compiler=ecj >>> >>> -- Kermit Kiser >>> >>> _______________________________________________ >>> Ibm-netrexx mailing list >>> [hidden email] >>> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >>> >>> >> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
Re: Request to change default compiler to ecj in windows script NetRexxC.bat
|
|
In reply to this post by rvjansen
The updated NetRexxC.bat script is committed to trunk for testing.
On May 31, 2014 11:50:16 AM PDT, "René Jansen" <[hidden email]> wrote: Kermit, -- Sent from my Android tablet with K-9 Mail. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
«
Return to ibm-netrexx
|
1 view|%1 views
| Free forum by Nabble | Edit this page |