Problem with the object file name of the Main module.

[Erik Hesselink]

I'd like to repeat the suggestion to use cabal. It's very well suited
for simple programs. In addition, you get the ability to specify
dependencies, you can upload to hackage, etc.

Erik

On Mon, Jan 13, 2014 at 11:10 PM, Christian Brolin <cbrolin at gmail.com> wrote:
> Thanks, but it is not a complicated build process. Just a few simple
> programs that share some modules. I like to keep it simple.
>
>
> On 2014-01-13 19:28, Carter Schonwald wrote:
>
> i warmly recommend you use cabal for any complicated build processes. if
> you're stuck, holler and we or haskell-cafe are happy to help
>
>
> On Mon, Jan 13, 2014 at 1:22 PM, Christian Brolin <cbrolin at gmail.com> wrote:
>>
>> No. As a workaround I remove the Main.o file after the executable has been
>> linked. It works, but it has its drawbacks.
>>
>>
>> On 2014-01-12 17:23, Carter Schonwald wrote:
>>
>> Christian, have you tried using cabal? People write cabal files with
>> multiple executables being generated all the time.
>>
>> On Sunday, January 12, 2014, Christian Brolin wrote:
>>>
>>> H.
>>>
>>> The documentation (version 7.6.3) section 7.7.2 Output files says that
>>> the source file name of the Main module does not have to be Main.hs making
>>> it "possible to have several Main modules in separate source files in the
>>> same directory". While this is true and promising it is seems to be unusable
>>> since GHC always compiles the main source file into an object file called
>>> Main.o.
>>>
>>> _______________________________________________
>>> Glasgow-haskell-users mailing list
>>> Glasgow-haskell-users at haskell.org
>>> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
>>
>>
>
>
>
> _______________________________________________
> Glasgow-haskell-users mailing list
> Glasgow-haskell-users at haskell.org
> http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
>