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.
#!fshell
# fshell-scriptcif-test.script
#
# 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
#
source $SCRIPT_PATH\errordef.script
export QUIET "2>&1 >/dev/null" # Used to quieten the things that we're fully expecting to fail
# The things that should suceed use "|| $Error", the things that should fail use $QUIET and "&& $Error" in case they actually succeed when the shouldn't
fshell $SCRIPT_PATH\tscriptargs.script abc123 || $Error
fshell $SCRIPT_PATH\tscriptargs.script $QUIET && $Error
export EXPECTEDMYOPTIONALARG optionalarg
fshell $SCRIPT_PATH\tscriptargs.script abc123 optionalarg || $Error
fshell $SCRIPT_PATH\tscriptargs.script abc123 $QUIET && $Error
fshell $SCRIPT_PATH\tscriptargs.script abc123 wrongoptionalarg $QUIET && $Error
export EXPECTEDMYOPTIONALARG
# Check that the arguments to the script are being set as local environment variables and so don't pollute our env
var myarg not-defined || $Error # Just to make sure our env is sane to start with
source $SCRIPT_PATH\tscriptargs.script abc123 || $Error
var myarg not-defined || $Error
# Now test that even if we define a var of the same name, we don't see the definition from the child script
export myarg "Something that isn't abc123."
source $SCRIPT_PATH\tscriptargs.script abc123 || $Error
var myarg == "Something that isn't abc123." || $Error
fshell tlotsofscriptargs abc123 123 0x123 $SCRIPT_PATHtlotsofscriptargs.script 3.141 enumsecondvalue || $Error