From: Jay Weisskopf <jayschwa@gmail.com>
To: Fred Concklin <fconcklin@trucoin.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Introduction
Date: Mon, 22 Aug 2011 22:42:06 -0500 [thread overview]
Message-ID: <CANAndtx9PJp1ffDx7HxuQiKWf4_7G7STdAi99-VPXRp8E12W0w@mail.gmail.com> (raw)
In-Reply-To: <4E531DFD.1070407@trucoin.com>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Mon, Aug 22, 2011 at 10:26 PM, Fred Concklin <fconcklin@trucoin.com>wrote:
> I was specifically referring to building with autotools as a starting
> point. Primarily autoconf to ease the installation and testing process.
Some work has already been done for autotools (not yet merged into main
repo). You might want to start there.
https://github.com/bitcoin/bitcoin/pull/180
- Jay
[-- Attachment #2: Type: text/html, Size: 747 bytes --]
next prev parent reply other threads:[~2011-08-23 3:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:02 [Bitcoin-development] Introduction Fred Concklin
2011-08-22 19:30 ` Douglas Huff
2011-08-22 19:49 ` Luke-Jr
2011-08-22 20:12 ` Douglas Huff
2011-08-23 3:26 ` Fred Concklin
2011-08-23 3:42 ` Jay Weisskopf [this message]
2011-08-23 4:20 ` Fred Concklin
2011-08-22 20:45 ` Matt Corallo
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=CANAndtx9PJp1ffDx7HxuQiKWf4_7G7STdAi99-VPXRp8E12W0w@mail.gmail.com \
--to=jayschwa@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=fconcklin@trucoin.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