[Octave-bug-tracker] [bug #54398] Windows: dev Octave opens file in GUI editor multiple times when debugging

[Philip Nienhuis]

Update of bug #54398 (project octave):

                  Status:               Confirmed => Ready For Test         

    _______________________________________________________

Follow-up Comment #18:

@Markus:
That fixes it. Thanks very much.
Reading the patch it's a bit of black magic to me :-) but it works. The COM
error is also fixed, nice!

I'll try to make a complete crossbuild now with all my local mods; if that
also works fine I'll push and close the bug, OK?

Then:
_MXE completed compilation over night._
In return a hint for you, or maybe you already do it:

Im my mxe-octave setups the pkg/ subdir is really a symlink to a pkg subdir
outside mxe. In that downloaded-package subdir, octave-5.0.0.tar.lz is again a
symlink to the .lz dist archive in Octave's native build dir (on Linux).
I refresh (re-clone and configure) my mxe-octave about every 2 months and hg
pull/ && hg update it about every other week.

That way, when I want to build a new installer, I only have to build the dist
archive on the Linux side and then, in mxe-octave, just run:
rm -f installed-packages/default-octave && make nsis-installer JOBS=5

That way, cross-building a complete octave setup (in dist/octave/) just takes
20 minutes, generating the installer another 10 minutes (I usually interrupt
it when it says "generating installer").

On the Windows side I have read-only access to my Linux $HOME dir using
ext2fsd and I can run Octave directly from the mxe-octave/dist/octave subdir.
(BTW to that end I renamed the dist/octave/ subdir in binary-dist-rules.mk by
eliminating the date/time suffix cruft.)

All in all generating a new crossbuild just for testing only takes me 20
minutes excl. the Linux rebuild time + reboot time.

ATM I'm busy setting up a Win10 test environment in VirtualBox. MS offers free
time-bombed Win10 builds for trying MS-Edge in a.o., VirtualBox, and that runs
fine on Linux as well. In Windows 7 I have such a test Win10 running in VB and
through shared folders + the ex2fsd setup on Win7 I can run the Octave
cross-build on the Linux side as well - no need to install Octave in the Win10
guest OS.
On Linux I'm just stuck setting up shared folders (no time/priority now to
investigate), but once there I don't even have to reboot into Windows anymore
to test crossbuilds. (Except for Win7-specific issues like the one here).


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54398>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/