mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

work around for windows watcher cabal build problem

Browse source
This commit is contained in:
Joey Hess 2013-11-12 21:23:20 -04:00
parent 3e9419b088
commit f30300e877
1 changed files with 9 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
doc/todo/windows_support.mdwn
View file

@ -9,10 +9,15 @@ now! --[[Joey]]
* rsync special remotes are known buggy. * rsync special remotes are known buggy.
* Bad file locking, it's probably not safe to run more than one git-annex * Bad file locking, it's probably not safe to run more than one git-annex
process at the same time on Windows. process at the same time on Windows.
* `git annex watch` builds, but it has not been tested at all.
* `git annex assistant` builds, but has not been tested, and is known
to not download any files. (transferrer doesn't built yet)
* Webapp doesn't build yet.
* Ssh connection caching does not work on Windows, so `git annex get` * Ssh connection caching does not work on Windows, so `git annex get`
has to connect twice to the remote system over ssh per file, which has to connect twice to the remote system over ssh per file, which
is much slower than on systems supporting connection caching. is much slower than on systems supporting connection caching.
* Webapp doesn't build yet.
* `git annex watch` builds, but does not quite work.
* `git annex assistant` builds, but has not been tested, and is known
to not download any files. (transferrer doesn't built yet)
* watch and assistant cannot be built with cabal. Possibly due to too many
files overflowing command line length limit at link stage.
To build a binary with them:
`ghc --make git-annex.hs -threaded -XPackageImports -DWITH_ASSISTANT=1 -DWITH_WIN32NOTIFY=1`
(should add all the other flags cabal uses)