On Thu, Feb 11, 2010 at 4:28 AM, Limestraël limestr...@gmail.com wrote:
Eventually, I think using cabal during development may be convenient. The
only drawback is that you have to specify each dependency and -- above all
-- every module each time you add one.
Nevertheless, I'm not convinced
* On Tue, Feb 09 2010, Johan Tibell wrote:
On Tue, Feb 9, 2010 at 6:10 AM, Ketil Malde ke...@malde.org wrote:
Limestraël limestr...@gmail.com writes:
how do usually Haskell developpers build their softwares (and
especially medium or big libraries) while they are still
Eventually, I think using cabal during development may be convenient. The
only drawback is that you have to specify each dependency and -- above all
-- every module each time you add one.
Nevertheless, I'm not convinced regarding the use of Makefiles with Cabal. I
happen to think it's a bit
On Thu, Feb 11, 2010 at 5:28 AM, Limestraël limestr...@gmail.com wrote:
Eventually, I think using cabal during development may be convenient. The
only drawback is that you have to specify each dependency...
I actually think this is a benefit, not a drawback. In one of my
projects where I used
Don't you simply need to do what the error message says, and add (*in
the Executable section*, at the end of the file):
build-depends: SFML
?
Limestraël wrote:
I think I must be dumb or something.
I did my SFML.cabal exactly the way the packager of vty-ui did vty-ui.cabal,
and I still have
Neil Brown-7 wrote:
Don't you simply need to do what the error message says, and add (*in
the Executable section*, at the end of the file):
Nope, just check my previous message (my issue (2)):
Limestrael wrote:
(2) well, then, when building, if I don't specify that my executable
Am Mittwoch 10 Februar 2010 18:16:42 schrieb Limestraël:
Neil Brown-7 wrote:
Don't you simply need to do what the error message says, and add (*in
the Executable section*, at the end of the file):
Nope, just check my previous message (my issue (2)):
I think
On Tue, Feb 9, 2010 at 8:48 AM, Limestraël limestr...@gmail.com wrote:
Cabal/cabal-install are good tools for distribution and installation, but I
was wondering -- as I was starting to learn how to use Cabal -- how do
usually Haskell developpers build their softwares
I add the enclosed
Cabal/cabal-install are good tools for distribution and installation, but I
was wondering -- as I was starting to learn how to use Cabal -- how do
usually Haskell developpers build their softwares (and especially medium or
big libraries) while they are still developping them ?
With cabal-install,
With cabal-install, usually.
Limestraël wrote:
Cabal/cabal-install are good tools for distribution and installation,
but I was wondering -- as I was starting to learn how to use Cabal --
how do usually Haskell developpers build their softwares (and especially
medium or big libraries) while
(This is a same message, but with newlines. Sorry for the double post)
Cabal/cabal-install are good tools for distribution and installation, but I
was wondering -- as I was starting to learn how to use Cabal -- how do
usually Haskell developpers build their softwares (and especially medium or
Limestraël limestr...@gmail.com writes:
how do usually Haskell developpers build their softwares (and
especially medium or big libraries) while they are still developping them ?
With cabal-install, by doing one 'cabal configure' once and 'cabal build'
each time they have altered their code ?
Okay, so then I have so troubles regarding the compilation of my executable:
First, what do you think is the simpler : (1) build only the library through
cabal-install and then the executable with ghc (it isn't to be distributed
with the lib), or (2) add both to my
Okay, I juste solved issue (1) :
The package compiled through Cabal has its information stored in the
dist/package.conf.inplace file.
I can then compile my main by doing :
ghc --make -package-conf dist/package.conf.inplace main.hs
I just don't know if it's really the way I'm supposed to do this.
On Tue, Feb 9, 2010 at 6:10 AM, Ketil Malde ke...@malde.org wrote:
Limestraël limestr...@gmail.com writes:
how do usually Haskell developpers build their softwares (and
especially medium or big libraries) while they are still developping them
?
With cabal-install, by doing one 'cabal
My development environment is a Screen with Bash, Vim and GHCi
running.
If I can just load the files in GHCi or compile them with GHC
without specifying many options or extensions, then I just do
it that way. As soon as I feel a need to write a Makefile or a
little build script, I
Okay, but have you ever felt the need to make in the same project a library
and an executable which depends on this library (even just like me, for
testing purpose)? How would you do it?
Jason Dusek wrote:
My development environment is a Screen with Bash, Vim and GHCi
running.
If I
Cabal/cabal-install are good tools for distribution and
installation, but I was wondering -- as I was starting to learn how
to use Cabal -- how do usually Haskell developpers build their
softwares (and especially medium or big libraries) while they are
still developping them ?
The first
Okay, but have you ever felt the need to make in the same project a library
and an executable which depends on this library (even just like me, for
testing purpose)? How would you do it?
Specifying the modules under test in other-modules section for the executable
does the trick for me. I can
Then how does the 'Executable' section of your .cabal look like? That's what
I can't get working.
Jonathan Daugherty-4 wrote:
The first thing I always do is create a skeletal cabal file for my
project and add Library and Executable sections to it. The executable
might be a test/demo
Then how does the 'Executable' section of your .cabal look like? That's what
I can't get working.
Suitably elided.
Executable test
hs-source-dirs: src, tests
other-modules:Text.Yaml.Yay, Text.Yaml.Yay.Syck
main-is: Main.hs
build-depends:base, HsSyck,
Then how does the 'Executable' section of your .cabal look like?
That's what I can't get working.
Executable vty-ui-demo
Hs-Source-Dirs: src
Main-is: Demo.hs
Build-Depends:
mtl = 1.1 1.2
The Main-is refers to src/Demo.hs. This example is from:
Executable test
hs-source-dirs: src, tests
other-modules:Text.Yaml.Yay, Text.Yaml.Yay.Syck
...
In general, it's not advisable to name your test executable test due
to a naming collision with the typical test utility. You might
consider naming it $package_name-test. (This
I think I must be dumb or something.
I did my SFML.cabal exactly the way the packager of vty-ui did vty-ui.cabal,
and I still have got the error when building:
hs_src/SFML/Direct/Graphics.hs:51:7:
Could not find module `SFML.Direct.Types.Enums':
It is a member of the hidden package
24 matches
Mail list logo
