summaryrefslogtreecommitdiffstats
path: root/bin/patch_capabilities.pl
diff options
context:
space:
mode:
authoraxis <qt-info@nokia.com>2010-02-26 15:12:29 (GMT)
committeraxis <qt-info@nokia.com>2010-02-26 15:17:35 (GMT)
commit2850abde744ae8140cf7187ca80dea684f60f3fa (patch)
treed1f6ef1cff09d9d8096b261c9d4d9cf18c09c718 /bin/patch_capabilities.pl
parentec45c75f443f21d47fa47d1fc0396af02befa1c7 (diff)
downloadQt-2850abde744ae8140cf7187ca80dea684f60f3fa.zip
Qt-2850abde744ae8140cf7187ca80dea684f60f3fa.tar.gz
Qt-2850abde744ae8140cf7187ca80dea684f60f3fa.tar.bz2
Switched the order of message and execution in patch_capabilities.
It seems more natural to have the message first, so that you can tell which file is taking long to complete.
Diffstat (limited to 'bin/patch_capabilities.pl')
-rwxr-xr-xbin/patch_capabilities.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/patch_capabilities.pl b/bin/patch_capabilities.pl
index bac7e64..d51f154 100755
--- a/bin/patch_capabilities.pl
+++ b/bin/patch_capabilities.pl
@@ -217,8 +217,8 @@ if (@ARGV)
$commandToExecute .= $binaryPath;
# Actually execute the elftran command to set the capabilities.
+ print ("Executing ".$commandToExecute."\n");
system ($commandToExecute." > NUL");
- print ("Executed ".$commandToExecute."\n");
## Create another command line to check that the set capabilities are correct.
#$commandToExecute = "elftran -dump s ".$binaryPath;