From: "Guilhem Bonnefille" <guilhem.bonnefille@gmail.com>
To: "Domenico Andreoli" <cavokz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: multiple checked out branches
Date: Thu, 2 Aug 2007 19:16:08 +0200 [thread overview]
Message-ID: <8b65902a0708021016j4eb11577v8da5bd67df58adea@mail.gmail.com> (raw)
In-Reply-To: <20070802000217.GA20018@raptus.dandreoli.com>
On 8/2/07, Domenico Andreoli <cavokz@gmail.com> wrote:
> On Wed, Aug 01, 2007 at 11:19:25PM +0100, Julian Phillips wrote:
> The actual problem is that switching form a branch to another makes
> my autotools fuck and I have to rebuild stuff all the time. My box is
> still a faint-hearted single core...
I encounter same problem. Actually, I did full rebuild every time
(which is counter-productive). But, reading at your mail, I have an
other idea: what about the "remote" compilation offered by autotools?
Normally, autotools are design in such way that you can share the same
source for different configuration. To do this, simply create one
"build" directory per branch, go to this directory and do:
../configure && make
I'm unable to try it now, so I express now all my "confuses" if it was
a bad idea.
--
Guilhem BONNEFILLE
-=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com
-=- mailto:guilhem.bonnefille@gmail.com
-=- http://nathguil.free.fr/
next prev parent reply other threads:[~2007-08-02 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 22:04 multiple checked out branches Domenico Andreoli
2007-08-01 22:19 ` Julian Phillips
2007-08-02 0:02 ` Domenico Andreoli
2007-08-02 17:16 ` Guilhem Bonnefille [this message]
2007-08-01 22:34 ` Alex Riesen
2007-08-01 22:39 ` Johannes Schindelin
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=8b65902a0708021016j4eb11577v8da5bd67df58adea@mail.gmail.com \
--to=guilhem.bonnefille@gmail.com \
--cc=cavokz@gmail.com \
--cc=git@vger.kernel.org \
/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).