BTW there is no "Test" directory and also no "CLI" directory .... I am pretty familiar with cabal but not as much with "Unix" Makefile. Probably I need to restructure source directory tree ... to have "library" source in one subtree, tests in another CLI executables in a third BUT can I set up cabal files to do recursive directory "visits" like Makefiles?<br>
<br>Vasili<br><br><div class="gmail_quote">On Wed, Jun 3, 2009 at 11:58 PM, Vasili I. Galchin <span dir="ltr"><<a href="mailto:vigalchin@gmail.com">vigalchin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br> I have cabalizing some "legacy" Haskell source. By "legacy", I totally don't mean in a pejorative sense ... code has been designed and written well. I am making good progress ... I have succeeded in building an archive file(library) on a POSIX platform, i.e. Linux. The original author intended to build several executables from this .a file. In addition there are many pairings of .hs/.lhs along with "main" test files. Currently I have only one .cabal file. This is inadequate for the author's intent:<br>
<br>1) I need to build "n" test executables.<br><br>2) I need to build 1/2 CLI executables.<br><br>I need advice on the cabal front. E.g. should I first run the library .cabal and then run several subsidary .cabal files, e.g. "n"test .cabals and also 1/2 CLI executable .cabals??? I am looking for advice so that I don't have a clumsy cabal build process/tree!<br>
<br>Thanks, Vasili<br>
</blockquote></div><br>