On Thu, Nov 01, 2018 at 03:22:52AM +0000 I heard the voice of
Yumekui Neru, and lo! it spake thus:
>
> This does make the build successful too.
Excellent. Landed in trunk.
> My understanding from when I asked around for help with the issue
> was that ctwm used to depend on ${CTWMLIBS} but it is now the new
> ctwmlib that directly depends on them and that they should go there
> during linking (hence the suggested replacement).
It's still ctwm that needs them; ctwmlib is just a mild hack in
building to roll up all the actual objects in one ball, to then link
with a thoroughly trivial main() into the actual binary. That way we
can just use the lib for building unit tests as well, which makes them
easy [to compile, anyway].
The better solution is probably to use cmake's "Object Libraries"
(which are just an internal rollup of the .o's) instead of making a
real static library. However, doing that means we'll have to start
requiring cmake 3.1. Which we probably can and should (we claim 2.6+,
but I wouldn't be surprised if we'd managed to break <2.8 at least,
and maybe <3+ by now), but I figured I'd wait 'till we had some other
big argument to tire everybody out before I brought that up :)
--
Matthew Fuller (MF4839) | [email protected]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
