On 18 Dec 2015, at 20:42, Chris Lattner wrote:
>
>
>> On Dec 17, 2015, at 1:47 PM, Daniel Eggert via swift-users
>> wrote:
>>
>> If I need access to the C fcntl(2):
>>
>> int fcntl(int, int, ...)
>>
>> can I get the swift-package-manager or swift-build-tool to compile C code
>> that wraps
> On Dec 18, 2015, at 1:52 AM, Daniel Eggert via swift-users
> wrote:
>
>> On 17 Dec 2015, at 22:47, Daniel Eggert via swift-users
>> wrote:
>>
>> If I need access to the C fcntl(2):
>>
>> int fcntl(int, int, ...)
>>
>> can I get the swift-package-manager or swift-build-tool to compile C c
> On Dec 17, 2015, at 1:47 PM, Daniel Eggert via swift-users
> wrote:
>
> If I need access to the C fcntl(2):
>
> int fcntl(int, int, ...)
>
> can I get the swift-package-manager or swift-build-tool to compile C code
> that wraps this into a non-vararg version:
Hi Daniel,
I’m pretty sure
> On 17 Dec 2015, at 22:47, Daniel Eggert via swift-users
> wrote:
>
> If I need access to the C fcntl(2):
>
> int fcntl(int, int, ...)
>
> can I get the swift-package-manager or swift-build-tool to compile C code
> that wraps this into a non-vararg version:
>
> int SocketHelper_fcntl_setF
If I need access to the C fcntl(2):
int fcntl(int, int, ...)
can I get the swift-package-manager or swift-build-tool to compile C code that
wraps this into a non-vararg version:
int SocketHelper_fcntl_setFlags(int const fildes, int const flags)
{
return fcntl(fildes, F_SETFL, flags);
