edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse Development <Edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] compiling edbrowse with js24
Date: Thu, 30 Jan 2014 10:33:22 +0000	[thread overview]
Message-ID: <20140130103322.GK7404@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87wqhil5jv.fsf@mushroom.PK5001Z>

On Wed, Jan 29, 2014 at 03:41:24PM -0800, Chris Brannon wrote:
> Chuck Hallenbeck <chuckh@ftml.net> writes:
> 
> So don't modify the makefile.  I'd suggest a script like this one:
> 
> #!/bin/sh
> # ebmake, build edbrowse
> # Expects to be run from the root of the edbrowse tree,
> 
> LDFLAGS=-L/usr/local/lib make JS_CXXFLAGS=/usr/local/include/mozjs-24
> # End of script.
> 
> This is sort of how we do things when packaging for distributions.
> Typically, we don't write patches against the makefile, because they're
> fragile.  It's better to set variables or flip configure switches.
> Since edbrowse doesn't have a configure script, we end up setting
> environment variables, or in the case of JS_CXXFLAGS, "make" variables.
> Don't make the mistake of using JS_CXXFLAGS as an environment variable,
> because make will override it.

Good point.

> Instead, it needs to be passed after the make command, so make will do
> the substitution:
> make JS_CXXFLAGS=whatever

You may also want to add -Wno-invalid-offsetof to the JS_CXXFLAGS variable to
prevent *lots* of warnings about stuff in various mozjs-24 headers.

Cheers,
Adam.

  reply	other threads:[~2014-01-30 10:33 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 [this message]
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=20140130103322.GK7404@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@the-brannons.com \
    /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).