On linux
The Glorious Glasgow Haskell Compilation System, version 8.6.5
compiled using version 2.4.0.1 of the Cabal library
1.3.6.1-BYFFNcZJFE8A61mvswaSZH) requires time-1.8.0.2
wxdirect would not istall via cabal. Downloading the archive to dig deeper
and running configure I get
This package i
Hi,
> it seems that the problem lies with wxc. I (for now) have provided
> bin/mk-cabal to build locally, did you use that, what is the full
> build output, in particular w.r.t wxc?
Yes, I have used bin/mk-cabal. The full build output is here:
http://pastebin.com/XSgGDh9E (Atze, nevermind my last
Hi Melanie,
it seems that the problem lies with wxc. I (for now) have provided bin/mk-cabal
to build locally, did you use that, what is the full build output, in
particular w.r.t wxc? wxc build (e.g.) might fail because of an
incorrect/incomplete install of wxWidgets. Is the correct (and not an
Hi,
thanks for your quick help, Atze.
> this problem is fixed in the forked repo
> https://github.com/atzedijkstra/wxHaskell. See the README there. The
> intent is that this fork will merge back into the official repo and
> an update of the version available via cabal and Hackage.
I have install
Hi Melanie,
this problem is fixed in the forked repo
https://github.com/atzedijkstra/wxHaskell. See the README there. The intent is
that this fork will merge back into the official repo and an update of the
version available via cabal and Hackage.
regards,
On 2 Aug, 2013, at 01:19 , "M. Schu
Hi,
I'm on Fedora 18, having installed wxWidgets (GTK) 2.9 in ~/local, ~/local/bin
is in $PATH. When I do 'cabal install wx', the following error gets triggered:
[...]
/usr/bin/gcc -Wl,--hash-size=31 -Wl,--reduce-memory-overheads -Isrc/include
-I/home/mel/local/include/wx-2.9
-I/home/mel/local
Eric Kow writes:
> >PATH: (add these)
> > %WXWIN%\lib\gcc_dll;%WXWIN%;%CABAL_DIR%\wxc-%WXC_VERSION%\%GHC_VERSION%
> So by rights, as far as building wxHaskell and wxHaskell apps is concerned
(sandbox or no), we need
> “only” really set the WXWIN and WXCFG environment variables. I forget
wha
On 2 Jun 2013, at 08:44, harry wrote:
> Referring to the installation instructions, we have the following
> environment variables:
>
>CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents
> and Settings\XXX\Application Data\cabal, or: %APPDATA%\cabal)
>GHC_VERSION: 7.0.
Referring to the installation instructions, we have the following
environment variables:
CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents
and Settings\XXX\Application Data\cabal, or: %APPDATA%\cabal)
GHC_VERSION: 7.0.3 (for our convenience)
WXC_VERSION: 0.90.0.2
On 2 Jun 2013, at 07:56, harry wrote:
> The next hurdle is wxcore, which expects to find various bits of wxc in
> places that it should really be keeping its nose out of. I suspect that if
> everything has been set up correctly outsides of the sandbox, this too will
> succeed by following the envi
Eric Kow writes:
> OK let me get this straight. Is the user-facing problem here that
installing wxHaskell for use in a sandbox
> environment is impossible or just very inconvenient/difficult?
The problem is that cabal-dev tries to install all the dependencies
automatically. So if I have a depen
On 06/01/2013 01:34 PM, Eric Kow wrote:
> I had some longer comments on the technical issues. I think we may
> be need to step back a bit and peel apart the fundamental issues
> first (C++, shared libraries, other?) but first let's make sure we
> understand what the user-facing problem really is.
OK, so let's step back a bit.
I think Luc's right in two senses, first that we need to understand what the
user-facing problem is, and second what is technical problem lying at the heart
of user-facing problem.
In your first message you said:
> OTOH, cabal install wxdirect installs both the he
Eric Kow writes:
> May I ask which environment variables in particular you're referring to?
All of them, particularly those used to find the location of wxc. cabal-dev
installs all dependencies blindly, and doesn't know to set environment
variables.
> (B) [an aspiring wxHaskell hacker] modify w
OK, I'm studying
http://www.haskell.org/haskellwiki/WxHaskell/Windows
to update my understanding of the build infrastructure a bit
May I ask which environment variables in particular you're referring to?
So for the matter of executables not being on the path, two approaches might be
(A1) [the
Eric Kow writes:
> Is the issue something related to the wxdirect executable not being
> available in the sandbox environment?
Yes - executables built in cabal-dev aren't on the path (which is different
for each sandbox). If wxdirect only built an executable, I could install it
outside of the sa
btw, we are already at the solution stage,
what is the problem in fact ? what are the typical difficulties that a raise
when installing wx ?
is it on the C side or on the haskell side ?
is it because they have to be fetched separately ?
do we have a shared view on where lies the problems ?
On 31 May 2013 06:34, harry wrote:
> The first problem is that wxdirect installs both executables and a library -
> why is that necessary, and is there another way to do it?
Could you elaborate on this? I'm not 100% sure I follow.
Is the issue something related to the wxdirect executable not bei
Blair Archibald writes:
> The logical first step seems to be to combine the 3 packages (wxcore, wx,
wxc) into some form of singly installed package. I'm a novice when it comes
to cabal so not sure how what the effects of such a change could be.
> I appreciate that cabal is a great system for inst
Simpler would be fantastic, but there are technical reasons for the current
setup. If you can meet the same goals whilst delivering an easier install
experience (or boldly cut off goals that can be better understood as
wrongheaded), more power to ya!
* wxc - C++ to C wrapper. Uses make (or can
I agree that the current deployment system for wxHaskell is not ideal and
we should probably look into changing it. Does anyone have any ideas as to
how we could go about this?
The logical first step seems to be to combine the 3 packages (wxcore, wx,
wxc) into some form of singly installed package
Building Gtk2Hs on Windows is very straightforward. After Gtk+ is included
in the path, cabal install gtk2hs-buildtools will install all the
executables needed for building the bindings, but no libraries. cabal
install gtk will then install the library.
OTOH, cabal install wxdirect installs both t
I have just installed wxHaskell 2.9.3 on OS X Lion from source.
When I run cabal install wx, wxc building fails with the following error:
src/cpp/ewxw_main.cpp: In function ‘void
ELJApp_InitializeC(wxClosure*, int, char**)’:
src/cpp/ewxw_main.cpp:99: warning: deprecated conversion from string
con
shelarcy:
> On Fri, 06 Mar 2009 02:45:28 +0900, Don Stewart wrote:
> > Much better,
> >
> > (snip)
> >
> > cat config/wxcore.pkg | sed -e "s|\${wxhlibdir}|/usr/lib|" | ghc-pkg
> > update -
> > Reading package info from stdin ... done.
> > ghc-pkg: /usr/lib/imports doesn't exist or isn't a director
On Fri, 06 Mar 2009 02:45:28 +0900, Don Stewart wrote:
> Much better,
>
> (snip)
>
> cat config/wxcore.pkg | sed -e "s|\${wxhlibdir}|/usr/lib|" | ghc-pkg
> update -
> Reading package info from stdin ... done.
> ghc-pkg: /usr/lib/imports doesn't exist or isn't a directory (use
> --force to override
shelarcy:
> Hi,
>
> On Thu, 05 Mar 2009 15:04:23 +0900, Don Stewart wrote:
> > wxc/src/eljdc.cpp: In function ‘void wxDC_EndDrawing(wxDC*)’:
> > wxc/src/eljdc.cpp:26: warning: ‘void wxDCBase::EndDrawing()’ is deprecated
> > (declared at /usr/include/wx-2.8/wx/dc.h:393)
> > wxc/src/eljdc.cpp: At
Hi,
On Thu, 05 Mar 2009 15:04:23 +0900, Don Stewart wrote:
> wxc/src/eljdc.cpp: In function ‘void wxDC_EndDrawing(wxDC*)’:
> wxc/src/eljdc.cpp:26: warning: ‘void wxDCBase::EndDrawing()’ is deprecated
> (declared at /usr/include/wx-2.8/wx/dc.h:393)
> wxc/src/eljdc.cpp: At global scope:
> wxc/src/
wxc/src/eljdc.cpp: In function ‘void wxDC_EndDrawing(wxDC*)’:
wxc/src/eljdc.cpp:26: warning: ‘void wxDCBase::EndDrawing()’ is deprecated
(declared at /usr/include/wx-2.8/wx/dc.h:393)
wxc/src/eljdc.cpp: At global scope:
wxc/src/eljdc.cpp:629: error: ‘wxMetafile’ was not declared in this scope
wxc/s
shelarcy:
> Hi,
>
> On Sat, 11 Oct 2008 11:26:43 +0900, Don Stewart <[EMAIL PROTECTED]> wrote:
> > configuration:
> > library: wxhaskell-0.10.4 (release 0)
> > (snip)
> >
> > *** config/config.mk:22: *** missing separator. Stop.
> > cabal: Error: some packages failed to install:
> > wxcore
shelarcy:
> Hi,
>
> On Sat, 11 Oct 2008 11:26:43 +0900, Don Stewart <[EMAIL PROTECTED]> wrote:
> > configuration:
> > library: wxhaskell-0.10.4 (release 0)
> > (snip)
> >
> > *** config/config.mk:22: *** missing separator. Stop.
> > cabal: Error: some packages failed to install:
> > wxcore
Hi,
On Sat, 11 Oct 2008 11:26:43 +0900, Don Stewart <[EMAIL PROTECTED]> wrote:
> configuration:
> library: wxhaskell-0.10.4 (release 0)
> (snip)
>
> *** config/config.mk:22: *** missing separator. Stop.
> cabal: Error: some packages failed to install:
> wxcore-0.10.4 failed during the buil
configuration:
library: wxhaskell-0.10.4 (release 0)
compiler:ghc-6.10.0.20081007
wxwidgets: gtk-2.8.9
extensions:
openGL:no
mediactrl: no
contrib: no
library dir: /home/dons/.cabal/lib
done:
type 'make' to build wxhaskell.
type 'make install' to install wxhaskell
32 matches
Mail list logo
