[Haskell-cafe] cabal sdist and auto-generated modules
6 views
Skip to first unread message
Marios Titas
Aug 31, 2014, 12:45:39 AM8/31/14
to haskell-cafe
I am trying to run cabal sdist on a package where one of exposed
modules does not exists because it is automatically generated by
setup.hs. cabal refuses to do that because it cannot find the file
corresponding to that module. Is there a solution to that problem? The
package builds just fine.
_______________________________________________
Haskell-Cafe mailing list
Haskel...@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
modules does not exists because it is automatically generated by
setup.hs. cabal refuses to do that because it cannot find the file
corresponding to that module. Is there a solution to that problem? The
package builds just fine.
_______________________________________________
Haskell-Cafe mailing list
Haskel...@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Mateusz Kowalczyk
Aug 31, 2014, 9:58:06 AM8/31/14
to haskel...@haskell.org
--
Mateusz K.
Brandon Allbery
Aug 31, 2014, 10:11:54 AM8/31/14
to Mateusz Kowalczyk, haskell-cafe
On Sun, Aug 31, 2014 at 9:57 AM, Mateusz Kowalczyk <fuuz...@fuuzetsu.co.uk> wrote:
On 08/31/2014 05:45 AM, Marios Titas wrote:
> I am trying to run cabal sdist on a package where one of exposed
> modules does not exists because it is automatically generated by
> setup.hs. cabal refuses to do that because it cannot find the file
> corresponding to that module. Is there a solution to that problem? The
> package builds just fine.
Does touch missingmodule.hs not do it for you?
brandon s allbery kf8nh sine nomine associates
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Mateusz Kowalczyk
Aug 31, 2014, 10:13:36 AM8/31/14
to Brandon Allbery, haskell-cafe
On 08/31/2014 03:11 PM, Brandon Allbery wrote:
> On Sun, Aug 31, 2014 at 9:57 AM, Mateusz Kowalczyk <fuuz...@fuuzetsu.co.uk>
> wrote:
>
>> On 08/31/2014 05:45 AM, Marios Titas wrote:
>>> I am trying to run cabal sdist on a package where one of exposed
>>> modules does not exists because it is automatically generated by
>>> setup.hs. cabal refuses to do that because it cannot find the file
>>> corresponding to that module. Is there a solution to that problem? The
>>> package builds just fine.
>>
>> Does touch missingmodule.hs not do it for you?
>>
>
> Sounds like a bad idea, it would mean instead of generating the module it
> would take the empty file as the generated module and probably fail to
> build?
>
> On Sun, Aug 31, 2014 at 9:57 AM, Mateusz Kowalczyk <fuuz...@fuuzetsu.co.uk>
> wrote:
>
>> On 08/31/2014 05:45 AM, Marios Titas wrote:
>>> I am trying to run cabal sdist on a package where one of exposed
>>> modules does not exists because it is automatically generated by
>>> setup.hs. cabal refuses to do that because it cannot find the file
>>> corresponding to that module. Is there a solution to that problem? The
>>> package builds just fine.
>>
>> Does touch missingmodule.hs not do it for you?
>>
>
> Sounds like a bad idea, it would mean instead of generating the module it
> would take the empty file as the generated module and probably fail to
> build?
>
Presumably setup.hs would take care to delete the ‘fake’ file with the
actual generated file at build time.
Marios Titas
Aug 31, 2014, 10:17:16 AM8/31/14
to Mateusz Kowalczyk, haskell-cafe
Yes, including an empty (or dummy) file causes cabal build to fail
because it apparently prefers that file over the generated one in the
autogen directory.
because it apparently prefers that file over the generated one in the
autogen directory.
On Sun, Aug 31, 2014 at 3:13 PM, Mateusz Kowalczyk
Marios Titas
Aug 31, 2014, 12:28:27 PM8/31/14
to Mateusz Kowalczyk, haskell-cafe
Also, isn't this a bad practice? I think setup.hs should not modify
the source tree in any way, it should only create/modify files in the
dist/ directory.
the source tree in any way, it should only create/modify files in the
dist/ directory.
Reply all
Reply to author
Forward
0 new messages