[wxhaskell-devel] [ wxhaskell-Bugs-3518787 ] wxc build doesn't install libwxc.so

[SourceForge . net]

Bugs item #3518787, was opened at 2012-04-17 06:15
Message generated for change (Tracker Item Submitted) made by peti
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=536845aid=3518787group_id=73133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Peter Simons (peti)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxc build doesn't install libwxc.so

Initial Comment:
When I build and install wxc on Nixos, then the Setup.hs procedure fails to 
installs the generated libwxc.so DLL into the target directory. A complete 
build log is attached below that shows the output from running ./Setup 
configure -v3  ./Setup build  ./Setup copy -v3.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=536845aid=3518787group_id=73133

--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel

[wxhaskell-devel] GitHub repo?

[Jeremy O'Donoghue]

Hi developers,

I wanted to canvas opinion about moving wxHaskell development from darcs on
code.haskell.org to (git, obviously) on GitHub.

Potential advantages:

   - Easier for new committers to commit code
   - GitHub provides some pretty decent tools (integrated issue tracker,
   particularly)
   - Easier handling of the wxWidgets 2.8/2.9 branches. I'm pretty
   impressed at the way git does this (and was not impressed by merging Dave
   Tapley's darcsden branch back into the code.haskell.org mainline using
   darcs - this turned out to be a completely manual operation which was no
   fun at all).

Downsides:

   - I personally find darcs easier than git, and as Haskellers we should
   promote darcs if possible
   - Possibly a new tool for old hands to learn

I would say that a move is probably only worthwhile if we think that it
would help to attract new developer to the project.

I have put up an experimental project at
https://github.com/jodonoghue/wxHaskell which gives an idea how the two
branches would look.

One option might be to use wxHaskell as a test case for darcs-bridge, in
which case we could allow commits to darcs or Github, but I'll leave it to
Eric to decide whether darcs bridge is ready for such a use case.

Regards

Jeremy
--
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev___
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel