[MacPorts] #60672: ispc: Why doesn't it build with ispc-clang?
MacPorts
noreply at macports.org
Thu Jun 18 08:06:18 UTC 2020
#60672: ispc: Why doesn't it build with ispc-clang?
-------------------------------+----------------------
Reporter: ryandesign | Owner: tenomoto
Type: enhancement | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.6.2
Resolution: wontfix | Keywords:
Port: ispc, ispc-clang |
-------------------------------+----------------------
Comment (by cjones051073):
Its only purpose is to provide static libraries, built with the custom
options required for ispc. ispc requires a number of features, asserts and
dump, that are not enabled in the main clang compilers, and which it would
be inappropriate to do by default.
Its called ispc-clang because ispc requires more than just the LLVM
libraries, but the clang static libraries as well. The clang compiler part
that comes along as well it not used, but also does no harm to the ispc
build.
If you think the port description does not explain this well enough,
please feel free to improve it
{{{
Description: Clang build specifically for ispc compiler. NOT TO
BE USED IN GENERAL. This build is specifically tuned to satisfy the
requirements of ispc which uses it as a build
dependency only. Has assertions and dump enabled by default, which is not
the case
in the primary MacPorts LLVM/Clang builds.
}}}
--
Ticket URL: <https://trac.macports.org/ticket/60672#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list