Re: Octave-maintainers Digest, Vol 155, Issue 1

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Octave-maintainers Digest, Vol 155, Issue 1

John Donoghue-3
On 2/1/19 2:50 AM, [hidden email] wrote:

> Message: 2
> Date: Thu, 31 Jan 2019 16:16:31 -0500
> From: Nicholas Jankowski<[hidden email]>
> To: octave-maintainers<[hidden email]>
> Subject: windows install for upcoming release
> Message-ID:
> <CABNpfR8CRDQm+gT7PsgnxxPS9jiEq5xdi0qf=[hidden email]>
> Content-Type: text/plain; charset="utf-8"
>
> looking at the wiki for Windows installation instructions [1], looking for
> a few clarifications as things have changed a bit over time. Please correct
> me if any of the following is incorrect:
>
> 1 - There is a note that starting with Octave 4.4.0 users must add
> --force-gui to any manual Windows shortcuts or the CLI will start by
> default.  I do not have that flag in my shortcuts, and the GUI starts by
> just calling 'octave.vbs'.  It seems this behavior has been changed and the
> instruction can be removed?

gui starts by default now, so you want to create cmdline octave
shortcut, you would need the --no-gui option, otherwise no additional
options are required.

>
> 2 - there is no more 'octave.bat' file, only octave.vbs. assuming this to
> be correct, reference the .bat can be removed for starting octave.
There is a bat file, how was moved to bin directory
> 3 - After using the executable installer, there's nothing else for the user
> to do except use the shortcuts created for him/her, correct? (Looking for
> confirmation, I only even use the zip archives...)
Correct

> 4 - for the zip/7z archives:  after unzipping, there are 6 different
> executable files in the octave root directory.
>
> cmdshell.bat
> fc_update.bat
> msys2_shell.cmd
> octave.vbs
> octave-firsttime.vbs
> post-install.bat
>
> while the general shortcut should be made to octave.vbs,  which of those
> files, and in what order, should the user run them? I know fc_update.bat
> was recommended, but I don't know what firsttime and post-install are
> intended to do.

post-install is what is run from the installer after installation, so
probally should be what is run at after unzipping. It registers the
msys2 environment, calls the fc_cache, and does the pkg rebuild

octave-firsttime.vbs is called from the installer when run octave checkbox is checked - its only needed in the installer, as it needs to run octave as the unelevated user.


cmdshell.bat will display a bash shell window

> [1]https://wiki.octave.org/Octave_for_Microsoft_Windows#Packages
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:<http://lists.gnu.org/archive/html/octave-maintainers/attachments/20190131/67350fbf/attachment.html>



Reply | Threaded
Open this post in threaded view
|

Re: Octave-maintainers Digest, Vol 155, Issue 1

nrjank


On Fri, Feb 1, 2019 at 6:22 AM John Donoghue <[hidden email]> wrote:
On 2/1/19 2:50 AM, [hidden email] wrote:

gui starts by default now, so you want to create cmdline octave
shortcut, you would need the --no-gui option, otherwise no additional
options are required.

ok, do we recall at what version this changed back? The current instructions say it was the other way for 4.4.0. Maybe should tidy that up for posterity before moving it over to the [outdated] page.   Will add a note about optionally creating a --no-gui shortcut if a CLI only one is desired, and then have that be the instruction set for v5 when it goes live.
 
>
> 2 - there is no more 'octave.bat' file, only octave.vbs. assuming this to
> be correct, reference the .bat can be removed for starting octave.
There is a bat file, how was moved to bin directory

ok, will still remove reference to the bat for purpose of making manual shortcuts.
 
> 3 - After using the executable installer, there's nothing else for the user
> to do except use the shortcuts created for him/her, correct? (Looking for
> confirmation, I only even use the zip archives...)
Correct

Does the exe still make both gui and cli shortcuts?
 

post-install is what is run from the installer after installation, so
probally should be what is run at after unzipping. It registers the
msys2 environment, calls the fc_cache, and does the pkg rebuild

octave-firsttime.vbs is called from the installer when run octave checkbox is checked - its only needed in the installer, as it needs to run octave as the unelevated user.


cmdshell.bat will display a bash shell window


ok, will plan to update the instructions to just say 'run the post-install' once after unzipping, since it takes care of everything including the pkg rebuild that we kept getting help requests about. 
Reply | Threaded
Open this post in threaded view
|

Re: Octave-maintainers Digest, Vol 155, Issue 1

Ian McCallion
On Fri, 1 Feb 2019 at 15:06, Nicholas Jankowski <[hidden email]> wrote:

>
> On Fri, Feb 1, 2019 at 6:22 AM John Donoghue <[hidden email]> wrote:
>>
>> On 2/1/19 2:50 AM, [hidden email] wrote:
>>
>> gui starts by default now, so you want to create cmdline octave
>> shortcut, you would need the --no-gui option, otherwise no additional
>> options are required.
>>
> ok, do we recall at what version this changed back? The current instructions say it was the other way for 4.4.0. Maybe should tidy that up for posterity before moving it over to the [outdated] page.   Will add a note about optionally creating a --no-gui shortcut if a CLI only one is desired, and then have that be the instruction set for v5 when it goes live.
>
>>
>> >
>> > 2 - there is no more 'octave.bat' file, only octave.vbs. assuming this to
>> > be correct, reference the .bat can be removed for starting octave.
>> There is a bat file, how was moved to bin directory
>
> ok, will still remove reference to the bat for purpose of making manual shortcuts.

One might ask why the .bat exists. If there is a good reason it should
be fixed to be compatible with the .vbs. It is not compatible in 4.4.1
 at least in the area of setup for qt5.

While looking at this area, perhaps these questions could be considered also:

1. Is it supported to launch octave from within another program rather
than just from a desktop icon of a commandline? If so it would be very
helpful if the parameters and the preparation work (environment
variables, etc) needed to launch the .exe directly was documented.
Without this it is necessary to reverse-engineer octave.vbs to find
the information.

2. Is it necessary to set up the HOME environment variable? I have not
found anything that breaks if not set

3. What is the purpose of octave-cli.exe and octave-cli-4.4.1.exe?
(Octave.vbs only calls octave-gui.exe, even for commandline)

Apologies if this is not the right place to raise these questions.

Cheers... Ian