All of lore.kernel.org
 help / color / mirror / Atom feed
From: LogiSch17 <logi.tss@hotmail.de>
To: buildroot@busybox.net
Subject: [Buildroot] Shell scripts does not emit finished() to QProcess
Date: Tue, 14 Feb 2017 02:06:59 -0800 (PST)	[thread overview]
Message-ID: <1487066819690-156977.post@n4.nabble.com> (raw)
In-Reply-To: <ce6994a6-76f7-a075-51b6-e80dc306cdd8@gmail.com>

Hi,
in my code i have something like:

void UpdateHandler::UpdateHandler(QObject* parent):QObject(parent){

     copy  = new QProcess(this);
     updEnc = new QFile("/media/upStick/update.enc"); //encrypt update file
on stick
     cpscript <<"/usr/bin/cpupdt.sh"; //shell script to copy the file to
/usr

      QObject::connect(copy, SIGNAL(finished(int, QProcess::ExitStatus)),
this, SLOT(fileCopied(int, QProcess::ExitStatus)));
}

void UpdateHandler::copyFile(){

    if(updEnc->exists()){
        qDebug()<< "Updatefile found on Stick";
        qDebug()<< "copying file to /usr";

        copy->start("/bin/sh", cpscript);
    }
}
void UpdateHandler::fileCopied(int status, QProcess::ExitStatus estatus){

     QDebug()<< "File copied, Status: " << status << estatus ;
.....
}

Have not tried strace -f yet.
But i will test i now.





--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Shell-scripts-does-not-emit-finished-to-QProcess-tp156891p156977.html
Sent from the Buildroot (busybox) mailing list archive@Nabble.com.

  reply	other threads:[~2017-02-14 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 14:51 [Buildroot] Shell scripts does not emit finished() to QProcess LogiSch17
2017-02-13 15:28 ` Zoltan Gyarmati
2017-02-14 10:06   ` LogiSch17 [this message]
2017-02-14 10:36     ` LogiSch17
2017-02-14 13:43   ` LogiSch17

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1487066819690-156977.post@n4.nabble.com \
    --to=logi.tss@hotmail.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.