[SERVER-63568] Check for undefined LIBDEPS in current build config Created: 11/Feb/22  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Mathias Stearn Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Participants:

 Description   

Right now LIBDEPS works by file name, rather than by a logical "library". This means that if you add a LIBDEP for a library that doesn't exist, you won't get an error until link time when it says something like "can't find file build/foo/libbar.so". Even worse, if there happens to already be a file with that name, eg because you renamed a library and missed fixing a LIBDEP (or a new one was added by a rebase), it will continue to use whatever file happens to be there leading to very confusing bugs.

We should check for this at configure time instead and fail the build early. If for some reason we can't do it at compile time, we should at least be able to do it as an input dependency for linking, so that we never try to link against a library we aren't building (except when intentionally linking against a prebuilt third-party lib).


Generated at Thu Feb 08 05:58:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.