@SGaist Great idea! I change the code and everything should work. I close the topic and if I encounter any other problems I will create a new one. @SGaist , @JoeCFD Thank you for your help!

@Kyeiv OK, but please put the error checking code in anyway. With OS commands you never know what might go wrong (just like you discovered), so it's important to check for & report all errors! And especially if you are going to be distributing this....

Hi, If your output follows a known pattern then parse stdout to extract what you want.

@NewMoon see QTBUG-38181 It's a known limitation of QJSEngine. If you can, switch to QScriptEngine (QML).

Hi, Are you using your distribution Qt packages ?

@Mark81 Yes both the Hello World and content of the variable were shown. Again it's on OS X with a recent version of bash.

Hm, I found it as separate install in Qt Maintenance tool. THe problem is - It's installing with such errors: (qt.55.qtscript.win32_mingw492): Could not find the needed QmakeOutputInstallerKey(qt.55.win32_mingw492_qmakeoutput) value on the installer object. The ConsumeOutput operation on the valid qmake needs to be called first.

I managed using the following additional lines in CustomCode QString function = "test(1)"; QJSValue testfunction = myEngine.evaluate(function); qDebug() << testfunction.toString(); With my script CustomLogic.qs looking like this: function test(x) { var a = "tested!"; a = a + x.toString(); return a; } Returns "tested!1" in the application output

Many thanks @Wieland, but my problem is with the installer script (sorry for not having explained before (-_-)). The application is fine according to the customer feedback. Am trying to check the existence of previous installations and if so, check which version is installed. For this, I have created a registry entry containing the application path and installed version, but I don´t know how to compare the current installation version with the previously installed one. Thanks in advance.

At last I got it to work. The parameter "/reg:64" passed to reg.exe makes it do what it's told. I just hope this won't mess things up on a 32bit windows. So, that needs to be component.addElevatedOperation("Execute",reg, "ADD",key, "/reg:64" ,"/v","@TargetDir@\\maintenancetool.exe","/t","REG_SZ","/d","~ RUNASADMIN", "/f");

Hi, The script works only if the Qt libraries are in the same directory of the executable. Move the .so files from qtlibs to the directory where the script and the executable are.

Hello SGaist, Thanks for your response. I expect for Serbian (Cyrillic, Serbia) to get: 2 (QLocale::Script::CyrillicScript) from QLocale::system().script(), and "sr-Cyrl-RS" from QLocale::system().bcp47Name(). Similarly, for Serbian (Latin, Serbia) I expect: 7 (QLocale::Script::LatinScript) from QLocale::system().script(), and "sr-Latn-RS" from QLocale::system().bcp47Name(). Should I open new bugs for script() and bcp47Name()? This is the workaround I made for bcp47Name: QString bcp47Name; #ifdef Q_OS_WIN wchar_t buffer[LOCALE_NAME_MAX_LENGTH]; ::GetUserDefaultLocaleName(buffer, LOCALE_NAME_MAX_LENGTH); bcp47Name = QString::fromWCharArray(buffer); #else bcp47Name = QLocale::system().bcp47Name(); #endif But didn't have a chance to try it on non-Windows platforms yet. Thanks!