hsfcsh: Incremental builder for flash

[ bsd3, development, program ] [ Propose Tags ]

It is a wrapper around fcsh. It allows to build flash/flex project incrementally. Can be used from Makefile

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS] 0.0.1
Dependencies base (>=4 && <5), hdaemonize (>=0.4 && <0.5), hslogger (>=1.1 && <1.2), network (>=2 && <3), process (>=1 && <2) [details]
License BSD-3-Clause
Author Yuras Shumovich
Maintainer shumovichy@gmail.com
Category Development
Home page https://github.com/Yuras/hsfcsh
Source repo head: git clone git@github.com:Yuras/hsfcsh.git
Uploaded by YurasShumovich at 2011-09-02T16:34:01Z
Reverse Dependencies 1 direct, 0 indirect [details]
Executables hsfcsh_do, hsfcsh
Downloads 1188 total (6 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
Successful builds reported [all 8 reports]

Readme for hsfcsh-0.0.1

[back to package description]
It is just a wrapper around fcsh. It allows to build flash/flex projects incrementally.
It can be used from Makefile.

The package contains two executables, hsfcsh and hsfcsh_do. The first one is daemon,
hsfcsh_do allows to send commands to the daemon.


- Install flex sdk and add <flex_sdk>/bin to your PATH
- Install haskell platform, add ~/.cabal/bin to your PATH
- `cabal install hsfcsh`


Use `hsfcsh_do spawn` or `hsfcsh_do exit` to start or stop the daemon.
Use `hsfcsh_do compile args` to compile something. It will spawn the daemon if it is not started yet.

The next example will compile Start.mxml from the current directory:
  hsfcsh_do compile -- "$(PWD)/Start.mxml"

The first time it may take few minutes to compile for large projects, but then it will compile
the project incrementally.

You can use hsfcsh_do from Makefile. See example in the corresponding directory.
It will redirect compiler output to the stdout, so you could examine the results (errors, warnings, etc)
or let your editor (vim, emacs) to parse them.