[erlang-questions] IPC bus for Erlang?
Fri Apr 3 13:24:39 CEST 2009
Just two more things:
1. It appears on Mac OS X Leopard that it is needed to instruction the
wxerlang configure script to use the newly installed wxWidgets library, like
2. in wxerlang, "make install" fails with the following error:
olibrius:wx camille$ sudo make install
escript ./install.es @libdir@
escript: exception error: undefined function 'escript__install.io':format/2
in function 'escript__install.es__1238__757603__565159':main/1
in call from escript:run/2
in call from escript:start/1
in call from init:start_it/1
in call from init:start_em/1
make: *** [install] Error 127
Sorry, I am not proficient enough in escript to be able to fix that.
I am using Erlang OTP R13A.
On Fri, Apr 3, 2009 at 12:42 PM, Camille Troillard <tuscland@REDACTED>wrote:
> Hi Dan,
> OK, I understand: I have actually tried to build wxWidgets *after*installing Erlang.
> I found some details to be a bit confusing:
> When Erlang is built, there is no warning about a deprecated or absent
> version of wxWidgets. For me it's like everything was ready to go. Having
> found that it was not the case, I have tried to follow wxerlang
> So, in the wxerlang build instruction it is said that the wxWidgets build
> should be static. Because the wxerlang driver has been built successfully
> and that it need a dynamic library, it didn't occurred to me that building
> wxWidgets and Erlang in the right order would solve the problem.
> Anyway, thanks for letting me know this. I think it would be great if the
> build instructions could reflect that*, or if by default Erland is not built
> with wxWidgets support unless a correct static library is found.
> Best Regards,
> (*) that is, tell the user that on Mac OS X the wxWidgets system library
> will not be used, and that a fresh build must be made before building
> On Fri, Apr 3, 2009 at 7:58 AM, Dan Gudmundsson <dgud@REDACTED>wrote:
>> On Mac OS X you will need to compile and install wxWidgets by yourself,
>> before compiling erlang. The wxWidgets libs that are included with Mac OS X
>> Leopard is old and is missing some things I require, (e.g. wxStyledTextCtrl
>> which provides erlang syntax highlighting).
>> See compiling instructions here:
>> Camille Troillard wrote:
>>> Hi Steve,
>>> On Thu, Apr 2, 2009 at 2:06 PM, Steve Davis <
>>> steven.charles.davis@REDACTED <mailto:steven.charles.davis@REDACTED>>
>>> I've been working on a library that does much of what you describe. It
>>> wraps for the cross-platform GUI library 'wx' that appeared in R13A
>>> release of Erlang/OTP.
>>> Yes, I have tested that on Windows and it worked well.
>>> However, on Mac OS X it compiles but I get :
>>> Erlang R13A (erts-5.7) [source] [smp:2:2] [rq:2] [async-threads:0] [hipe]
>>> Eshell V5.7 (abort with ^G)
>>> 1> sudoku:start().
>>> 2> =ERROR REPORT==== 2-Apr-2009::22:06:50 ===
>>> WX Failed loading
>>> ** exception error:
>>> 2): Symbol not found: __ZN10wxGLCanvas20MacVisibilityChangedEv\n Referenced
>>> Expected in: flat namespace\n"}
>>> in function wxe_server:start/0
>>> in call from wx:new/0
>>> in call from sudoku_gui:new/1
>>> in call from timer:tc/3
>>> in call from sudoku:tc/3
>>> in call from sudoku:init/1
>>> I didn't find the origin of this problem.
>>> However, I searched and found the symbol was defined in the wxWidgets
>>> library included with Mac OS X (libwx_macud_gl-126.96.36.199.1.dylib). Why the
>>> library is not dynamically loaded is a mystery to me.
>>> This interface runs the UI as a separate process (a gen_server), it
>>> allows you to specify the application GUI in XML which makes it very
>>> easy to design/modify/update. It allows you to pass in a callback
>>> module to use for the UI issued commands. So it's pretty close to your
>>> design target.
>>> It looks very interesting.
>>> However, my application will need to use a widespread format, so any user
>>> that has basic skill in HTML can write simple extensions.
>>> The problem is that I only started development of this library less
>>> than a month ago, it's as yet unfinished, and as yet badly documented
>>> as it's a work in rapid progress.
>>> However you may wish to keep an eye on:
>>> I am interested in anything that touches close of far GUI and Erlang.
>>> I will have a look, thanks!
>>> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions