We need a way to pass flags to rombuilds in Raptor via extension flm interfaces, so that the CPP pass
of the rom input files can be informed what toolchain we are building with and conditionally
include or exclude files depending on whether the toolchain could build them.
/*
* Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).
* All rights reserved.
* This component and the accompanying materials are made available
* under the terms of the License "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:
* Nokia Corporation - initial contribution.
*
* Contributors:
*
* Description:
*
*/
#ifndef OST_IBY
#define OST_IBY
//Put kernel side DLLs in the core image on NAND configurations
//since that's where the majority of the client code will also be.
//This also works for NOR configurations since then the 'core' image is
//the entire ROM and there's no ROFS.
//ROM_IMAGE[0] device[VARID]=ABI_DIR\DEBUG_DIR\e32ostkernel.dll sys\bin\e32ostkernel.dll
//ROM_IMAGE[0] device[VARID]=ABI_DIR\DEBUG_DIR\e32ostkernelstubbed.dll sys\bin\e32ostkernelstubbed.dll
file=ABI_DIR\DEBUG_DIR\ostuser.dll sys\bin\ostuser.dll
file=ABI_DIR\DEBUG_DIR\ostuserstubbed.dll sys\bin\ostuserstubbed.dll
#endif