[GCCE] We need a way for the HAL config extension to parameterise the HAL config file (.hcf) that will be used, depending upon
the toolchain we are building with. E.g. if we are building BeagleBoard with RVCT we can configure hardware floating point
because we have ARM's vfp math libraries; if we are building it with GCC, we lack this library support.
// Copyright (c) 2006-2009 Nokia Corporation and/or its subsidiary(-ies).
// All rights reserved.
// This component and the accompanying materials are made available
// under the terms of "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:
// Implementation of the Class StdExeTarget for the elf2e32 tool
// @internalComponent
// @released
//
//
#include "stdexe_target.h"
/**
Constructor for the StdExeTarget Class
@internalComponent
@released
*/
StdExeTarget::StdExeTarget(ParameterListInterface* aParameterListInterface):
ExportTypeFBTarget(aParameterListInterface)
{
}
/**
Destructor for the StdExeTarget Class
@internalComponent
@released
*/
StdExeTarget::~StdExeTarget(){
}
/**
Function to check if the provided input is a DLL.
@internalComponent
@released
@result False since StdExe Target is an Exe.
*/
bool StdExeTarget::ImageIsDll()
{
return false;
}
/**
Function to check if writable data is allowed.
@internalComponent
@released
@result True, since STDEXE targets can have writable data
*/
bool StdExeTarget::AllowDllData()
{
return true;
}
/**
Function to write E32 image. Here, no def file or Dso file is generated.
@internalComponent
@released
@result void
*/
void StdExeTarget::GenerateOutput()
{
WriteE32();
}
bool StdExeTarget::WarnForNewExports()
{
return false;
}