Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

buckd on Windows #1361

Open
jeeloo opened this issue Jun 1, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@jeeloo
Copy link

commented Jun 1, 2017

I have been trying to build a C/C++ project on windows and one thing that I have noticed is that there is a new buckd process for each time I invoke "buck build". I just have these two files in a folder

BUCK:

cxx_binary(
        name = 'echo',
        srcs = [ 'hello-world.c', ],
)

hello-world.c:

#include<stdio.h>
main()
{
    printf("Hello World!\n");
}

And no matter if it is up to date or not a new buckd process i spawned every time, I have watchman in the path and that is being used

> ...\bin\buck build -j 1 //:
Using watchman.
[-] PARSING BUCK FILES...FINISHED 0.0s [100%]
BUILT 1/5 JOBS 0.1s //:echo#default,private-headers
BUILT 2/5 JOBS 0.0s //:echo#default,preprocessor-deps
hello-world.c
BUILT 3/5 JOBS 0.6s //:echo#compile-hello-world.c.obj5c20620a,default
BUILT 4/5 JOBS 0.3s //:echo#binary
BUILT 5/5 JOBS 0.0s //:echo
[-] BUILDING...FINISHED 3.4s [100%] (5/5 JOBS, 5 UPDATED, 3 [60.0%] CACHE MISS)
[-] DOWNLOADING... (0.00 B/S AVG, TOTAL: 0.00 B, 0 Artifacts)
@ilya-klyuchnikov

This comment has been minimized.

Copy link
Member

commented Jun 1, 2017

I failed to reproduce it. @jeeloo could you run the following command in Powershell Get-WmiObject Win32_Process -filter "CommandLine like 'buckd%'" and put the output here?

@jeeloo

This comment has been minimized.

Copy link
Author

commented Jun 2, 2017

@ilya-klyuchnikov

This comment has been minimized.

Copy link
Member

commented Jun 8, 2017

@jeeloo could you try ilya-klyuchnikov@c2a8dcb? Thanks

@jeeloo

This comment has been minimized.

Copy link
Author

commented Jun 26, 2017

@ilya-klyuchnikov I still get the same behaviour.

@ilya-klyuchnikov

This comment has been minimized.

Copy link
Member

commented Jun 27, 2017

According to your logs you have Windows 7 Enterprise.
Internally, buckd on windows uses windows named pipes for communication between client/server. We are testing/supporting it only on Windows 10 reliably so far. It is quite possible that we hit default system settings when we create named pipes and these settings are forbidding to create named pipes on your machine.

I am sorry, but we don't have any bandwidth to investigate/fix it right now.

You could enable NO_BUCKD=1 system var, and use buck without daemon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.