Re: New fields/flags and semantics for GHCJS

2014-10-31 Thread Luite Stegeman
One more thing I had forgotten to mention, and still need to implement in GHCJS: If a library has web assets, for example CSS files or images for a GUI framework library, they should be listed under `data-files` of a package. The compiler then makes all data directories of dependencies available i

Re: New fields/flags and semantics for GHCJS

2014-10-30 Thread Luite Stegeman
> > > # new js-sources field > > A js-sources field is treated like the c-sources field. JS sources of all > dependencies of a an executable are collected into a big JavaScript file. > GHCJS also outputs some data about the collected files for custom > deployment scripts. > > JS sources are not com

Re: New fields/flags and semantics for GHCJS

2014-10-30 Thread Luite Stegeman
On Wed, Oct 29, 2014 at 2:10 AM, Mikhail Glushenkov < the.dead.shall.r...@gmail.com> wrote: > > The user-visible changes look reasonable in my opinion. Looking > forward to merging your patches! > When merging the latest master I found that ghcjs-options are actually mappended to ghc-options in t

Re: New fields/flags and semantics for GHCJS

2014-10-28 Thread Mikhail Glushenkov
Hi, On 28 October 2014 21:00, Luite Stegeman wrote: > Hi all, > > I've been maintaining a Cabal fork for GHCJS. The GHCJS-specific bits have > been relatively stable for a while now, and are feature complete, apart from > a few small features that I'll complete later this week. > > So I think it'