From: "Luke-Jr" <luke@dashjr.org>
To: "Michael Grønager" <gronager@ceptacle.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] libcoin (HEAD) now supports boost < 1.47 - please test
Date: Thu, 2 Feb 2012 18:27:31 -0500 [thread overview]
Message-ID: <201202021827.34097.luke@dashjr.org> (raw)
In-Reply-To: <50342F76-062C-4A88-A5DA-A77C799AEC80@ceptacle.com>
On Thursday, February 02, 2012 5:43:07 PM Michael Grønager wrote:
> Enabling dynamic libs was on my TODO, but on the
> Redmond_OS_not_to_be_mentioned you need to : * prepend class definitions
> with __declspec(dllexport) when you compile the dll * prepend class
> definitions with __declspec(dllimport) when you use the dll I just love
> the way they spoil their developers...
I hadn't even thought of this. Sounds like a pain :/
The problem I had was related to *using* static libraries; ie, boost.
I have libboost*.so, but libboost*.a
prev parent reply other threads:[~2012-02-02 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 13:46 [Bitcoin-development] libcoin (HEAD) now supports boost < 1.47 - please test Michael Grønager
2012-02-02 16:30 ` Luke-Jr
2012-02-02 22:43 ` Michael Grønager
2012-02-02 23:27 ` Luke-Jr [this message]
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=201202021827.34097.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gronager@ceptacle.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