`stack install` for library targets -


i'd have similar functionality stack install (e.g. --copy-bins flag) executables, libraries.

currently, have stack build , manually find libhs*-<version>-<fingerprint>.a files in .stack-work. problematic/uncomfy 2 reason:

  1. i have rely on internal folder structure of stack (reliable enough, though)
  2. i have manually rid of fingerprint , version

well, work around both, guess, i'd know if might available/sensible implement.


some background, may or may not relevant question rather motivation:

i playing around https://hackage.haskell.org/package/dynamic-loader-0.0/docs/system-plugins-dynamicloader.html , want provide realistic example can, plan compile package's object code *.a (containing compilation of multiple modules) want link in @ runtime.

what want works trivial single module files, need use loadmodule. i'm tinkering around loadpackage.


Comments

Popular posts from this blog

serialization - Convert Any type in scala to Array[Byte] and back -

matplotlib support failed in PyCharm on OSX -

python - Matplotlib: TypeError: 'AxesSubplot' object is not callable -