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
Configuring a Windows Environment - make #145
Comments
Please show output of |
Command prompt:
msys32:
|
Thanks. In command prompt case, it seems that running Can you try the following instructions? Create xxx:
echo generating test-x64-mingw32.def Run > make
> echo %ERRORLEVEL% In msys32 case, it seems that Can you look into why |
Command Prompt:
As for why msys is using /c/, I figured that was the purpose, to provide a Unix-like environment with / as the root. That's how I navigate to the C: drive, even though msys also doesn't list that directory with an Looking at the generated Makefile, I spotted this section near the top
and further down
I noticed the initial path was set that way after building on the msys configuration. I attempted to change the path manually to C:\ and it failed running make similar to the standard cmd:
|
I'm also going to be trying with a full MinGW setup soon as well, since it seems to have its own version of make. EDIT: Hm, seems the binary is named differently, don't know if rake can catch that |
For command prompt case, |
For msys32 case, it seems that |
So I'm understanding how the gem works, and I can get to the point where I'm generating a Makefile, and everything looks okay, but make for whatever reason isn't playing nicely with rake.
Background, I'm using Ruby 2.4.2 for Windows and GnuWin32 for make. I have msys32 as well. I'm not using a MAKE path variable, but I have put GnuWin32's bin directory into my path.
From nothing, running
rake compile
in Windows command prompt:Nothing is generated beyond the Makefile.
Switching over to msys32, I get a very different result (after clearing the temp files to start clean)
This creates the Makefile and the .def file.
Using cmder (alternative Windows command prompt) gives yet another different result
Either something's configured incorrectly or I'm missing something outright. I'm not particularly sure what's going on though. I'm far more used to development environments in macOS and Linux, and getting something on Windows that behaves similarly for development has always eluded me.
The text was updated successfully, but these errors were encountered: