PJSR creating subprocess

[georg.viehoever]

Code: [Select]

../../SystemCommandInstance.cpp:24:20: aviso: QProcess: No existe el fichero o el directorio
../../SystemCommandInstance.cpp:25:17: aviso: QTime: No existe el fichero o el directorio
../../SystemCommandInstance.cpp: In member function ‘virtual bool pcl::SystemCommandInstance::ExecuteGlobal()’:
../../SystemCommandInstance.cpp:24:20: aviso: QProcess: No existe el fichero o el directorio

This looks as if the Qt4 development files are not installed on your system. I am currently not at my development system, so I can tell you only tonight what you should be looking for.

Regarding the problem in your the follow up message: I have no idea what happens there.

Georg

[vicent_peris]

Hmmm... Qt4 files? What must I install? I thought that only the PCL was needed.


V.

[georg.viehoever]

Vincent, I will check this tonight at my development system. I also thought I had not installed anything on top of the default...
Georg

[georg.viehoever]

...
Yes, I've installed the full PCL, of course. I don't know why this happens... if I put in .bashrc "$HOME/Pixinsight/bin" instead of "/home/vperis/Pixinsight/bin", then make doesn't find the files.
...

Maybe you are working as root/su (which is neither necessary nor recommended), not as vperis. You can check the setting of $HOME via "echo $HOME". If this is not /home/vperis, you are probably working as a different user.

Georg

[georg.viehoever]

...

Code: [Select]

../../SystemCommandInstance.cpp:24:20: aviso: QProcess: No existe el fichero o el directorio
../../SystemCommandInstance.cpp:25:17: aviso: QTime: No existe el fichero o el directorio
....
What's happening??

Hi,

I updated the description in http://pixinsight.com/forum/index.php?topic=1791.msg10769#msg10769 (see the Post Scriptum). Current versions of SystemCommand also need the Qt development packages.

Georg

[georg.viehoever]

...here is updated version of the module, with bugfixes and some steps towards new functionality...

I precompiled version for Fedora11-x64 is available on http://cid-c56e60845cfa6790.skydrive.live.com/self.aspx/Pixinsight/SystemCommand-pxm_20100430.zip . Put the unpacked file into your PI bin directory, check that permissions are as with all other *.so files, and add the module as previously described. Note: I have no idea on what kind of Linuxes this will run without problems. Use at your own risk.

Georg

[vicent_peris]

Hi,

seems that my problem is that I'm under GNome, so it doesn't comes with Qt libraries.

Thanks you for the precompiled module! It's working in my Fedora10 x64.


Regards,
Vicent.

[Christoph Puetz]

Dear Georg,
thank you for your hints to the astrometry project. I also compiled and installed the software on my system.
I also tried your Fedora Library on my Suse 11.2 64bit Version of PI 1.6.0 and it also works fine  !
GREAT WORK !

PS: Would be great if this could be applied as a standard to future releases  of PI.

Thanks to all, who helped (see above) to make the software run.
Christoph

[georg.viehoever]

Christoph,

thanks for your kind words  ! I still have a lot of ideas of what to do with this tool, but currently I dont have the time to work on it. We'll see what the future brings...

Georg

[georg.viehoever]

...

Code: [Select]

var commandsAllowed = Settings.readGlobal( "Security/AllowJavaScriptCommandExecution", DataType_Boolean );
...

Juan,

I tried your code in PI1.61, and it always produces a "false". I changed the settings, checked them again and again, reset the JS engine, restarted PI, nothing helped.

Code: [Select]

  var commandsAllowed = Settings.readGlobal( "Security/AllowJavaScriptCommandExecution", DataType_Boolean );
   if (!commandsAllowed){
      throw new Error("Cannot execute shell commands, please change Edit > Security Settings > Allow execution of commands from JavaScript scripts");
   }  //if not allowed

So what is wrong with the code?

Georg

[Juan Conejero]

Absolutely nothing is wrong with your code. It is a bug (a regression) in PI 1.6.1, which I'm going to publish on the bug reports board after writing this message. Sorry!

Fortunately, the workaround is easy and works perfectly:

Code: [Select]

#include <pjsr/StdIcon.jsh>
#include <pjsr/DataType.jsh>

function canExecuteCommands()
{
#iflteq __PI_BUILD__ 625 // public final 1.6.1 release

   try
   {
      console.execute( "version" );
      return true;
   }
   catch ( e )
   {
      return false;
   }

#else

   return Settings.readGlobal( "Security/AllowJavaScriptCommandExecution", DataType_Boolean );

#endif
}

var commandsAllowed = canExecuteCommands();
if ( !commandsAllowed )
{
   (new MessageBox( "<p><b>Cannot execute shell commands</b></p>" +
                    "<p>Please change the state of the following global security item:</p>" +
                    "<p><i>Allow execution of commands from JavaScript scripts</i></p>" +
                    "<p>using the <i>Edit > Security Settings</i> main menu command.</p>",
                    "My Script", StdIcon_Error )).execute();
   throw new Error( "Global security directive: Command execution not allowed from scripts." );
}
else
{
   (new MessageBox( "<p>I can execute shell commands. Thanks!</p>",
                    "My Script", StdIcon_Information )).execute();
}

This bug will be fixed in the next version, but it will have to wait until September.

[georg.viehoever]

Thanks a lot.
Note: It is also there in 1.60 (at least the Linux x64 version)
Georg