-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Error when installing on Windows #592
Comments
Completely blind guess but that looks like an error that stems from not wrapping paths in quotes. The space in |
My guess is that |
For your information @localpcguy, we have a development environment for Calypso running on Vagrant that will be released soon. That way you won't have to deal with configuration issues such as this one. |
Yup, I was diving deeper and every time I fixed one line (i.e. adding quotes, fixing other Windows shell related issues), another one would error, so I figured it hadn't been tested on Windows. I'm assuming Vagrant will spin up a Linux VM for development? |
@localpcguy exactly. |
Is there a plan for getting it to work in Windows? Please? |
@alexdresko: The Vagrant setup that @stephanethomas mentioned is so much easier than trying to deal with getting it running natively on Windows, even if there weren't any bugs in our configuration files. You just The alternative is requiring the installation of Cygwin or whatnot in order to be able to run We're working on releasing it publicly soon. |
While that is your opinion @Viper007Bond, I believe that if there is a desire to get Calypso widely adopted for open source WordPress, it must work on Windows (and not through a Cygwyn-style workaround or Linux VM). One of the best things about WordPress is that it runs on a variety of OSes, and the core technology (Node) also runs well on Windows as well, so that isn't a barrier. As far as I can tell, the only serious barrier (I haven't done a deep dive) is the installation/build being driven by Make instead of something cross-OS like Gulp or something similar. |
Second what @localpcguy need:) |
#100 is related to this -- spaces in the path, i.e. |
Why are you using make instead of gulp/grunt anyway? If gulp/grunt can do the same thing (which is what I'm wanting to find out), how difficult would it be to switch? |
+1 support to use gulp/grunt instead of make. |
It's probably worth opening a new, separate issue stating a case for switching away from make instead of having it being buried in an issue specifically about Windows. |
@Viper007Bond Done: #1193 |
I just wanted to let you know that we have released this portable development environment based on Vagrant that simplifies the task of running Calypso on Windows. |
I run Windows 10, and I've tried to install both with the standard CMD prompt and with Cmder. I have Clink and GNU for Windows installed, so make tries to run the makefile but it fails. The error message is as follows:
I can (it seems) get a little farther by adding
SHELL=C:/Windows/System32/cmd.exe
to the beginning of the Makefile, but then the error is:Before I started debugging further into the Makefile, I wanted to find out if it has ever been tested on Windows or if Windows is not a supported system at this time? Or am I just missing something?
The text was updated successfully, but these errors were encountered: