Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 17-Jul-2025 02:45:19 JST Haelwenn /элвэн/ :triskell:

   • anna

   @ska @navi Reminds me of why I'd also do $prefix/include/foo-$major so it's easy to build a previous version for an application that has yet to update it's API calls, yet still having current version of libfoo installed for the other software that it might depend on (and not all distros split packages between .so and headers anyway, like gentoo doesn't).

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 17-Jul-2025 03:13:54 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • anna
     @navi @ska Well stuff which uses hardcoded values instead of pkg-config ought to break.
     
     Seen so many doing that, specially with like an: Oh, it's linux / "non-apple unix" then, $lib is present, let's go!
     (non-apple unix being all over the place in CMake stuff…)
   • Embed this notice
     anna (navi@social.vlhl.dev)'s status on Thursday, 17-Jul-2025 03:13:55 JST anna

     in reply to
     @lanodan @ska at least with pkg-config it's easier to abstract moving the headers or adding libdirs to the search path (just changing the .pc file suffices)
     
     it gets a lot annoying when someone's handcrafted makefile does -lfoo directly, with no checks no anything