| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Set the assembly compiler and flags directly instead of implicitly
forcing them in the build rule.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Split multi-argument CC/CXX/FC into a CMake array consisting of one
element containing the compiler path (name) and the other containing all
command-line options, space-separated. This is how CMake splits
the environment variables CC/CXX/FC internally.
The alternative would be to set CC/CXX/FC directly, and let CMake handle
the splitting. However, changing that had unforeseen consequences like
assembler not being set correctly (#601292) which in turn was impossible
to set via environment variables due to bugs in CMake.
Therefore, splitting the values into CMAKE_*_COMPILER correctly seems
the simplest and safest way forward, at least until we can rely on fixed
CMake versions being sufficiently deployed.
|
|
|
|
| |
The latter doesnt work reliably with latest oasis versions.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
#601326)."
This reverts commit 00b1fa774f05e16d855dbf39e42d2eb6a7483ab7.
At this time the gtk+:2 dependencies are still required.
|
|
|
|
|
| |
Revert using CC/CXX/FC envvars since it breaks implicit assembler
override and is non-trivial to fix, #601292.
|
|
|
|
|
|
| |
Revert setting ASM=${CC}. It turns out that CMake is not splitting
arguments in ASM like in CC, so this effectively broke all multilib
builds.
|
|
|
|
| |
Support older EAPIs with epatch_user.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use <CMAKE_ASM_COMPILER> in the assembly compile command in order to fix
building assembly files. It turns out that <CMAKE_C_COMPILER> is no
longer correctly evaluated in that command once it is no longer set
explicitly in the toolchain file and passed through the environment
instead.
Pass ASM and ASMFLAGS (equal to CC and CFLAGS) appropriately to enforce
using the correct compiler.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We need at least Cargo 0.13.0 to use the new bits in this eclass.
Signed-off-by: Doug Goldstein <cardoe@gentoo.org>
|
|
|
|
|
|
|
|
| |
Add support for newer dependency vendoring which allows us to download
the dependencies with the package manager and just have cargo use that
to compile the package.
Signed-off-by: Doug Goldstein <cardoe@gentoo.org>
|
|
|
|
|
|
|
|
|
| |
Originally this eclass only had the bits to build cargo and not other
packages built with cargo. Cargo is a special case and needs to override
some parts. This adds the generic case for normal cargo packages,
allowing for debug and release builds of packages as well.
Signed-off-by: Doug Goldstein <cardoe@gentoo.org>
|
|
|
|
|
|
| |
Wipe out the default compiler & linker flags that are forced by CMake
for the standard build types. This improves the sanity of the build if
we are forced to use one of those types.
|
|
|
|
|
|
|
| |
Declare the CMAKE_GENTOO_BUILD cache variable to indicate that a Gentoo
package build is being performed. This variable enables Gentoo code
paths in CMake modules without the necessity of setting a custom
CMAKE_BUILD_TYPE.
|
| |
|
|
|
|
| |
This fixes Gentoo bug #601134.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Move CMAKE_AR & CMAKE_RANLIB definitions into the toolchain file. It
seems to make more sense there than in build rules.
|
| |
|
| |
|
|
|
|
|
| |
Makes sure that 5.8 LTS stable branch does not raise FRAMEWORKS_MINIMAL
Also bumping FRAMEWORKS_MINIMAL to 5.28.0 for >=Plasma-5.9
|
|
|
|
|
|
|
|
|
|
| |
While some of the Qt4 packages build correctly with -std=gnu++14,
others rely upon std::tr1 and other renamed library items. Because
most of these issues have been resolved upstream in Qt5, the easiest
solution is to ensure Qt4 is always built with -std=gnu++98.
Gentoo-Bug: 582522, 582618, 583744, 583662
Closes: https://github.com/gentoo/gentoo/pull/2908
|
|
|
|
| |
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
| |
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/2550
Signed-off-by: Patrice Clement <monsieurp@gentoo.org>
|
| |
|
|
|
|
|
|
|
| |
This is necessary in case the language packs need to be taken from an
alternative URL instead of the default Mozilla URL.
It is considered to be a drop-in replacement so no changes to existing
mozilla ebuilds are necessary.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently distutils_install_for_testing does not install the complete
egg-info into ${TEST_DIR}. This was first noticed by W. Trevor King
and reported in bug #524322. Based on info found in the related upstream
setuptools bug I added the necessary call to setuptools to create
the complete egg_info.
Without this certain packages (like cryptography) fail during testing
because they use introspection but the metadata isn't available.
Bug: https://bugs.gentoo.org/524322
|
|
|
|
|
|
| |
Thanks Robert Förster for noticing the error.
Bug: https://bugs.gentoo.org/598808
|
| |
|
|
|
|
|
| |
Unconditionally setting FRAMEWORKS_MINIMAL prevents it being overridden in an
ebuild (or somewhere else...).
|
|
|
|
| |
Thanks-to: Arfrever on irc @ #gentoo-kde
|
| |
|
|
|
|
| |
Don't interfere with live ebuild KF5 dep though.
|
|
|
|
| |
5.26.0 is unconditionally required since 6c5d7cc84530d912bb7d6433b54d154f37717e2d.
|
| |
|
| |
|
|
|
|
| |
Reported-by: Laine Gholson <laine.gholson@gmail.com>
|