/[gentoo-x86]/eclass/toolchain-funcs.eclass
Gentoo

Diff of /eclass/toolchain-funcs.eclass

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.107 Revision 1.112
1# Copyright 1999-2007 Gentoo Foundation 1# Copyright 1999-2011 Gentoo Foundation
2# Distributed under the terms of the GNU General Public License v2 2# Distributed under the terms of the GNU General Public License v2
3# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain-funcs.eclass,v 1.107 2011/09/12 21:42:08 vapier Exp $ 3# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain-funcs.eclass,v 1.112 2012/06/14 03:38:51 vapier Exp $
4 4
5# @ECLASS: toolchain-funcs.eclass 5# @ECLASS: toolchain-funcs.eclass
6# @MAINTAINER: 6# @MAINTAINER:
7# Toolchain Ninjas <toolchain@gentoo.org> 7# Toolchain Ninjas <toolchain@gentoo.org>
8# @BLURB: functions to query common info about the toolchain 8# @BLURB: functions to query common info about the toolchain
11# for gleaning useful information about the toolchain and to simplify 11# for gleaning useful information about the toolchain and to simplify
12# ugly things like cross-compiling and multilib. All of this is done 12# ugly things like cross-compiling and multilib. All of this is done
13# in such a way that you can rely on the function always returning 13# in such a way that you can rely on the function always returning
14# something sane. 14# something sane.
15 15
16___ECLASS_RECUR_TOOLCHAIN_FUNCS="yes" 16if [[ ${___ECLASS_ONCE_TOOLCHAIN_FUNCS} != "recur -_+^+_- spank" ]] ; then
17[[ -z ${___ECLASS_RECUR_MULTILIB} ]] && inherit multilib 17___ECLASS_ONCE_TOOLCHAIN_FUNCS="recur -_+^+_- spank"
18
19inherit multilib
18 20
19DESCRIPTION="Based on the ${ECLASS} eclass" 21DESCRIPTION="Based on the ${ECLASS} eclass"
20 22
21# tc-getPROG <VAR [search vars]> <default> [tuple] 23# tc-getPROG <VAR [search vars]> <default> [tuple]
22_tc-getPROG() { 24_tc-getPROG() {
175# @FUNCTION: tc-is-softfloat 177# @FUNCTION: tc-is-softfloat
176# @DESCRIPTION: 178# @DESCRIPTION:
177# See if this toolchain is a softfloat based one. 179# See if this toolchain is a softfloat based one.
178# @CODE 180# @CODE
179# The possible return values: 181# The possible return values:
180# - only: the target is always softfloat (never had fpu) 182# - only: the target is always softfloat (never had fpu)
181# - yes: the target should support softfloat 183# - yes: the target should support softfloat
184# - softfp: (arm specific) the target should use hardfloat insns, but softfloat calling convention
182# - no: the target doesn't support softfloat 185# - no: the target doesn't support softfloat
183# @CODE 186# @CODE
184# This allows us to react differently where packages accept 187# This allows us to react differently where packages accept
185# softfloat flags in the case where support is optional, but 188# softfloat flags in the case where support is optional, but
186# rejects softfloat flags where the target always lacks an fpu. 189# rejects softfloat flags where the target always lacks an fpu.
187tc-is-softfloat() { 190tc-is-softfloat() {
191 local CTARGET=${CTARGET:-${CHOST}}
188 case ${CTARGET} in 192 case ${CTARGET} in
189 bfin*|h8300*) 193 bfin*|h8300*)
190 echo "only" ;; 194 echo "only" ;;
191 *) 195 *)
192 [[ ${CTARGET//_/-} == *-softfloat-* ]] \ 196 if [[ ${CTARGET//_/-} == *-softfloat-* ]] ; then
193 && echo "yes" \ 197 echo "yes"
198 elif [[ ${CTARGET//_/-} == *-softfp-* ]] ; then
199 echo "softfp"
200 else
194 || echo "no" 201 echo "no"
202 fi
195 ;; 203 ;;
196 esac 204 esac
197}
198
199# @FUNCTION: tc-is-hardfloat
200# @DESCRIPTION:
201# See if this toolchain is a hardfloat based one.
202# @CODE
203# The possible return values:
204# - yes: the target should support hardfloat
205# - no: the target doesn't support hardfloat
206tc-is-hardfloat() {
207 [[ ${CTARGET//_/-} == *-hardfloat-* ]] \
208 && echo "yes" \
209 || echo "no"
210} 205}
211 206
212# @FUNCTION: tc-is-static-only 207# @FUNCTION: tc-is-static-only
213# @DESCRIPTION: 208# @DESCRIPTION:
214# Return shell true if the target does not support shared libs, shell false 209# Return shell true if the target does not support shared libs, shell false
216tc-is-static-only() { 211tc-is-static-only() {
217 local host=${CTARGET:-${CHOST}} 212 local host=${CTARGET:-${CHOST}}
218 213
219 # *MiNT doesn't have shared libraries, only platform so far 214 # *MiNT doesn't have shared libraries, only platform so far
220 return $([[ ${host} == *-mint* ]]) 215 return $([[ ${host} == *-mint* ]])
216}
217
218# @FUNCTION: tc-export_build_env
219# @USAGE: [compiler variables]
220# @DESCRIPTION:
221# Export common build related compiler settings.
222tc-export_build_env() {
223 tc-export "$@"
224 : ${BUILD_CFLAGS:=-O1 -pipe}
225 : ${BUILD_CXXFLAGS:=-O1 -pipe}
226 : ${BUILD_CPPFLAGS:=}
227 : ${BUILD_LDFLAGS:=}
228 export BUILD_{C,CXX,CPP,LD}FLAGS
229}
230
231# @FUNCTION: tc-env_build
232# @USAGE: <command> [command args]
233# @INTERNAL
234# @DESCRIPTION:
235# Setup the compile environment to the build tools and then execute the
236# specified command. We use tc-getBUILD_XX here so that we work with
237# all of the semi-[non-]standard env vars like $BUILD_CC which often
238# the target build system does not check.
239tc-env_build() {
240 tc-export_build_env
241 CFLAGS=${BUILD_CFLAGS} \
242 CXXFLAGS=${BUILD_CXXFLAGS} \
243 CPPFLAGS=${BUILD_CPPFLAGS} \
244 LDFLAGS=${BUILD_LDFLAGS} \
245 AR=$(tc-getBUILD_AR) \
246 AS=$(tc-getBUILD_AS) \
247 CC=$(tc-getBUILD_CC) \
248 CPP=$(tc-getBUILD_CPP) \
249 CXX=$(tc-getBUILD_CXX) \
250 LD=$(tc-getBUILD_LD) \
251 NM=$(tc-getBUILD_NM) \
252 PKG_CONFIG=$(tc-getBUILD_PKG_CONFIG) \
253 RANLIB=$(tc-getBUILD_RANLIB) \
254 "$@"
255}
256
257# @FUNCTION: econf_build
258# @USAGE: [econf flags]
259# @DESCRIPTION:
260# Sometimes we need to locally build up some tools to run on CBUILD because
261# the package has helper utils which are compiled+executed when compiling.
262# This won't work when cross-compiling as the CHOST is set to a target which
263# we cannot natively execute.
264#
265# For example, the python package will build up a local python binary using
266# a portable build system (configure+make), but then use that binary to run
267# local python scripts to build up other components of the overall python.
268# We cannot rely on the python binary in $PATH as that often times will be
269# a different version, or not even installed in the first place. Instead,
270# we compile the code in a different directory to run on CBUILD, and then
271# use that binary when compiling the main package to run on CHOST.
272#
273# For example, with newer EAPIs, you'd do something like:
274# @CODE
275# src_configure() {
276# ECONF_SOURCE=${S}
277# if tc-is-cross-compiler ; then
278# mkdir "${WORKDIR}"/${CBUILD}
279# pushd "${WORKDIR}"/${CBUILD} >/dev/null
280# econf_build --disable-some-unused-stuff
281# popd >/dev/null
282# fi
283# ... normal build paths ...
284# }
285# src_compile() {
286# if tc-is-cross-compiler ; then
287# pushd "${WORKDIR}"/${CBUILD} >/dev/null
288# emake one-or-two-build-tools
289# ln/mv build-tools to normal build paths in ${S}/
290# popd >/dev/null
291# fi
292# ... normal build paths ...
293# }
294# @CODE
295econf_build() {
296 tc-env_build econf --build=${CBUILD:-${CHOST}} "$@"
221} 297}
222 298
223# @FUNCTION: tc-has-openmp 299# @FUNCTION: tc-has-openmp
224# @USAGE: [toolchain prefix] 300# @USAGE: [toolchain prefix]
225# @DESCRIPTION: 301# @DESCRIPTION:
690 ;; 766 ;;
691 esac 767 esac
692 fperms a+x "/usr/${libdir}/${lib}" || die "could not change perms on ${lib}" 768 fperms a+x "/usr/${libdir}/${lib}" || die "could not change perms on ${lib}"
693 done 769 done
694} 770}
771
772fi

Legend:
Removed from v.1.107  
changed lines
  Added in v.1.112

  ViewVC Help
Powered by ViewVC 1.1.20