Fixed lots of issues with installing a low-caps version of fshell from SIS file.
* Fixed issue in CCommandFactory whereby some APIs like GetCommandInfoL could trigger allocations on the wrong heap or signals to the wrong thread. The symptoms were often seen as a crash in the which_00 thread when running ciftest.
* Lots of build fixes for when FSHELL_PROTECTED_UIDS isn't defined and when all capabilities aren't available.
* Added new platform.mmh macro FSHELL_OPEN_SIGNED.
* Open signing of fshell SIS files is now supported for production S60 handsets. Build fshell with the FSHELL_OPEN_SIGNED macro defined (and without defining FSHELL_CAP_ALL or FSHELL_PROTECTED_UIDS) in your platform.mmh and submit \epoc32\fshell\fshell.unsigned.sis to https://www.symbiansigned.com/app/page/public/openSignedOnline.do . The following commands are not available when using Open Signing due to Platform Security restrictions: fdb; kerninfo; chunkinfo; svrinfo; objinfo; sudo; fsck; localdrive; ramdefrag; readmem; reboot; setcritical; setpriority. Others such as chkdeps, e32header, ps, and fshell itself will run but in a restricted capacity (for example, fshell will no longer allow you to modify files in the \sys\bin directory).
* Removed commands objinfo, svrinfo, chunkinfo, readmem, fsck completely when memory access isn't present - previously they would still appear in the help but would give an error if you tried to run them.
# var.cif
#
# Copyright (c) 2010 Accenture. All rights reserved.
# This component and the accompanying materials are made available
# under the terms of the "Eclipse Public License v1.0"
# which accompanies this distribution, and is available
# at the URL "http://www.eclipse.org/legal/epl-v10.html".
#
# Initial Contributors:
# Accenture - Initial contribution
#
==name var
==short-description
Perform an operation involving environment variables.
==long-description
This command returns zero (KErrNone) in the success case, and a non-zero positive code otherwise. Usage:
var SOMETHING defined # Doesn't cause an error, returns '1'
var SOMETHING defined && echo Defined # Nothing is echoed
export SOMETHING 1
var SOMETHING defined && echo Defined # "Defined" will be printed
var SOMETHING == 1 && echo "Equal" # "Equal" will be printed
var SOMETHING add 3 && echo "$SOMETHING" # $SOMETHING now has value "4"
C<==> and C<!=> are text comparisons not numerical, and all environment variables are strings, so the following will I<not> work:
export VAL 16
var VAL == 0x10 && echo Equal # Error! "16" does not equal "0x10"
==argument string variable
The environment variable to be operated on.
==argument enum operation
The operation to be performed.
==enum-value defined
Test if the specified environment variable is defined.
==enum-value not-defined
Opposite of C<defined>.
==enum-value ==
Tests if the specified environment variable is an exact string match for the supplied argument.
==enum-value !=
Opposite of C<==>.
==enum-value add
Assume that the specified environment variable holds an integer, and adds the value given by the argument to it. If the variable isn't defined or doesn't contain a decimal integer, it is assumed to have value zero.
==enum-value subtract
Subtracts the given value from the environment variable. Semantics as per add.
==enum-value multiply
Multiply the specified environment variable by the given value.
==argument string argument optional
The argument to the operation.
==copyright
Copyright (c) 2006-2010 Accenture. All rights reserved.
==smoke-test
# Tested by fshell-basic-test.script, this section is just so ciftest doesn't report it as a command without any tests