Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-63568

Check for undefined LIBDEPS in current build config

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Server Development Platform

    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).

      Attachments

        Activity

          People

            backlog-server-devplatform [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: