Re: Distribute only 64-bit executables?

[Edward K. Ream]

On Wed, Feb 7, 2018 at 12:26 PM, David Szent-Györgyi 
wrote:

>
> This is the Windows analogue of the Debian GNU/Linux's Multiarch support
> .
>

​Many thanks for these lengthy comments.  I've put a link to them at the
start of #710 . This
info item won't ever close, so your notes should remain readily accessible.

It looks like it is possible to create a 32-bit version of Leo on Windows,
so pyinstaller should work again on Windows. If so, everything will as it
was previously.  No changes needed to NSIS.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Distribute only 64-bit executables?

[David Szent-Györgyi]

On Monday, February 5, 2018 at 12:22:30 PM UTC-5, Edward K. Ream wrote:
>
> I am thinking of installing only 64-bit software on my Windows machine, 
> and to release only 64-bit pyinstaller builds.  Here are my thoughts:
>
> 1. Every distribution option doubles the amount of testing required for a 
> release.  In practice, not all options are tested.
>
> 2. Afaik, pyenchant is the only package requiring a 32-bit build. The tail 
> is wagging the dog.
>
> 3. True, 32-bit builds should run on 64-bit machines, so 32-bit builds 
> should be more portable.  But I have my doubts.
>
> Your comments, please.
>

This is the Windows analogue of the Debian GNU/Linux's Multiarch support 
. 

One can make 32-bit builds run on 64-bit operating systems, but that's 
extra work. 

I cope with this sort of problem all the time for work, where the issue is 
installing 32-bit apps that need to talk to hardware - the publisher of the 
Windows-level driver has extra work to do to provide interfaces for 32-bit 
code. 

Corresponding challenges for Leo start with the fact that 32-bit builds run 
on 64-bit machines, as long as the 32-bit build is aware that on a 64-bit 
machine, the C:\Program Files folder is 64-bit, and that C:\Program Files 
(x86) is 32-bit. It is also the case that 64-bit libraries either have 
32-bit duplicates that don't conflict with simultaneous use of the 64-bit 
cousins, or the 64-bit libraries must handle requests from 32-bit 
applications themselves. 

If you were to return to using a NSIS-based installer for Leo, you could 
handle the complications, but you would need to know both how Windows 
requires files placed and how it requires Registry entries places, and you 
would then need to write the NSIS-based installer to address those 
requirements. 

As I recall, you had enough headaches updating the NSIS-based installer as 
files were added and removed - and that was 32-bit Leo on 32-bit Windows 
XP, without the joys of UAC dialogs to handle permissions as forced by 
Vista and more recent versions of Windows. 

Links of interest: 

NSIS 32-bit 64-bit on Stack Overflow 


Stack Overflow: writing registry value in a 64-bit system 


-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Distribute only 64-bit executables?

[Edward K. Ream]

On Monday, February 5, 2018 at 11:22:30 AM UTC-6, Edward K. Ream wrote:

> 1. Every distribution option doubles the amount of testing required for a 
release. 

The following does indeed work when invoked in a python 3 interpreter, but 
maybe only on 64-bit systems:

import PyQt5.QtCore as C
import PyQt5.QtMultimedia as M
import os, sys
app=C.QCoreApplication(sys.argv)
path = 'c:/users/edreamleo/GayaneBalletSuite.mp3'
assert os.path.exists(path), repr(path)
url= C.QUrl.fromLocalFile(path)
content= M.QMediaContent(url)
player = M.QMediaPlayer()
player.setMedia(content)
player.play() 

The following works from within Leo:

import PyQt5.QtCore as C
import PyQt5.QtMultimedia as M
import os
path = 'c:/users/edreamleo/GayaneBalletSuite.mp3'
assert os.path.exists(path), repr(path)
url= C.QUrl.fromLocalFile(path)
content= M.QMediaContent(url)
player = M.QMediaPlayer()
player.setMedia(content)
g.app.permanentScriptDict['player'] = player # <--- new
player.play()

*Important*: a reference to the player must be retained, as shown in the 
penultimate line.

This is today's new idea, so maybe the new code *would *work on a 32-bit 
system.  But I don't want to test everything twice ;-)

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Distribute only 64-bit executables?

[Edward K. Ream]

I am thinking of installing only 64-bit software on my Windows machine, and 
to release only 64-bit pyinstaller builds.  Here are my thoughts:

1. Every distribution option doubles the amount of testing required for a 
release.  In practice, not all options are tested.

2. Afaik, pyenchant is the only package requiring a 32-bit build. The tail 
is wagging the dog.

3. True, 32-bit builds should run on 64-bit machines, so 32-bit builds 
should be more portable.  But I have my doubts.

Your comments, please.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.