DLL on Windows

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

DLL on Windows

Serguey Zefirov
I tried the way described in
http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
and i got this error message:

--------------------------------------------------------------------------------------------
ghc -shared -o test.dll --make test.hs
[1 of 1] Compiling Test             ( test.hs, test.o )
ghc.exe: panic! (the 'impossible' happened)
  (GHC version 6.10.3 for i386-unknown-mingw32):
        link: GHC not built to link this way: LinkDynLib

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
--------------------------------------------------------------------------------------------
How can I fix it?
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: DLL on Windows

Neil Mitchell
Hi Serguey,

I notice you are using GHC 6.10.3, I suggest you try 6.10.4 which I
know does work.

I rewrote that section of the manual recently. I haven't had time to
merge it back in, but it might give you more help:

http://neilmitchell.blogspot.com/2009/11/haskell-dlls-on-windows.html

Thanks, Neil

On Tue, Feb 16, 2010 at 2:33 PM, Serguey Zefirov <[hidden email]> wrote:

> I tried the way described in
> http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
> and i got this error message:
>
> --------------------------------------------------------------------------------------------
> ghc -shared -o test.dll --make test.hs
> [1 of 1] Compiling Test             ( test.hs, test.o )
> ghc.exe: panic! (the 'impossible' happened)
>  (GHC version 6.10.3 for i386-unknown-mingw32):
>        link: GHC not built to link this way: LinkDynLib
>
> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
> --------------------------------------------------------------------------------------------
> How can I fix it?
> _______________________________________________
> Haskell-Cafe mailing list
> [hidden email]
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: DLL on Windows

Serguey Zefirov
I'd like to, but I cannot. My code is tied to gtk2hs, which supports
either 6.10.1 or 6.10.3.

I put it another way: could I build DLL using ghc 6.12.*?

If I can, I'll use 6.10.3 for gtk2hs code and 6.12 for all new stuff.

2010/2/16 Neil Mitchell <[hidden email]>:

> Hi Serguey,
>
> I notice you are using GHC 6.10.3, I suggest you try 6.10.4 which I
> know does work.
>
> I rewrote that section of the manual recently. I haven't had time to
> merge it back in, but it might give you more help:
>
> http://neilmitchell.blogspot.com/2009/11/haskell-dlls-on-windows.html
>
> Thanks, Neil
>
> On Tue, Feb 16, 2010 at 2:33 PM, Serguey Zefirov <[hidden email]> wrote:
>> I tried the way described in
>> http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
>> and i got this error message:
>>
>> --------------------------------------------------------------------------------------------
>> ghc -shared -o test.dll --make test.hs
>> [1 of 1] Compiling Test             ( test.hs, test.o )
>> ghc.exe: panic! (the 'impossible' happened)
>>  (GHC version 6.10.3 for i386-unknown-mingw32):
>>        link: GHC not built to link this way: LinkDynLib
>>
>> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
>> --------------------------------------------------------------------------------------------
>> How can I fix it?
>> _______________________________________________
>> Haskell-Cafe mailing list
>> [hidden email]
>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: DLL on Windows

Neil Mitchell
Hi Serguey,

A GHC 6.10.4 version of Gtk2hs:

http://www.mail-archive.com/gtk2hs-devel@.../msg00340.html

I used to recommend Gtk2hs over wxHaskell for GUI development as there
was always a version that worked on Windows with the latest GHC
release. I think I might have to switch back to recommending C# for
GUI development...

Thanks, Neil

On Tue, Feb 16, 2010 at 5:19 PM, Serguey Zefirov <[hidden email]> wrote:

> I'd like to, but I cannot. My code is tied to gtk2hs, which supports
> either 6.10.1 or 6.10.3.
>
> I put it another way: could I build DLL using ghc 6.12.*?
>
> If I can, I'll use 6.10.3 for gtk2hs code and 6.12 for all new stuff.
>
> 2010/2/16 Neil Mitchell <[hidden email]>:
>> Hi Serguey,
>>
>> I notice you are using GHC 6.10.3, I suggest you try 6.10.4 which I
>> know does work.
>>
>> I rewrote that section of the manual recently. I haven't had time to
>> merge it back in, but it might give you more help:
>>
>> http://neilmitchell.blogspot.com/2009/11/haskell-dlls-on-windows.html
>>
>> Thanks, Neil
>>
>> On Tue, Feb 16, 2010 at 2:33 PM, Serguey Zefirov <[hidden email]> wrote:
>>> I tried the way described in
>>> http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
>>> and i got this error message:
>>>
>>> --------------------------------------------------------------------------------------------
>>> ghc -shared -o test.dll --make test.hs
>>> [1 of 1] Compiling Test             ( test.hs, test.o )
>>> ghc.exe: panic! (the 'impossible' happened)
>>>  (GHC version 6.10.3 for i386-unknown-mingw32):
>>>        link: GHC not built to link this way: LinkDynLib
>>>
>>> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
>>> --------------------------------------------------------------------------------------------
>>> How can I fix it?
>>> _______________________________________________
>>> Haskell-Cafe mailing list
>>> [hidden email]
>>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>>
>>
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: DLL on Windows

Serguey Zefirov
Thank you very much.

How do you use C# for GUI development? Do you use hs-dotnet?

2010/2/16 Neil Mitchell <[hidden email]>:

> Hi Serguey,
>
> A GHC 6.10.4 version of Gtk2hs:
>
> http://www.mail-archive.com/gtk2hs-devel@.../msg00340.html
>
> I used to recommend Gtk2hs over wxHaskell for GUI development as there
> was always a version that worked on Windows with the latest GHC
> release. I think I might have to switch back to recommending C# for
> GUI development...
>
> Thanks, Neil
>
> On Tue, Feb 16, 2010 at 5:19 PM, Serguey Zefirov <[hidden email]> wrote:
>> I'd like to, but I cannot. My code is tied to gtk2hs, which supports
>> either 6.10.1 or 6.10.3.
>>
>> I put it another way: could I build DLL using ghc 6.12.*?
>>
>> If I can, I'll use 6.10.3 for gtk2hs code and 6.12 for all new stuff.
>>
>> 2010/2/16 Neil Mitchell <[hidden email]>:
>>> Hi Serguey,
>>>
>>> I notice you are using GHC 6.10.3, I suggest you try 6.10.4 which I
>>> know does work.
>>>
>>> I rewrote that section of the manual recently. I haven't had time to
>>> merge it back in, but it might give you more help:
>>>
>>> http://neilmitchell.blogspot.com/2009/11/haskell-dlls-on-windows.html
>>>
>>> Thanks, Neil
>>>
>>> On Tue, Feb 16, 2010 at 2:33 PM, Serguey Zefirov <[hidden email]> wrote:
>>>> I tried the way described in
>>>> http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
>>>> and i got this error message:
>>>>
>>>> --------------------------------------------------------------------------------------------
>>>> ghc -shared -o test.dll --make test.hs
>>>> [1 of 1] Compiling Test             ( test.hs, test.o )
>>>> ghc.exe: panic! (the 'impossible' happened)
>>>>  (GHC version 6.10.3 for i386-unknown-mingw32):
>>>>        link: GHC not built to link this way: LinkDynLib
>>>>
>>>> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
>>>> --------------------------------------------------------------------------------------------
>>>> How can I fix it?
>>>> _______________________________________________
>>>> Haskell-Cafe mailing list
>>>> [hidden email]
>>>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>>>
>>>
>>
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: DLL on Windows

Neil Mitchell
Oh no, I just give up on Haskell and use C# entirely - I'd much rather
program in Haskell, but if all you are doing is a simple Windows app
then a nice GUI is easy in C# with the form designer.

Thanks, Neil

On Tue, Feb 16, 2010 at 6:01 PM, Serguey Zefirov <[hidden email]> wrote:

> Thank you very much.
>
> How do you use C# for GUI development? Do you use hs-dotnet?
>
> 2010/2/16 Neil Mitchell <[hidden email]>:
>> Hi Serguey,
>>
>> A GHC 6.10.4 version of Gtk2hs:
>>
>> http://www.mail-archive.com/gtk2hs-devel@.../msg00340.html
>>
>> I used to recommend Gtk2hs over wxHaskell for GUI development as there
>> was always a version that worked on Windows with the latest GHC
>> release. I think I might have to switch back to recommending C# for
>> GUI development...
>>
>> Thanks, Neil
>>
>> On Tue, Feb 16, 2010 at 5:19 PM, Serguey Zefirov <[hidden email]> wrote:
>>> I'd like to, but I cannot. My code is tied to gtk2hs, which supports
>>> either 6.10.1 or 6.10.3.
>>>
>>> I put it another way: could I build DLL using ghc 6.12.*?
>>>
>>> If I can, I'll use 6.10.3 for gtk2hs code and 6.12 for all new stuff.
>>>
>>> 2010/2/16 Neil Mitchell <[hidden email]>:
>>>> Hi Serguey,
>>>>
>>>> I notice you are using GHC 6.10.3, I suggest you try 6.10.4 which I
>>>> know does work.
>>>>
>>>> I rewrote that section of the manual recently. I haven't had time to
>>>> merge it back in, but it might give you more help:
>>>>
>>>> http://neilmitchell.blogspot.com/2009/11/haskell-dlls-on-windows.html
>>>>
>>>> Thanks, Neil
>>>>
>>>> On Tue, Feb 16, 2010 at 2:33 PM, Serguey Zefirov <[hidden email]> wrote:
>>>>> I tried the way described in
>>>>> http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html
>>>>> and i got this error message:
>>>>>
>>>>> --------------------------------------------------------------------------------------------
>>>>> ghc -shared -o test.dll --make test.hs
>>>>> [1 of 1] Compiling Test             ( test.hs, test.o )
>>>>> ghc.exe: panic! (the 'impossible' happened)
>>>>>  (GHC version 6.10.3 for i386-unknown-mingw32):
>>>>>        link: GHC not built to link this way: LinkDynLib
>>>>>
>>>>> Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug
>>>>> --------------------------------------------------------------------------------------------
>>>>> How can I fix it?
>>>>> _______________________________________________
>>>>> Haskell-Cafe mailing list
>>>>> [hidden email]
>>>>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>>>>
>>>>
>>>
>>
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

GUI (was: Re: DLL on Windows)

Henk-Jan van Tuyl
In reply to this post by Neil Mitchell
On Tue, 16 Feb 2010 18:57:20 +0100, Neil Mitchell <[hidden email]>  
wrote:

> I used to recommend Gtk2hs over wxHaskell for GUI development as there
> was always a version that worked on Windows with the latest GHC
> release. I think I might have to switch back to recommending C# for
> GUI development...

The latest revision of wxHaskell can be compiled relatively easy, so that  
wxHaskell can be used immediately for the latest version of GHC.

Regards,
Henk-Jan

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Thomas DuBuisson
On Tue, Feb 16, 2010 at 3:48 PM, Henk-Jan van Tuyl <[hidden email]> wrote:

> On Tue, 16 Feb 2010 18:57:20 +0100, Neil Mitchell <[hidden email]>
> wrote:
>
>> I used to recommend Gtk2hs over wxHaskell for GUI development as there
>> was always a version that worked on Windows with the latest GHC
>> release. I think I might have to switch back to recommending C# for
>> GUI development...
>
> The latest revision of wxHaskell can be compiled relatively easy, so that
> wxHaskell can be used immediately for the latest version of GHC.

Exciting allegation, but it doesn't quite check out with GHC 6.12.1 +
cabal 1.8.0.2 and cabal-install 0.8 (see below).  I would expect this
issue to be easily resolved by specifying "containers <= 0.3.*" in the
"wxdirect" package, but cabal is misbehaving (for me) and stating
wxdirect needs reinstalled with a supposedly newer version of
containers, 0.2.0.1.

Thomas

[tommd@Mavlo ~]$ cabal install wx
Resolving dependencies...
Downloading containers-0.2.0.1...
Configuring containers-0.2.0.1...
Preprocessing library containers-0.2.0.1...
Building containers-0.2.0.1...

Data/IntMap.hs:182:7:
    Could not find module `Data.Data':
      It is a member of the hidden package `base'.
      Perhaps you need to add `base' to the build-depends in your .cabal file.
      Use -v to see a list of the files searched for.
cabal: Error: some packages failed to install:
containers-0.2.0.1 failed during the building phase. The exception was:
ExitFailure 1
wx-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
wxcore-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
wxdirect-0.12.1.1 depends on containers-0.2.0.1 which failed to install.
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Jeremy O'Donoghue
You're probably correct about the dependencies. I have never tried to
compile wxHaskell against GHC 6.12.1

I'm waiting for Haskell Platform to be released to make the required
changes since (working primarily on Windows) I just don't have time to
create a complete GHC 6.12 installation with most of the HP libraries
(some of which are a pain to get working on Windows).

wxHaskell will support GHC 6.12.x within a couple of days of release of
a suitable Haskell Platform.

Regards
Jeremy

On Tue, 16 Feb 2010 17:55 -0800, "Thomas DuBuisson"
<[hidden email]> wrote:

> On Tue, Feb 16, 2010 at 3:48 PM, Henk-Jan van Tuyl <[hidden email]>
> wrote:
> > On Tue, 16 Feb 2010 18:57:20 +0100, Neil Mitchell <[hidden email]>
> > wrote:
> >
> >> I used to recommend Gtk2hs over wxHaskell for GUI development as there
> >> was always a version that worked on Windows with the latest GHC
> >> release. I think I might have to switch back to recommending C# for
> >> GUI development...
> >
> > The latest revision of wxHaskell can be compiled relatively easy, so that
> > wxHaskell can be used immediately for the latest version of GHC.
>
> Exciting allegation, but it doesn't quite check out with GHC 6.12.1 +
> cabal 1.8.0.2 and cabal-install 0.8 (see below).  I would expect this
> issue to be easily resolved by specifying "containers <= 0.3.*" in the
> "wxdirect" package, but cabal is misbehaving (for me) and stating
> wxdirect needs reinstalled with a supposedly newer version of
> containers, 0.2.0.1.
>
> Thomas
>
> [tommd@Mavlo ~]$ cabal install wx
> Resolving dependencies...
> Downloading containers-0.2.0.1...
> Configuring containers-0.2.0.1...
> Preprocessing library containers-0.2.0.1...
> Building containers-0.2.0.1...
>
> Data/IntMap.hs:182:7:
>     Could not find module `Data.Data':
>       It is a member of the hidden package `base'.
>       Perhaps you need to add `base' to the build-depends in your .cabal
>       file.
>       Use -v to see a list of the files searched for.
> cabal: Error: some packages failed to install:
> containers-0.2.0.1 failed during the building phase. The exception was:
> ExitFailure 1
> wx-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
> wxcore-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
> wxdirect-0.12.1.1 depends on containers-0.2.0.1 which failed to install.
> _______________________________________________
> Haskell-Cafe mailing list
> [hidden email]
> http://www.haskell.org/mailman/listinfo/haskell-cafe
--
  Jeremy O'Donoghue
  [hidden email]

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Thomas DuBuisson
On Wed, Feb 17, 2010 at 3:17 AM, Jeremy O'Donoghue
<[hidden email]> wrote:
> You're probably correct about the dependencies. I have never tried to
> compile wxHaskell against GHC 6.12.1
>
> I'm waiting for Haskell Platform to be released to make the required
> changes since (working primarily on Windows) I just don't have time to
> create a complete GHC 6.12 installation with most of the HP libraries
> (some of which are a pain to get working on Windows).

FYI, it also seems the current version of wxcore assumes something
that isn't true about Cabal (again, I use Cabal 1.8.0.2).  I just
tested with ghc-6.10.4 + Cabal 1.8.0.2 + cabal-install 0.8.0 and
received what is probably a well known complaint:

[tommd@Mavlo ~]$ cabal install wx
Resolving dependencies...
[1 of 1] Compiling Main             (
/tmp/wxcore-0.12.1.23133/wxcore-0.12.1.2/Setup.hs,
/tmp/wxcore-0.12.1.23133/wxcore-0.12.1.2/dist/setup/Main.o )

/tmp/wxcore-0.12.1.23133/wxcore-0.12.1.2/Setup.hs:15:57:
    Couldn't match expected type `GenericPackageDescription'
           against inferred type `Either
                                    GenericPackageDescription
PackageDescription'
      Expected type: (GenericPackageDescription, HookedBuildInfo)
      Inferred type: (Either
                        GenericPackageDescription PackageDescription,
                      HookedBuildInfo)
    In the `confHook' field of a record
    In the first argument of `defaultMainWithHooks', namely
        `simpleUserHooks {confHook = myConfHook}'

/tmp/wxcore-0.12.1.23133/wxcore-0.12.1.2/Setup.hs:51:37:
    Couldn't match expected type `GenericPackageDescription'
           against inferred type `Either
                                    GenericPackageDescription
PackageDescription'
    In the expression: pkg0
    In the second argument of `confHook', namely `(pkg0, pbi)'
    In a stmt of a 'do' expression:
        lbi <- confHook simpleUserHooks (pkg0, pbi) flags
cabal: Error: some packages failed to install:
wx-0.12.1.2 depends on wxcore-0.12.1.2 which failed to install.
wxcore-0.12.1.2 failed during the configure step. The exception was:
ExitFailure 1
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Daniel Fischer-4
In reply to this post by Jeremy O'Donoghue
Am Mittwoch 17 Februar 2010 12:17:10 schrieb Jeremy O'Donoghue:

> You're probably correct about the dependencies. I have never tried to
> compile wxHaskell against GHC 6.12.1
>
> I'm waiting for Haskell Platform to be released to make the required
> changes since (working primarily on Windows) I just don't have time to
> create a complete GHC 6.12 installation with most of the HP libraries
> (some of which are a pain to get working on Windows).
>
> wxHaskell will support GHC 6.12.x within a couple of days of release of
> a suitable Haskell Platform.
>
> Regards
> Jeremy

Beating a dead horse, but today I decided to see whether I could install
wxHaskell, all it took was a few edits in some .cabal files and one in
wxcore's Setup to make it all build with 6.12.1.
Still, it's annoying because you have to unpack everything, edit and cabal
install in the unpacked directories.

Now since I did that, I could upload new verxions of wxdirect, wxcore and
wx to hackage, so others could do a simple cabal install wx.

But I would only do that if I get a go-ahead from somebody authorised
(since Jeremy uploaded the previous versions, he'd be qualified, I think).

Or I could send the edits to Jeremy and let him do the uploading, whatever
is preferred.

>
> On Tue, 16 Feb 2010 17:55 -0800, "Thomas DuBuisson"
>
> <[hidden email]> wrote:
> > On Tue, Feb 16, 2010 at 3:48 PM, Henk-Jan van Tuyl <[hidden email]>
> >
> > wrote:
> > > On Tue, 16 Feb 2010 18:57:20 +0100, Neil Mitchell
> > > <[hidden email]>
> > >
> > > wrote:
> > >> I used to recommend Gtk2hs over wxHaskell for GUI development as
> > >> there was always a version that worked on Windows with the latest
> > >> GHC release. I think I might have to switch back to recommending C#
> > >> for GUI development...
> > >
> > > The latest revision of wxHaskell can be compiled relatively easy, so
> > > that wxHaskell can be used immediately for the latest version of
> > > GHC.
> >
> > Exciting allegation, but it doesn't quite check out with GHC 6.12.1 +
> > cabal 1.8.0.2 and cabal-install 0.8 (see below).  I would expect this
> > issue to be easily resolved by specifying "containers <= 0.3.*" in the
> > "wxdirect" package, but cabal is misbehaving (for me) and stating
> > wxdirect needs reinstalled with a supposedly newer version of
> > containers, 0.2.0.1.
> >
> > Thomas
> >
> > [tommd@Mavlo ~]$ cabal install wx
> > Resolving dependencies...
> > Downloading containers-0.2.0.1...
> > Configuring containers-0.2.0.1...
> > Preprocessing library containers-0.2.0.1...
> > Building containers-0.2.0.1...
> >
> > Data/IntMap.hs:182:7:
> >     Could not find module `Data.Data':
> >       It is a member of the hidden package `base'.
> >       Perhaps you need to add `base' to the build-depends in your
> > .cabal file.
> >       Use -v to see a list of the files searched for.
> > cabal: Error: some packages failed to install:
> > containers-0.2.0.1 failed during the building phase. The exception
> > was: ExitFailure 1
> > wx-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
> > wxcore-0.12.1.2 depends on containers-0.2.0.1 which failed to install.
> > wxdirect-0.12.1.1 depends on containers-0.2.0.1 which failed to
> > install.
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Jeremy O'Donoghue
Hi Daniel,

On Fri, 26 Feb 2010 15:31 +0100, "Daniel Fischer"
<[hidden email]> wrote:
> Am Mittwoch 17 Februar 2010 12:17:10 schrieb Jeremy O'Donoghue:
> > You're probably correct about the dependencies. I have never tried to
> > compile wxHaskell against GHC 6.12.1
[snip]
>
> Beating a dead horse, but today I decided to see whether I could install
> wxHaskell, all it took was a few edits in some .cabal files and one in
> wxcore's Setup to make it all build with 6.12.1.
> Still, it's annoying because you have to unpack everything, edit and
> cabal install in the unpacked directories.
>
> Now since I did that, I could upload new verxions of wxdirect, wxcore and
> wx to hackage, so others could do a simple cabal install wx.

Thanks for doing this: it's great news for everyone who is on GHC
6.12.x.

> But I would only do that if I get a go-ahead from somebody authorised
> (since Jeremy uploaded the previous versions, he'd be qualified, I
> think).

You're right - I'm probably as qualified as anyone! I've found that
if a Cabal build works for one person, it's pretty reliable for all
(this
is one of the joys of Cabal and (to a lesser extent) the Haskell
Platform.

I'm quite happy for you to upload updates to Cabal. I'll pull them next
week and make sure that they get merged to the wxHaskell darcs repo. If
there are any reports of issues with the uploaded version (which I
doubt)
I'll look into them, so you're not taking on any long-term support
burden.

> Or I could send the edits to Jeremy and let him do the uploading,
> whatever is preferred.

I have no strong preference - the only thing I want to be sure of is
that the
darcs repo stays closely in sync with whatever is in Cabal. If you are
OK with
doing the upload, that's great. Otherwise I'll be very happy to do it
based on
your patches.

Best regards
Jeremy
--
  Jeremy O'Donoghue
  [hidden email]

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Neil Mitchell
Hi,

I thought this thread suggested that a cabal install wx would now
work? I just tried it and got:

...
generated 2439 constant definitions
ok.
setup.exe: wx-config: does not exist
cabal: Error: some packages failed to install:
wx-0.12.1.4 depends on wxcore-0.12.1.4 which failed to install.
wxcore-0.12.1.4 failed during the configure step. The exception was:
ExitFailure 1

If wxHaskell could be installed with one cabal command that would be
incredibly cool :-)

Thanks, Neil

On Fri, Feb 26, 2010 at 6:26 PM, Jeremy O'Donoghue
<[hidden email]> wrote:

> Hi Daniel,
>
> On Fri, 26 Feb 2010 15:31 +0100, "Daniel Fischer"
> <[hidden email]> wrote:
>> Am Mittwoch 17 Februar 2010 12:17:10 schrieb Jeremy O'Donoghue:
>> > You're probably correct about the dependencies. I have never tried to
>> > compile wxHaskell against GHC 6.12.1
> [snip]
>>
>> Beating a dead horse, but today I decided to see whether I could install
>> wxHaskell, all it took was a few edits in some .cabal files and one in
>> wxcore's Setup to make it all build with 6.12.1.
>> Still, it's annoying because you have to unpack everything, edit and
>> cabal install in the unpacked directories.
>>
>> Now since I did that, I could upload new verxions of wxdirect, wxcore and
>> wx to hackage, so others could do a simple cabal install wx.
>
> Thanks for doing this: it's great news for everyone who is on GHC
> 6.12.x.
>
>> But I would only do that if I get a go-ahead from somebody authorised
>> (since Jeremy uploaded the previous versions, he'd be qualified, I
>> think).
>
> You're right - I'm probably as qualified as anyone! I've found that
> if a Cabal build works for one person, it's pretty reliable for all
> (this
> is one of the joys of Cabal and (to a lesser extent) the Haskell
> Platform.
>
> I'm quite happy for you to upload updates to Cabal. I'll pull them next
> week and make sure that they get merged to the wxHaskell darcs repo. If
> there are any reports of issues with the uploaded version (which I
> doubt)
> I'll look into them, so you're not taking on any long-term support
> burden.
>
>> Or I could send the edits to Jeremy and let him do the uploading,
>> whatever is preferred.
>
> I have no strong preference - the only thing I want to be sure of is
> that the
> darcs repo stays closely in sync with whatever is in Cabal. If you are
> OK with
> doing the upload, that's great. Otherwise I'll be very happy to do it
> based on
> your patches.
>
> Best regards
> Jeremy
> --
>  Jeremy O'Donoghue
>  [hidden email]
>
> _______________________________________________
> Haskell-Cafe mailing list
> [hidden email]
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Daniel Fischer-4
Am Sonntag 18 April 2010 20:59:25 schrieb Neil Mitchell:
> Hi,
>
> I thought this thread suggested that a cabal install wx would now
> work?

It does, as far as I can tell.

> I just tried it and got:
>
> ...
> generated 2439 constant definitions
> ok.
> setup.exe: wx-config: does not exist

That's not our fault, I think :)
You need wxWidgets-2.8.*.
wx-config should have been installed as part of the wxWidgets package. Is
that not included in the windows-installer of wxWidgets?

$ which wx-config
/usr/bin/wx-config
$ wx-config --help

 wx-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--release] [--version-
full]
           [--list] [--selected-config] [--host=HOST] [--toolkit=TOOLKIT]
           [--universal[=yes|no]] [--unicode[=yes|no]] [--debug[=yes|no]]
           [--static[=yes|no]] [--version[=VERSION]] [--basename] [--cc]
           [--cppflags] [--cflags] [--cxxflags] [--rescomp] [--libs] [--
cxx]
           [--ld] [--linkdeps] [--utility=UTIL] [LIB ...]

    wx-config returns information about the wxWidgets libraries available
on
  your system.  It may be used to retrieve the information required to
build
  applications using these libraries using --cppflags, --cflags,  --
cxxflags
  and --libs options.
<snip>

> cabal: Error: some packages failed to install:
> wx-0.12.1.4 depends on wxcore-0.12.1.4 which failed to install.
> wxcore-0.12.1.4 failed during the configure step. The exception was:
> ExitFailure 1
>
> If wxHaskell could be installed with one cabal command that would be
> incredibly cool :-)
>
> Thanks, Neil

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Daniel Fischer-4
Am Sonntag 18 April 2010 21:41:06 schrieb Daniel Fischer:
> wx-config should have been installed as part of the wxWidgets package.
> Is that not included in the windows-installer of wxWidgets?

Seems it's not so.
http://www.haskell.org/haskellwiki/WxHaskell/Building says
"Windows users should also get the Windows port of wx-config."
( http://sites.google.com/site/wxconfig/ )
Furthermore,
http://www.haskell.org/haskellwiki/WxHaskell/Building#On_Windows
says you can't use just any old compiler to build wxWidgets on windows, but
have to use the MinGW compiler.


> > If wxHaskell could be installed with one cabal command that would be
> > incredibly cool :-)

Well, it's just one cabal command if you have all non-Haskell requirements
installed as needed.

> >
> > Thanks, Neil

_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Ivan Lazar Miljenovic
On 19 April 2010 06:06, Daniel Fischer <[hidden email]> wrote:
>> > If wxHaskell could be installed with one cabal command that would be
>> > incredibly cool :-)
>
> Well, it's just one cabal command if you have all non-Haskell requirements
> installed as needed.

Exactly; it's unreasonable to suggest/assume that cabal-install can
deal with non-Haskell dependencies and toolchains for you.

--
Ivan Lazar Miljenovic
[hidden email]
IvanMiljenovic.wordpress.com
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Jeremy O'Donoghue
In reply to this post by Daniel Fischer-4
On 18/04/2010, Daniel Fischer <[hidden email]> wrote:
> Am Sonntag 18 April 2010 21:41:06 schrieb Daniel Fischer:
>> wx-config should have been installed as part of the wxWidgets package.
>> Is that not included in the windows-installer of wxWidgets?
>
> Seems it's not so.
> http://www.haskell.org/haskellwiki/WxHaskell/Building says
> "Windows users should also get the Windows port of wx-config."
> ( http://sites.google.com/site/wxconfig/

Sadly, the Windows port of wxWidgets doesn't contain wx-config (all of
the Unix variants have it - it's a shell script), which is a major
problem as this by far the simplest way for the build system to work
out the options used to build wxWidgets.

The Windows port of wx-config is an attempt to fix this problem, but
only currently supports gcc, hence the restriction to using MinGW
(although I guess Cygwin would probably work).

>> > If wxHaskell could be installed with one cabal command that would be
>> > incredibly cool :-)
>
> Well, it's just one cabal command if you have all non-Haskell requirements
> installed as needed.

An option I am looking at is creating a basic Windows installer for
wxHaskell which would contain a compiled copy of wxWidgets and a copy
of wx-config, and which would run cabal install wxWidgets out of the
box. (basic here means you probably don't get to choose anything at
all - not even where the wxWidgets libraries get installed)

Provided that I don't need to maintain a source distribution, this
might be a good way forward for some Windows users. The installer
would be updated for 'significant' wxWidgets updates (you would be
able to 'cabal install wx' at any time wxHaskell is updated once you
have all of the libraries)

Any interest - please let me know.

Regards Jeremy
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe
Reply | Threaded
Open this post in threaded view
|

Re: GUI (was: Re: DLL on Windows)

Neil Mitchell
:-( - it seems that cabal install wx isn't how you install it on
Windows, not by a long shot.

I'm currently a Gtk2hs user. If wx got to the point where cabal
install wx either installed wx, including all it's non-Haskell
dependencies, or printed out a message "you're a windows user who
hasn't installed wxWidgets, here's a handy url for you to click and
run then run cabal install wx again" I'd be tempted to switch. I
realise that the platform differences makes it annoying, but it would
be generally handy for Windows users.

I do appreciate the work the wx people are doing for Windows users -
it is generally going in the right direction :-)

Thanks, Neil


On Mon, Apr 19, 2010 at 2:54 AM, Jeremy O'Donoghue
<[hidden email]> wrote:

> On 18/04/2010, Daniel Fischer <[hidden email]> wrote:
>> Am Sonntag 18 April 2010 21:41:06 schrieb Daniel Fischer:
>>> wx-config should have been installed as part of the wxWidgets package.
>>> Is that not included in the windows-installer of wxWidgets?
>>
>> Seems it's not so.
>> http://www.haskell.org/haskellwiki/WxHaskell/Building says
>> "Windows users should also get the Windows port of wx-config."
>> ( http://sites.google.com/site/wxconfig/
>
> Sadly, the Windows port of wxWidgets doesn't contain wx-config (all of
> the Unix variants have it - it's a shell script), which is a major
> problem as this by far the simplest way for the build system to work
> out the options used to build wxWidgets.
>
> The Windows port of wx-config is an attempt to fix this problem, but
> only currently supports gcc, hence the restriction to using MinGW
> (although I guess Cygwin would probably work).
>
>>> > If wxHaskell could be installed with one cabal command that would be
>>> > incredibly cool :-)
>>
>> Well, it's just one cabal command if you have all non-Haskell requirements
>> installed as needed.
>
> An option I am looking at is creating a basic Windows installer for
> wxHaskell which would contain a compiled copy of wxWidgets and a copy
> of wx-config, and which would run cabal install wxWidgets out of the
> box. (basic here means you probably don't get to choose anything at
> all - not even where the wxWidgets libraries get installed)
>
> Provided that I don't need to maintain a source distribution, this
> might be a good way forward for some Windows users. The installer
> would be updated for 'significant' wxWidgets updates (you would be
> able to 'cabal install wx' at any time wxHaskell is updated once you
> have all of the libraries)
>
> Any interest - please let me know.
>
> Regards Jeremy
> _______________________________________________
> Haskell-Cafe mailing list
> [hidden email]
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
_______________________________________________
Haskell-Cafe mailing list
[hidden email]
http://www.haskell.org/mailman/listinfo/haskell-cafe