On Tue, 15 Oct 2024 23:06:15 +0100
Stuart Henderson <stu@spacehopper.org> wrote:
>
> I haven't been following this (and don't really do games on OpenBSD
> apart the occasional bit of xonix). But AFAIK the backtrace functions
> (in libexecinfo on OpenBSD and IIRC FreeBSD, and glibc on Linux)
> aren't expected to require the program using those functions to need
> c++ to link.
>
> (In the case of OpenBSD's libexecinfo, in gnu/lib, it reaches into
> llvm/libcxx dirs for the parts needed so that it's self contained).
>
Well then that makes the choice the upstream dev and I made more
reasonable, right?
To clarify, the OpenBSD target upstream *does not*
use `$(CXX)` to build. Like you said, it isn't expected on modern
"regular" unices, such as FreeBSD, OpenBSD or Linux, to require C++ to
link. This port does not include this LINK variable patch.
I was only mentioning is as in the future, for
them, or perhaps us, I included a LINK variable to be used. For
example, as it stands right now, the HaikuOS target hardcodes a link to
`-lstdc++`, which may not be ideal in the long run. Having this LINK
variable included upstream, can be more extensible to other systems,
not just OpenBSD, FreeBSD, or Linux. Might not be all that useful for
us, but I wanted to help where i could.
Peace-
--
iz (they/them)
> i like to say mundane things,
> there are too many uninteresting things
> that go unnoticed.
izder456 (dot) neocities (dot) org
No comments:
Post a Comment