macOS prevents executables from running in Desktop, Documents, and Downloads unless you specifically allow them in Settings>Security and Privacy>Files and Folders. I tried the sequence given earlier with j903_mac64.zip (dated 11/20) copying the j903 folder to ~ (as noted above), ~/testing, and Applications and everything worked. I opened a terminal in j903, ran bin/jconsole, and the Qt folder was created and the jqt.app starts. Doing the same in Documents, Downloads, or Desktop results in the jqt.app not starting up. Norman
On Sat, Nov 20, 2021 at 8:47 PM Aaron Ash <[email protected]> wrote: > I just tried with a new directory ~/testing/j903 and the Qt directory > is not created by 'install'jpkg'*'. > > On Sun, Nov 21, 2021 at 12:24 PM Raul Miller <[email protected]> > wrote: > > > > It's plausible that Apple has some extra security on the Downloads > > directory, to prevent rogue code from deploying there. > > > > On the other hand, I expect that ~/Applications/j903/ should work. > > > > (But I do not have an M1 to test this.) > > > > FYI, > > > > -- > > Raul > > > > On Sat, Nov 20, 2021 at 9:15 PM Aaron Ash <[email protected]> wrote: > > > > > > Hi Norman, > > > > > > Ah, that was the missing piece! > > > The Qt directory only gets created if the j903 folder is directly in > > > the home directory: ~/j903 > > > If it's in ~/Downloads/j903 or anywhere else then the Qt directory > > > doesn't get created and then jqt can't start due to the missing libs. > > > > > > I followed your steps above with the directory in ~/Downloads/j903 and > > > it still didn't work, then moved the directory to ~/j903 and ran > > > 'install'jpkg'*' again and it created the Qt directory and required > > > libs. > > > > > > Is that location hard coded somewhere that it shouldn't be? > > > > > > Cheers, > > > Aaron Ash. > > > > > > On Sun, Nov 21, 2021 at 1:36 AM Norman Drinkwater > > > <[email protected]> wrote: > > > > > > > > New zips with updated pacman install fine on macOS 12 M1 Macbook. > > > > Download j903_mac64.zip, move j903 folder to home folder. > > > > From terminal in j903 run ./macos-fix.command > > > > Start jconsole (9!:56'cpu' should say arm64) > > > > load'pacman' > > > > 'install'jpkg'*' > > > > There should now be a folder named Qt in the j903 folder. > > > > Start jqt from jqt903 icon on desktop. > > > > In jqt terminal, 9!:56'cpu' will return x86_64. > > > > > > > > > > > > On Sat, Nov 20, 2021 at 12:36 AM bill lam <[email protected]> > wrote: > > > > > > > > > Since jqt is not a fat binary, the arch -x86_64 is not needed, can > you > > > > > check if this is a security issue by doing a fresh install on > ~/j903 ? > > > > > > > > > > On Sat, Nov 20, 2021 at 2:10 PM Aaron Ash <[email protected]> > wrote: > > > > > > > > > > > Thanks Norman, > > > > > > > > > > > > A native arm64 jqt in j904 will be nice to see. > > > > > > I've done the following: > > > > > > cd /Applications/j903 > > > > > > arch -x86_64 bin/jconsole > > > > > > load'pacman' > > > > > > 'install'jpkg'*' > > > > > > NB. (successful run) > > > > > > > > > > > > However jqt still doesn't want to start: > > > > > > arch -x86_64 bin/jqt > > > > > > dyld: Library not loaded: @rpath/QtGui.framework/Versions/5/QtGui > > > > > > Referenced from: /Applications/j903/bin/jqt > > > > > > Reason: image not found > > > > > > zsh: abort arch -x86_64 bin/jqt > > > > > > > > > > > > The binaries do look to be correct: > > > > > > file bin/* > > > > > > bin/icons: directory > > > > > > bin/installer.txt: ASCII text > > > > > > bin/jbrk.command: POSIX shell script text executable, > ASCII text > > > > > > bin/jconsole: Mach-O universal binary with 2 > > > > > > architectures: [x86_64:Mach-O 64-bit executable x86_64] > [arm64:Mach-O > > > > > > 64-bit executable arm64] > > > > > > bin/jconsole (for architecture x86_64): Mach-O 64-bit executable > x86_64 > > > > > > bin/jconsole (for architecture arm64): Mach-O 64-bit executable > arm64 > > > > > > bin/jhs.command: POSIX shell script text executable, > ASCII text > > > > > > bin/jqt: Mach-O 64-bit executable x86_64 > > > > > > bin/jqt.command: POSIX shell script text executable, > ASCII text > > > > > > bin/libj.dylib: Mach-O universal binary with 2 > > > > > > architectures: [x86_64:Mach-O 64-bit dynamically linked shared > library > > > > > > x86_64] [arm64] > > > > > > bin/libj.dylib (for architecture x86_64): Mach-O 64-bit > > > > > > dynamically linked shared library x86_64 > > > > > > bin/libj.dylib (for architecture arm64): Mach-O 64-bit > > > > > > dynamically linked shared library arm64 > > > > > > bin/libjqt.1.9.4.dylib: Mach-O 64-bit dynamically linked > shared > > > > > > library x86_64 > > > > > > bin/libjqt.1.9.dylib: Mach-O 64-bit dynamically linked > shared > > > > > > library x86_64 > > > > > > bin/libjqt.1.dylib: Mach-O 64-bit dynamically linked > shared > > > > > > library x86_64 > > > > > > bin/libjqt.dylib: Mach-O 64-bit dynamically linked > shared > > > > > > library x86_64 > > > > > > bin/profile.ijs: ASCII text > > > > > > bin/profilex_template.ijs: CLIPPER instruction profile > > > > > > > > > > > > Do I also need to manually install the right version of Qt5 > somewhere > > > > > > that dyld can find it? > > > > > > > > > > > > Cheers, > > > > > > Aaron Ash. > > > > > > > > > > > > On Sat, Nov 20, 2021 at 3:36 PM Norman Drinkwater > > > > > > <[email protected]> wrote: > > > > > > > > > > > > > > The current version of jqt on macOS will only run under > Rosetta2 as it > > > > > > > depends on Intel Qt 5.15 libraries. The beta v is a universal > binary > > > > > and > > > > > > > runs arm64 unless you tell it to use the Intel version. Start > jconsole > > > > > as > > > > > > > the Intel version, then load’pacman’ and run ‘install’jpkg’*’. > > > > > > > > > > > > > > I think that should get jqt up and running. A native arm64 > version of > > > > > jqt > > > > > > > should show up in j904. > > > > > > > Norman > > > > > > > > > > > > > > On Fri, Nov 19, 2021 at 10:46 PM Aaron Ash < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > I'm trying to get jqt to run on an m1 macbook air somewhat > > > > > > unsuccessfully. > > > > > > > > On linux and windows jqt has always "just worked" after > running: > > > > > > install > > > > > > > > '*' > > > > > > > > But on macos it seems like the qt libraries don't get > installed > > > > > > > > automatically. > > > > > > > > (On linux I likely already have the qt5 libraries installed > via the > > > > > > > > package manager I guess) > > > > > > > > > > > > > > > > Steps: > > > > > > > > - Download j903_mac64.zip and extract to /Applications/j903 > > > > > > > > - cd /Applications/j903 > > > > > > > > - sudo macos-fix.command > > > > > > > > - sudo updateje.sh > > > > > > > > - sudo updatejqt.sh > > > > > > > > ./bin/jconsole > > > > > > > > JVERSION > > > > > > > > Engine: j903/j64/darwin > > > > > > > > Beta-v: commercial/2021-11-16T21:55:10 > > > > > > > > Library: 9.03.07 > > > > > > > > Platform: Darwin 64 > > > > > > > > Installer: J903 install > > > > > > > > InstallPath: /applications/j903 > > > > > > > > Contact: www.jsoftware.com > > > > > > > > 9!:56'cpu' > > > > > > > > arm64 > > > > > > > > exit'' > > > > > > > > > > > > > > > > /bin/jqt.command > > > > > > > > dyld: Library not loaded: > @rpath/QtGui.framework/Versions/5/QtGui > > > > > > > > Referenced from: /Applications/j903/bin/jqt > > > > > > > > Reason: image not found > > > > > > > > ./bin/jqt.command: line 4: 61087 Abort trap: 6 > bin/jqt > > > > > > > > > > > > > > > > > > > > > > > > I've installed Qt via the online installer (selecting "Qt > Desktop > > > > > > > > libs" including QtCreator and Qt 6.2.1) but jqt still shows > the above > > > > > > > > error. > > > > > > > > Qt has installed to $HOME/Qt > > > > > > > > > > > > > > > > Is there a step that I have missed? > > > > > > > > I can go through the steps to build jqt from source but I > would have > > > > > > > > thought there would be an easier way for most users to get > jqt > > > > > > > > running. > > > > > > > > > > > > > > > > Cheers, > > > > > > > > Aaron Ash. > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > > For information about J forums see > > > > > http://www.jsoftware.com/forums.htm > > > > > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > > > > > ---------------------------------------------------------------------- > > > > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > > > > > > > > ---------------------------------------------------------------------- > > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
