[erlang-questions] IPC bus for Erlang?

Camille Troillard tuscland@REDACTED
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

cd wx

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
> instructions.
> 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,
> Cam
> (*) 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
> Erlang.
> 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:
>> http://apps.sourceforge.net/mediawiki/wxerlang/index.php?title=Getting_Started
>> /Dan
>> 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>>
>>> wrote:
>>>    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]
>>> [kernel-poll:false]
>>> Eshell V5.7  (abort with ^G)
>>> 1> sudoku:start().
>>> <0.34.0>
>>> 2> =ERROR REPORT==== 2-Apr-2009::22:06:50 ===
>>> WX Failed loading
>>> "wxe_driver"@"/usr/local/lib/erlang/lib/wx-0.98/priv/i386-apple-darwin9.6.0"
>>> ** exception error:
>>> {load_driver,"dlopen(/usr/local/lib/erlang/lib/wx-0.98/priv/i386-apple-darwin9.6.0/wxe_driver.so,
>>> 2): Symbol not found: __ZN10wxGLCanvas20MacVisibilityChangedEv\n  Referenced
>>> from:
>>> /usr/local/lib/erlang/lib/wx-0.98/priv/i386-apple-darwin9.6.0/wxe_driver.so\n
>>>  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-  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:
>>>    http://github.com/komone/gx
>>> I am interested in anything that touches close of far GUI and Erlang.
>>> I will have a look, thanks!
>>> Best,
>>> Cam
>>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://www.erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20090403/3d74c30d/attachment.htm>

More information about the erlang-questions mailing list