summaryrefslogtreecommitdiff
path: root/mk/compiler/ccache.mk
AgeCommit message (Collapse)AuthorFilesLines
2009-08-31break dependency loop between ccache and digesttnn1-2/+2
2008-02-07Replaced _PKG_SILENT and _PKG_DEBUG with RUN.rillig1-4/+4
XXX: Why do we have the exactly same code in all the files?
2007-10-16Added the variable CCACHE_BASE, so that a ccache other than the onerillig1-26/+35
installed by devel/ccache can be used. This is especially important for cross-builds. Documented IGNORE_CCACHE. Fixed the double use of the directory ${WRKDIR}/.ccache, which was used both as wrapper directory and as cache directory.
2006-12-15Remove trailing spaces.martti1-2/+2
2006-10-14Added the user-settable variable CCACHE_DIR, so that the cache can berillig1-2/+13
outside of WRKDIR. I don't see a reason for having the cache inside a directory that will go away on "make clean", but I left the default value as is.
2006-07-21"BUILD_ENV" was misnamed. It's actually the environment that is passedjlam1-3/+3
to all internal recursive make processes. As such, rename it to "PKGSRC_MAKE_ENV". XXX Note, some of the usage of this variable in package Makefiles seems XXX incorrect. They probably want "MAKE_ENV", which is the environment XXX passed to the make process when running "make" within ${WRKSRC}.
2005-01-24Merge down deferred EVAL_PREFIX handling from tv-derecurse branch.tv1-2/+1
Also move its definition later in bsd.pkg.mk, so that it actually works for compiler/*.mk (which is why those files originally had to provide "defaults" for their variables -- they never did get evaluated).
2005-01-12Correct my name to what I legally use.jlam1-2/+2
2005-01-12Put a TNF copyright on files that I authored.jlam1-1/+36
2005-01-10_ALIASES.<wrappee> should be cumulative.jlam1-3/+3
2005-01-10Whitespace nits.jlam1-3/+3
2004-11-30Modify the way that the toolchain variables, e.g. CC, CPP, CXX, LD, etc.,jlam1-10/+18
are handled. The idea now is to simply remove the paths in the values of these variables, leaving behind only the basename plus any arguments, e.g.: CC= /usr/local/bin/gcc becomes CC= gcc CPP= /usr/local/bin/gcc -E becomes CPP= gcc -E The wrapper scripts are generated for every unique executable mentioned by the toolchain variables, so for the example above, only a "gcc" wrapper script is generated for ${CC} and ${CPP}. PKG_{CC,CPP,CXX,etc.} are the paths to the executables wrapped by the wrapper scripts. Note that it's now possible to set "CC" to something more than just the path to the compiler, e.g. CC= cc -ffast-math -funroll-loops -fomit-frame-pointer and the full value of ${CC} will be passed through via CONFIGURE_ENV and MAKE_ENV.
2004-11-17For some reason EVAL_PREFIX is not properly using the _DEFAULT values, sotv1-1/+2
re-add the ?= assignments. (Will be fixed properly later.)
2004-11-17Don't check _*PREFIX/bin for the requested compiler hook program. Iftv1-13/+8
PKGSRC_COMPILER requested it, assume that it's available, so that compilation will (properly) fail if the hook program is somehow not correctly installed.
2004-10-09devel/patch is needed by some platforms in order to build ccache, so don'ttv1-2/+2
cache that one either.
2004-02-22Allow setting CCACHE_DIR in the environment or in /etc/mk.conf.jlam1-1/+5
2004-02-21Use BUILD_ENV instead of just {CONFIGURE,MAKE}_ENV to pass CCACHE_HASHCCjlam1-3/+2
to ccache. This now correctly passes CCACHE_HASHCC to ccache if the package has a custom do-build target that invokes ${CC} directly.
2004-02-18* Move pkgsrc/mk/compiler/bsd.compiler.mk to pkgsrc/mk/compiler.mk.jlam1-40/+29
Package Makefiles may now directly include compiler.mk. * Don't include compiler.mk within bsd.prefs.mk any longer. It was only included for the purposes of defining CC_VERSION. Packages that want to test the value of CC_VERSION should now first include "../../mk/compiler.mk". Any GCC_REQD statements in package Makefiles should be set before compiler.mk is included. * Simpllfy pkgsrc/mk/compiler/*.mk files as a result of not needing to be included indirectly by bsd.prefs.mk. We remove the special handling associated with detecting whether the file was included from within bsd.prefs.mk. These files are now much more straightforward to write and understand. * G/C the BSD_PREFS_MK stack mechanism as the only users (compiler/*) no longer need it. * Ensure that directories are prepended to the PATH only from within bsd.pkg.mk.
2004-02-12Generate a more informative string "CC_VERSION_STRING" that is passed tojlam1-1/+7
ccache as the compiler information to hash.
2004-02-09Don't have recursive variable definitions.jlam1-3/+3
2004-02-08* Let CC/CXX/CPP/FC always point to the compiler used in the actualjlam1-5/+7
building of software. For packages that use either buildlink2 or buildlink3, this would be the wrapper script in ${BUILDLINK_DIR}. * Garbage-collect _BLNK_WRAP_SETENV.* as those are not needed after the above changes. Configure and make processes will automatically find the right compilers in the PATH. * PKGLIBTOOL and PKGSHLIBTOOL are no longer needed since LIBTOOL and SHLIBTOOL point to the correct libtools regardless of any USE_BUILDLINK[23] definitions.
2004-02-07Symlink the compiler into ${WRKDIR} so that there's a consistent path tojlam1-5/+12
the compiler and that it's behind .tools/bin and .buildlink/bin, regardless of whether or not we're using gcc3-c or not, or whether it's been installed yet in the process of satisfying dependencies, etc.
2004-02-06Hiding the PATH from certain phases of the build only accidentally workedjlam1-3/+2
due to a type on gcc.mk that causes the ${_GCC_PREFIX}/bin to always be prepended to the PATH. The problem that was hiding was "make" resolving to ${TOOLS_DIR}/bin/make if the package used GNU make, which broke building since the package Makefile is a BSD Makefile and we passed PATH to some phases of the build. Fix this by expanding MAKE to the full path to ${MAKE} in bsd.prefs.mk. We also garbage collect the now useless checks for PHASES_AFTER_BUILDLINK that cluttered the PREPEND_PATH code.
2004-02-06We only prepend a directory to the PATH if we haven't already done sojlam1-2/+6
(by checking PREPEND_PATH) and only for those phases of the build that care about the PATH (buildlink or later). We also pass the PATH to those same phases of the build so that executing ${CC} will work correctly from custom {pre,do,post}-* targets that occur at buildlink time or later.
2004-02-05Simpilfy the test for whether we're inside bsd.prefs.mk.jlam1-2/+2
2004-02-05Allow bsd.compiler.mk to be included by both bsd.prefs.mk and bsd.pkg.mk.jlam1-31/+42
Any additions to DEPENDS/BUILD_DEPENDS or inclusions of buildlink[23].mk files are deferred till bsd.compiler.mk is included by bsd.pkg.mk. We allow bsd.compiler.mk to be included by bsd.prefs.mk solely for the purpose of setting CC_VERSION properly for use by package Makefiles. There is the surprising behaviour that CC_VERSION won't necessarily have the correct value at all times until after "make extract" has been completed (dependencies are installed before "make extract"), so package Makefile writers should keep that in mind. Just to note that this is _existing_ behaviour that's preserved by these changes.
2004-02-03Fix a pervasive cut-and-paste bug: change a = back into a +=. Noted byjlam1-2/+2
David Brownlee in private email.
2004-02-02Only prepend the compiler package location to the PATH if we actuallyjlam1-3/+4
request a compiler that's supported by the named compiler package.
2004-02-02Whitespace fixes.jlam1-5/+5
2004-02-02Support a new variable in package Makefiles:jlam1-4/+24
USE_LANGUAGES Lists the languages used in the source code of the package, and is used to determine the correct compilers to install. Valid values are: c, c++, fortran, java, objc. The default is "c". Packages that don't need any compilers and set this variable to an empty value, e.g. "USE_LANGUAGES=". This can probably be combined in some smart way with setting USE_GCC_SHLIBS and USE_FORTRAN automatically.
2004-02-01Match names for the C and C++ compilers with the ones we're masquerading.jlam1-3/+3
This should allow ccache to work with SunPro and MIPSpro compilers.
2004-02-01New compiler specification framework, based on mk/compiler.mk. Thejlam1-0/+45
changes from the old compiler.mk are: * Split apart the compiler-specific logic into separate files. This should make supporting other compilers a bit easier. * Deprecate all of the USE_* compiler.mk variables, e.g. USE_GCC[23], USE_SUNPRO, etc. It's all replaced with a new PKGSRC_COMPILER variable. * Clean up the GCC handling so that it's all controlled by a single variable GCC_REQD. The following behaviour is expected: (a) If USE_PKGSRC_GCC is defined, then pretend there is no GCC on the system. (b) If there is no GCC, then the appropriate GCC corresponding to GCC_REQD is installed and used. (c) If there is a GCC, if it satisfies GCC_REQD, then use it; otherwise install and use the appropriate GCC package. (d) If lang/gcc is installed and GCC_REQD > 2.95.3, then lang/gcc3 is installed and used. (e) If lang/gcc3 is installed and GCC_REQD = 2.95.3, then gcc3 is still used instead of installing lang/gcc. New features include: * PKGSRC_COMPILER takes a list of values specifying the chain of compilers to call when building packages. Valid values are: distcc distributed C/C++ (chainable) ccache compiler cache (chainable) gcc GNU mipspro Silicon Graphics, Inc. MIPSpro sunpro Sun Microsystems, Inc. WorkShip/Forte/Sun ONE Studio The default is "gcc". You can use ccache and/or distcc with an appropriate PKGSRC_COMPILER setting, e.g. "ccache distcc gcc". * Change GCC_REQD to hold a list of values that we scan through to find the highest version of GCC required by the build. Package Makefiles should now do "GCC_REQD+=..." instead of "GCC_REQD=...".
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-15 15:18:45 +0000