This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: DomTerm - a new console for Kawa (and everyone else)
- From: Charlie Turner <chturne at gmail dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: Kawa mailing list <kawa at sourceware dot org>
- Date: Fri, 18 Dec 2015 20:00:32 +0000
- Subject: Re: DomTerm - a new console for Kawa (and everyone else)
- Authentication-results: sourceware.org; auth=none
- References: <56733C82 dot 1050008 at bothner dot com> <CAPMhJv2OYR9FaoGPNgzOdo6RcqRq_YpUgzYSkYeO=Hhgrdxe7A at mail dot gmail dot com> <56745B04 dot 7040907 at bothner dot com> <CAPMhJv1Dx_V_QRdEsLFUoj-whSw_vT1C-SjE0Un-UbVM8HFA-w at mail dot gmail dot com> <56746287 dot 70007 at bothner dot com>
I'm mostly sure that the ".jnilib" extension is deprecated (but still
supported), and that nowadays, JNI dynamic libraries can use the same
file extension as ordinary Mac OS X dynamic libraries (i.e. ".dylib").
Either way, yeah ".so" is not the right file extension on Macs.
Ahh, interesting. Thanks for the background info.
It may be easier to start with the server, as that avoids JavaFX issues.
Perhaps try the --process option to avoid PTY issues:
Yep; I've got a terminal in the browser! Thanks Per, I'll have a play.
On 18 December 2015 at 19:46, Per Bothner <per@bothner.com> wrote:
>
>
> On 12/18/2015 11:28 AM, Charlie Turner wrote:
>>
>> I almost got this working on OSX. See my hacks in the attached patch
>> file if you want to get where I got :-) [where the heck do you get
>> err_sys from on our box??]
>
>
>> In addition to that patch file, I also had to rename libpty.so to
>> libpty.jnilib on OSX. I have no idea why. This is my first experience
>> with Native Java :-)
>
>
> I guess I should start using autoconf ...
> Including --disable-javafx and --disable-pty configure options.
>
>> Sadly, I got lost after managing to get the DomTerm to run. make-pty
>> completes, and then the DomTerm window pops up with a scroll-bar, but
>> nothing else. I get this stack trace in the terminal window from which
>> I launched make run-pty,
>
>
> It may be easier to start with the server, as that avoids JavaFX issues.
> Perhaps try the --process option to avoid PTY issues:
>
> make run-server SERVER_ARGS=--process
>
> Then you can open a web console windows in your browser to check for
> error messages.
>
> You might enable the various verbosity options, including the one
> in terminal.js:
> this.verbosity = 2; // instead of 0
>
>
>> netscape.javascript.JSException: ReferenceError: Can't find variable:
>> makeDomTerm
>
>
> That suggests the JavaScript in repl.html didn't get executed,
> or got executed in the wrong context, or something like that.
>
> I suggest try the server/browser combination first.
>
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/