edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse Development <Edbrowse-dev@lists.the-brannons.com>
Subject: Re: [Edbrowse-dev] compiling edbrowse with js24
Date: Wed, 29 Jan 2014 15:41:24 -0800	[thread overview]
Message-ID: <87wqhil5jv.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <alpine.LNX.2.03.1401291755240.22740@ftml.net> (Chuck Hallenbeck's message of "Wed, 29 Jan 2014 17:57:59 -0500")

Chuck Hallenbeck <chuckh@ftml.net> writes:

> Next question: If I modify the edbrowse makefile to add those flags, what
> happens to my modifications when the makefile iks updated?

Well, they get erased!
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.
Instead, it needs to be passed after the make command, so make will do
the substitution:
make JS_CXXFLAGS=whatever

-- Chris

  reply	other threads:[~2014-01-29 23:41 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 [this message]
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=87wqhil5jv.fsf@mushroom.PK5001Z \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.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).