![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / x11 / xcb-imdkit
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
devel/extra-cmake-modules: Use buildlink3.mk, not TOOL_DEPENDS. This one is borderline: should it be BUILD_DEPENDS or TOOL_DEPENDS? It doesn't appear to vary depending on the build environment, so it doesn't meaningfully describe the cross-builder vs the target system. It is used only at build-time, but it doesn't have any native executables -- they're just source code cmake scripts. For now, it is convenient to use a buildlink3.mk file because this enables us to explicitly expose only files under share/ECM/ -- and not other random files installed in the prefix -- via buildlink3 to keep dependent package builds clean. Eventually we should have the same mechanism for TOOL_DEPENDS but that day has not yet come. This change creates a new use of BUILDLINK_DEPMETHOD build for extra-cmake-modules, which is a priori risky. Fortunately, extra-cmake-modules has no libraries, so this is unlikely to cause trouble.
x11/xcb-imdkit: Update to 1.0.6 Changelog: Some optimizations. Update documents and demos.
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/. Almost all uses, if not all of them, are wrong, according to the semantics of BUILD_DEPENDS (packages built for target available for use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for host available for use _as_ tools at build-time). No change to BUILD_DEPENDS as used correctly inside buildlink3. As proposed on tech-pkg: https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html
*: Re-apply SunOS linker argument removals. These are currently duplicated in mk/platform/SunOS.mk but the generic removals will be removed soon in favour of per-package removals, due to flags getting leaked into installed files.
x11/xcb-imdkit: import xcb-imdkit-1.0.2 xcb-imdkit is an implementation of xim protocol in xcb, comparing with the implementation of IMDkit with Xlib, and xim inside Xlib, it has less memory foot print, better performance, and safer on malformed client.