edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chuck Hallenbeck <chuckh@ftml.net>
Cc: Edbrowse Development <Edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] compiling edbrowse with js24
Date: Wed, 29 Jan 2014 13:44:09 +0000	[thread overview]
Message-ID: <20140129134409.GG7404@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <alpine.LNX.2.03.1401290701220.8817@ftml.net>

Hi Chuck,

On Wed, Jan 29, 2014 at 07:12:10AM -0500, Chuck Hallenbeck wrote:
> Hi all,
> I retrieved and compiled the js24 sources, using the default instructions +
> "make install", apparently successfully (no fatal errors, numerous
> warnings)

Where did it install to?

> 
> I retrieved the master branch of edbrowse from git after Adam's pushes
> yesterday, but the compile failed when jsapi.h could not be found.
> 
> "locate" shows the existence of jsapi.h under /usr/include/js and also
> /usr/include/js-17.0, apparently from earlier versions from the arch
> repositories, and other jsapi.h files under the source directories for
> js24.
> 
> I'm wondering if I need to add a link somewhere to point to the new jsapi.h
> files?

No, simply set JS_CXXFLAGS and JSLIB to point to your new mozjs24 installation.
On my system, I install custom libs under ~/usr so this looks like:
make JS_CXXFLAGS=-I/home/adam/usr/include/mozjs-24 JSLIB="-L/home/adam/usr/lib -lmozjs-24"

You also have to have the custom library path (in my case /home/adam/usr/lib) on your LD_LIBRARY_PATH for this to work.

Alternatively, if you've installed under /usr/local (default I think):
make JS_CXXFLAGS=-I/usr/local/include/mozjs-24 JSLIB=-lmozjs-24

For debugging (assuming a debug build of mozjs already):
CFLAGS="-g -gdb" CXXFLAGS="-g -gdb" make <js_settings> STRIP=""

Where <js_settings> is the js set up required to make things compile.

Cheers,
Adam.

  reply	other threads:[~2014-01-29 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 12:12 Chuck Hallenbeck
2014-01-29 13:44 ` Adam Thompson [this message]
2014-01-29 22:05   ` Chris Brannon
2014-01-29 22:57     ` Chuck Hallenbeck
2014-01-29 23:41       ` Chris Brannon
2014-01-30 10:33         ` Adam Thompson
2014-01-30 10:21       ` Adam Thompson
2014-01-29 22:16 Karl Dahlke
2014-01-29 23:08 Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140129134409.GG7404@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chuckh@ftml.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).