2014-08-24 08:45:29 +0200 <lispy> augur: something that has a .cabal file
2014-08-24 08:36:11 +0200 <lispy> augur: it matters for your .cabal file. If ghc is to build the .c file then you use c-sources but if you alread have the library then you use extra-libs
2014-08-24 08:34:11 +0200 <augur> lispy: i thiiink i just have to tell cabal to about the .h file, right?
2014-08-24 08:20:17 +0200 <lispy> augur: by the way, I often come back to this page as a reference: http://www.haskell.org/cabal/users-guide/developing-packages.html
2014-08-24 08:19:50 +0200 <avocado> i have a package that depends on Tensor- but cabal can't build it. am i ... missing something?
2014-08-24 08:19:23 +0200 <lispy> augur: that will be more involved. You'll need to tell cabal where the C sources (or compiled library) can be found. You'll need to know how to use the FFI.
2014-08-24 08:18:16 +0200 <lispy> I like to use sandboxes so I typically do; cabal sandbox; cabal install
2014-08-24 08:18:13 +0200 <dmj`> augur: for exectuables don't use cabal install, all you need is cabal build. cabal install puts them in your sandbox directory, cabal build puts them in the dist folder, cabal clean removes the dist folder
2014-08-24 08:17:24 +0200 <lispy> and cabal install is something like cabal configure; cabal build; cabal copy
2014-08-24 08:16:52 +0200 <augur> then i just do cabal build to compile the exposed module? or what?
2014-08-24 08:11:39 +0200 <lispy> augur: do you have some .hs files relative to this .cabal file? Perhaps src/Foo.hs?
2014-08-24 08:11:13 +0200 <lispy> augur: There is also a 'cabal check' command that you should use periodically
2014-08-24 08:10:55 +0200 <augur> lispy: that seems to make cabal configure happy
2014-08-24 08:09:10 +0200 <augur> lispy: i just did cabal init and followed the instructions
2014-08-24 08:08:30 +0200 <lispy> augur: So the first thing that stands out to me is that this .cabal file is for building an executable only. So we should change it so that it's for building a library.
2014-08-24 08:05:49 +0200 <lispy> augur: Do you have a link where I can look at your .cabal file?
2014-08-24 08:05:48 +0200 <joelteon> props, cabal
2014-08-24 08:05:44 +0200 <joelteon> no, wow, it's been there ever since cabal was first written
2014-08-24 08:05:06 +0200 <lispy> augur: ah, so 'main-is:' tells cabal what file has main :: IO (), and that is needed for executables
2014-08-24 08:04:35 +0200 <augur> > cabal: No 'main-is' field found for executable language-engine
2014-08-24 08:04:24 +0200 <lispy> augur: it will look at your build-depends mostly. It will also make sure the .cabal file parses and it will see if it can figure out how to build your library.
2014-08-24 08:03:25 +0200 <lispy> augur: You might do that to test your .cabal file.
2014-08-24 08:03:19 +0200 <joelteon> has cabal always had the --with-compiler flag, or was that a recent addition?
2014-08-24 08:03:02 +0200 <lispy> augur: and if you type 'cabal configure' does it complain?
2014-08-24 08:02:43 +0200 <lispy> augur: So, you have a .cabal file, you have some .hs files?
2014-08-24 08:01:31 +0200 <augur> dmj`: cabal help isn't helpful.
2014-08-24 07:56:20 +0200 <dmj`> augur: run the command "cabal help"
2014-08-24 07:56:09 +0200 <dmj`> augur: look through cabal help, see if its intuitive, as stalintrotsky mentions having your modules named correctly (corresponding to folder names) is necessary
2014-08-24 07:54:29 +0200 <augur> dmj`: no, all i've done is cabal init. like i said, i dont know cabal, so i dont know what im doing
2014-08-24 07:54:02 +0200 <dmj`> augur: ok, did you run cabal build?
2014-08-24 07:52:41 +0200 <dmj`> augur: in your cabal file there is might be a "Build-depends" section, do you have any packages defined there?
2014-08-24 07:51:25 +0200 <dmj`> augur: have you installed the dependencies you've defined your cabal file
2014-08-24 07:50:38 +0200 <augur> dmj`: yes i have a cabal file using cabal init
2014-08-24 07:50:09 +0200 <dmj`> augur: have you defined a cabal file?
2014-08-24 07:49:15 +0200 <augur> dmj`: im not cabal installing