Update library linking proposal. #17
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bobot
reviewed
Aug 21, 2020
The order is inconsistent with both ocaml's `-I` and gcc's `-L`.
dbuenzli
commented
Sep 22, 2020
dbuenzli
commented
Sep 23, 2020
The naming is consistent with what is done at the compilation unit level.
Member
|
Discussion also at: https://discuss.ocaml.org/t/ocaml-rfc-17-library-linking-proposal/7499 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update to the library linking RFC resolves a backward compatibilty concern that was raised with the previous one. Namely the fact library dependencies embedded in archives where resolved when archives were given directly to the compiler as arguments.
In this new version when an archive is specified on the command line (or
#loaded inocaml) its library dependencies are not resolved.In order to resolve they need to be specified via the
-requireoption (or#requiredirective) which is now overloaded in certain contexts to take either a library name to be resolved in theOCAMLPATHor a direct path to an archive file.This provides more control over which dependencies should be resolved than the
-noautoliblinkflag of the previous version which would disable resolution in bulk for the whole compiler invocation.This does not change anything to the
dune/ocamlfindcompatibility story. However it gives more control for people which will want to use the bare compiler support in their build system (e.g.make).Also for the tools that intepret
OCAMLPATHa-L PATHoption is added to allow to prepend a path to theOCAMLPATH.Rendered markdown