You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#127 gave us a more flexible way to configure paths, we just need to make effective use of it in distributions.
There are a few scenarios:
a developer wants to build a distribution and run it in place
we want to distribute a tarball that can be extracted to any location on a filesystem
we want to distribute a package manager-specific artifact like a .rpm or Homebrew formula
Right now the Makefile optimizes for case 3 by baking in /usr/local/ or C:\Program Files\... into the make dist target. We need to make it possible to support cases 1 and 2 as well.
1 and 2 are likely to end up looking very similar (i.e., a distribution directory with /bin/, /share/cryptol/, etc). However we may want to add some sort of conditional compilation step so that those paths are not baked into the module search path; instead we should just rely on our heuristics for determining paths relative from the executable to avoid accidentally bringing in system-wide stuff that doesn't belong to us.
The text was updated successfully, but these errors were encountered:
#127 gave us a more flexible way to configure paths, we just need to make effective use of it in distributions.
There are a few scenarios:
.rpm
or Homebrew formulaRight now the Makefile optimizes for case 3 by baking in
/usr/local/
orC:\Program Files\...
into themake dist
target. We need to make it possible to support cases 1 and 2 as well.1 and 2 are likely to end up looking very similar (i.e., a distribution directory with
/bin/
,/share/cryptol/
, etc). However we may want to add some sort of conditional compilation step so that those paths are not baked into the module search path; instead we should just rely on our heuristics for determining paths relative from the executable to avoid accidentally bringing in system-wide stuff that doesn't belong to us.The text was updated successfully, but these errors were encountered: