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: Thu, 30 Jan 2014 10:21:22 +0000	[thread overview]
Message-ID: <20140130102122.GI7404@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <alpine.LNX.2.03.1401291755240.22740@ftml.net>

On Wed, Jan 29, 2014 at 05:57:59PM -0500, Chuck Hallenbeck wrote:
> On Wed, 29 Jan 2014, Chris Brannon wrote:
> 
> > Adam Thompson <arthompson1990@gmail.com> writes:
> >
> > > Where did it install to?
> >
> > Looks like it uses autotools, so my guess is under /usr/local.  Chuck,
> > I'd look under /usr/local/include/mozjs-24 for the headers and
> > /usr/local/lib for the libraries.
> 
> Yes, that's where they were.
> 
> Next question: If I modify the edbrowse makefile to add those flags, what
> happens to my modifications when the makefile iks updated?

Git complains about uncommitted changes and you have to revert your changes.
You shouldn't need to modify the makefile anyway,
see my previous message for how to build without doing this.
That, and dependancy tracking, are the two big advantages of using make over a
build shell script in my opinion.

Cheers,
Adam.

  parent reply	other threads:[~2014-01-30 10:21 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
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 [this message]
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=20140130102122.GI7404@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).