[asio] Compilation requirements
Hi, Is asio is a header-only library? If so, what are the requirements for compilation? If you are using Visual C++ with /Za (language extensions disabled), that will cause problems if you include windows.h. TIA, Sohail
On 3/20/07, Sohail Somani <s.somani@fincad.com> wrote:
Hi,
Is asio is a header-only library? If so, what are the requirements for
Not anymore.
compilation? If you are using Visual C++ with /Za (language extensions disabled), that will cause problems if you include windows.h.
You should first include asio, then windows.h IIRC.
On 20/03/07, Olaf van der Spek <olafvdspek@gmail.com> wrote:
On 3/20/07, Sohail Somani <s.somani@fincad.com> wrote:
Hi,
Is asio is a header-only library? If so, what are the requirements for
Not anymore.
I think it still is. If you're using the boost variant of cvs/0.3.8rc asio, then you need to link it with the boost system library, something like /libboost_system*/. That's shipped with the rc version of asio, IIRC. hth, Darren
On 3/20/07, Darren Garvey <lists.drrngrvy@googlemail.com> wrote:
On 20/03/07, Olaf van der Spek <olafvdspek@gmail.com> wrote:
On 3/20/07, Sohail Somani <s.somani@fincad.com> wrote:
Hi,
Is asio is a header-only library? If so, what are the requirements for
Not anymore.
I think it still is. If you're using the boost variant of cvs/0.3.8rc asio, then you need to link it with the boost system library, something like /libboost_system*/. That's shipped with the rc version of asio, IIRC.
If you need to link, it's not header only anymore.
On 20/03/07, Olaf van der Spek <olafvdspek@gmail.com> wrote:
<snip> If you need to link, it's not header only anymore.
My last answer was ambiguous. What I meant to get across was that (I think) the non-boost version of asio (ie. from asio.sf.net) requires no linking. It's only when you run the boostify.pl script, or get it from boost cvs HEAD, that you need to link it the system library.
Thanks. I hate including windows.h. Makes my nice non-language-extension-using build go flop. I guess I should just give up the fight! -----Original Message----- From: boost-users-bounces@lists.boost.org on behalf of Olaf van der Spek Sent: Tue 3/20/2007 1:02 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] [asio] Compilation requirements On 3/20/07, Sohail Somani <s.somani@fincad.com> wrote:
Hi,
Is asio is a header-only library? If so, what are the requirements for
Not anymore.
compilation? If you are using Visual C++ with /Za (language extensions disabled), that will cause problems if you include windows.h.
You should first include asio, then windows.h IIRC.
On 3/20/07, Sohail Somani <s.somani@fincad.com> wrote:
Thanks. I hate including windows.h. Makes my nice non-language-extension-using build go flop. I guess I should just give up the fight!
I think you can define lean and mean (not sure of exact spelling) and avoid including windows.h yourself.
Sohail Somani <s.somani <at> fincad.com> writes:
Hi,
Is asio is a header-only library? If so, what are the requirements for compilation? If you are using Visual C++ with /Za (language extensions disabled), that will cause problems if you include windows.h.
At the moment asio itself is header only and does include windows headers, so /Za won't work. It's something I'm looking to fix in the longer term. Cheers, Chris
participants (4)
-
Christopher Kohlhoff -
Darren Garvey -
Olaf van der Spek -
Sohail Somani