$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Edward Diener: "[Boost-build] Including one jam file into another"
- Previous message: Kuhl, Brian: "[Boost-build] Is there any difference , or is this redundant ?"
- In reply to: Kuhl, Brian: "[Boost-build] Is there any difference , or is this redundant ?"
- Next in thread: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
- Reply: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
- Reply: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
AMDG
On 01/09/2018 02:38 PM, Kuhl, Brian via Boost-build wrote:
> Hi I'm looking to update my pull request to ASIO and I'm looking at various NT logic that's are causing problems for cross-compiles.
> > In various ...
> libs/asio/example/... /Jamfile.v2
>
> else if [ os.name ] = NT
> {
> lib ws2_32 ;
> lib mswsock ;
> }
> <snip>
> <os>NT:<define>_WIN32_WINNT=0x0501
> <snip>
>
> Could we not just ?
>
> <target-os>windows:<library>ws2_32
> <target-os>windows:<library>mswsock
>
Yes, <target-os> is the correct way. <os> has
been obsolete for years.
In Christ,
Steven Watanabe
- Next message: Edward Diener: "[Boost-build] Including one jam file into another"
- Previous message: Kuhl, Brian: "[Boost-build] Is there any difference , or is this redundant ?"
- In reply to: Kuhl, Brian: "[Boost-build] Is there any difference , or is this redundant ?"
- Next in thread: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
- Reply: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
- Reply: Kuhl, Brian: "Re: [Boost-build] Is there any difference , or is this redundant ?"
$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-footer.inc");
?>