Versions are funny things - arbitrarily and haphazardly assigned, typically.
On the mac I'm currently working on, with this month's j807, going into the j64-807 directory and running otool -L $(find Qt -iname '*.dylib') gets me over 200 lines of output and a variety of "version numbers": j64-807$ otool -L $(find Qt -iname '*.dylib') | fmt -w1 | sed 's/[),]//g' | egrep '[0-9][.][0-9]+[.][0-9]' | sort -u 0.0.0 1.0.0 1.2.8 1070.22.0 1238.50.2 1349.63.0 1349.64.0 150.0.0 1504.82.104 157.0.0 2.0.0 2.12.0 228.0.0 275.0.0 300.0.0 307.5.0 45.0.0 48.0.0 5.9.0 5.9.6 64.0.0 775.19.0 That said, for qt 4 or later, if you have the build tools installed, you could do: qmake -query QT_VERSION See also: https://wiki.qt.io/Undocumented_QMake Anyways, testing for how other people have messed up is an open-ended problem. There's some good low-hanging fruit there, but at some point you have to deal with crashes... FYI, -- Raul On Tue, Oct 23, 2018 at 10:12 AM Don Guinn <[email protected]> wrote: > > There are several "IFxxx" names in the "z" locale, like "IFQT". But there > does not seem to be one telling which version of Qt is installed. Rather > than crash with strange errors, one could issue an error message that is > clear. Then again, there a few in there that I don't know what they mean as > well. Is there some place telling what all those "IFxxx" names mean? > > On Tue, Oct 23, 2018 at 12:04 AM bill lam <[email protected]> wrote: > > > the plot addon should also work for slim because it depends on gl2 only. > > > > One thing that looks strange to me is the name of libjqt file has > > asterisks in the front and rear. that name was passed from jqt to libj > > during boot up. Could you check what is the value of the name libjqt on > > Mac? > > on windows, it is something like > > libjqt > > C:/j64-807/bin/jqt.dll > > > > On Tue, Oct 23, 2018, 1:07 PM 'robert therriault' via General < > > [email protected]> wrote: > > > > > Hi Ian, > > > > > > I think that Joey hit on the issue with the QT IDE: 1.7.9s line. The s in > > > 1.7.9s suggests that you are running the slim version of jqt which does > > not > > > support OpenGL, Webview or Websockets. You can get the full version of > > jqt > > > by running install 'full' from the jconsole. Details at > > > > > https://code.jsoftware.com/wiki/Guides/Qt_IDE/Install#Slim_vs_Full_Builds > > > > > > Hope this helps. > > > > > > Cheers, bob > > > > > > > On Oct 22, 2018, at 8:45 PM, Ian Clark <[email protected]> wrote: > > > > > > > > The offending line is in: > > > > > > > > qt_gpapply_jzplot_=: 3 : 0 > > > > *rc=. glcmds`glcmds_jglc_@.(Poutput=iQTC) buf* > > > > assert. 0=rc [ 'glcmds buf' > > > > buf=: $0 > > > > ) > > > > > > > > It runs a choice of "cd" calls (one of which crashes)… > > > > glcmds_jgl2_=: chkgl2@:('"*/Applications/j64-807/bin/libjqt.dylib*" > > > > glcmds > i *i i' cd (; #))"1 > > > > glcmds_jglc_=: chkgl2@:('"*/Applications/j64-807/bin/libjqt.dylib*" > > > > glc_cmds > i *i i' cd (; #))"1 > > > > > > > > */Applications/j64-807/bin/libjqt.dylib* > > > > …is an alias of: > > > > /Applications/j64-807/bin/libjqt.1.7.9.dylib (dated 22/Sep/18, 22:51) > > > > …which looks as if it lends the trailing figures of its filename to the > > > Qt > > > > IDE: line of JVERSION. > > > > > > > > I've tried these alternative dylibs from earlier releases in its place: > > > > /Applications/j64-807/bin/libjqt.1.5.3.dylib > > > > /Applications/j64-807/bin/libjqt.1.7.7.dylib > > > > re-directing to each one in turn all the aliases that point to [1.7.9]. > > > > But no joy: jqt won't even start. [1.7.9] is the only one that works > > for > > > me. > > > > But not well enough to support the Plot Package it seems - I don't know > > > > enough about dylibs to conjecture why. > > > > > > > > On Tue, Oct 23, 2018 at 2:57 AM Joey K Tuttle <[email protected]> wrote: > > > > > > > >> I'm in the AVX version, and there I didn't encounter your problem, the > > > >> only difference I see is the Qt IDE: line reported in JVERSION > > > >> > > > >> I suppose it might have something to do with the Darwin release (on > > this > > > >> machine I'm at Version 10.14.1 beta 4... > > > >> > > > >> I'll look into trying it on a machine without AVX, running an older > > OS X > > > >> > > > >> load 'plot' > > > >> plot 0 > > > >> plot 1 2 3 5 > > > >> JVERSION > > > >> Engine: j807/j64/darwin > > > >> Release: commercial/2018-10-05T11:55:35 > > > >> Library: 8.07.18 > > > >> Qt IDE: 1.7.9/5.9.6 > > > >> Platform: Darwin 64 > > > >> Installer: J807 install > > > >> InstallPath: /applications/j64-807 > > > >> Contact: www.jsoftware.com > > > >> > > > >> > > > >>> On 2018Oct 22, at 18:31, Ian Clark <[email protected]> wrote: > > > >>> > > > >>> 1. Launch jqt. (With no startup script, to get an out-of-the-box > > > session. > > > >>> That's in case there's a clash with something else I was running.) > > > >>> > > > >>> 2. Enter: > > > >>> load'plot' > > > >>> plot 0 > > > >>> …an empty "plot" window appears (as happens with j805 jqt) > > > >>> > > > >>> 3. Enter (…the first effective phrase from the Plot Package lab): > > > >>> plot 1 2 3 5 > > > >>> …an error message-box appears, with one button: "OK". > > > >>> It reads: > > > >>> ——————————————— > > > >>> error in: plot_gs_paint > > > >>> > > > >>> domain error: cd > > > >>> rc=. glcmds`glcmds_jglc_@. > > > >>> (Poutput=iQTC)buf > > > >>> ——————————————— > > > >>> > > > >>> 4. Press the "OK" button > > > >>> …the message-box disappears then immediately reappears with the same > > > >>> message, in an infinite cycle. No other input is accepted by jqt. > > > >>> > > > >>> 5. To quit jqt, choose {Apple} > Force Quit… > > > >>> …(I haven't found any other way to escape.) > > > >>> > > > >>> JVERSION > > > >>> Engine: j807/j64nonavx/darwin > > > >>> Release: commercial/2018-10-05T11:56:35 > > > >>> Library: 8.07.19 > > > >>> Qt IDE: 1.7.9s/5.9.6 > > > >>> Platform: Darwin 64 > > > >>> Installer: J807 install > > > >>> InstallPath: /applications/j64-807 > > > >>> Contact: www.jsoftware.com > > > >>> > > ---------------------------------------------------------------------- > > > >>> 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
