-
Notifications
You must be signed in to change notification settings - Fork 16
Support executable-only packages and non-Haskell libraries #4
Comments
There are a couple more ones you'll want.
|
Do you mean some packages specifically require |
Oh, nevermind I didn't review the code carefully enough to notice those libraries were already handled. |
Work in progress report: We can now easily determine what are the exact executable-only packages and non-Haskell libraries needed to install any Cabal package.
This work would benefit from |
A proper implementation of my ideas for solving this issue ought to be done as an improvement to Cabal. My first step towards this (PR haskell/cabal#1977) has been stuck in the review pipeline for a while now. I am leaving this for later, as there is now another way to achieve the same results. |
Pre- and post-build hooks are now included, hashed and tracked as dependencies. This work turned out to be a great start towards complete automation. It is now possible to automatically deploy extra apps with a single Halcyon invocation. For example, here’s how to deploy Idris in 0m51.807s:
Support for non-Haskell libraries is now tracked as #33. |
Executable-only packages needed as Non-Haskell libraries can be declared as native OS packages in |
Add uniform support for dependencies which may be Haskell executable-only packages or non-Haskell libraries.
Relevant issues:
Examples:
language-javascript
andhaskell-src-exts
needalex
andhappy
type-eq
needscpphs
pcre-light
needslibpcre
The text was updated successfully, but these errors were encountered: