I am having trouble running mono CLI commands inside the msysgit console. It works fine in the windows command prompt added by the Mono installer. I have paid attention to the path env variable in the mono command prompt and added C:\Program Files (x86)\Mono\bin\; to the beginning of my system path (and restarted msysgit).
I am getting the following error when trying to run xbuild:
/c/Program Files (x86)/Mono/bin/xbuild: line 2: cygpath: command not found Cannot open assembly 'xbuild.exe': No such file or directory.
What am I missing from msysgit to help mono's CLI tools work better?
Mono for windows is built with cygwin + mingw (see Mono compile guide).
I'm not sure whether it's fully compatible with msys or not. From the error, I guess there is a problem of path. You may need cygpath.exe in your path from the following link. You should probably invoke mono either from Cygwin or cmd (through the bat provided files).
Even if mono for windows is compiled with mingw (and thus should not depend on cygwin), from your error, we can see there are still cygwin dependencies.
Related
I followed the gcc compiler installation tutorial for windows from the vscode website: https://code.visualstudio.com/docs/cpp/config-mingw
And the bin folder (C:\msys64\mingw64\bin) is empty, so i'm not able to run the "g++ --version" by adding this path to the Windows path environment variable.
My alternative to it was to use the codeblocks compiler to run my code in vscode, by adding this path: (C:\Program Files\CodeBlocks\MinGW\bin) to the "path" selection in the windows environment variables.
I want to make the MSYS2 compiler work properly in my vscode.
Hope you guys can help me!
MSYS2 comes with a package manager pacman that you should use to install any components you need.
In your case, open the MSYS2 shell (by running mingw64.exe) and run the following commands:
pacman -Syu --noconfirm
pacman -S mingw-w64-x86_64-toolchain
The first command will tell the package manager to update it's database, the second command will get the MinGW-w64 64-bit GCC compiler.
If you don't really need MSYS2 (e.g. because you dan't plan to use the MSYS2 shell) you could also consider getting a standalone MinGW-w64 build from https://winlibs.com/
I have already installed vimplug I can open the file but has no effect on Neovim 1
The error says that your plugin manager (vim-plug) isn't able to run the git executable. It needs to do this to fetch the plugins you're trying to load. So install git, make sure you can run it from your PowerShell command line, and you should be set.
I have been tasked with creating a build server for a Xilinx project. The developer for the project provided me with the steps he manually takes to do a build, and those work fine. I am now trying to do the build via the command line, so I can set up a script to do the build. From my understanding, the command:
ECLIPSECPATH\eclipsec.exe -nosplash -vm “JAVAVMPATH\jvm.dll” -application org.eclipse.cdt.managedbuilder.core.headlessbuild -build all -data WORKSPACE -vmargs -Dorg.eclipse.cdt.core.console=org.eclipse.cdt.core.systemConsole
Should be the correct command to perform the build (the all caps names being file paths to the various files needed). I use the same command for importing (except -import instead of -build), which does work correctly. But when I run the command, it returns a bunch of errors that are either "Cannot run program "make": Launching failed" or "Error: Program "make" not found in PATH".
The build works just fine when building from the GUI, and I didn't have to use the Tool Change Editor to change anything (it worked by default). Am I missing something from my command, or is there something else I need to set? Are the projects just missing something needed? I'm not a developer, but I would think if it builds from the GUI, the projects have everything they need to build.
I have a project where I run a Xilinx eclipse project in headless mode. It is on a Linux system, but I think what I am about to say applies to windows too.
When one of the Xilinx GUI apps run the first thing they do is source some environment settings. If you are not sourcing this before you run the command line above then you may be missing some paths in the environment, in particular the path to "make" which is not part of windows.
There is a batch file under C:\Xilinx\SDK\2014.4\ (or whichever version you have installed) called settings64.bat.
Running this before the eclipse command line should setup the tool environment you require.
C:\Xilinx\SDK\2014.4\settings64.bat
As part of the setup I also run this to help setup the workspace.
xsdk -wait -script sdk.xml -workspace WORKSPACE
I have installed swig on my mac and it works in the console just fine. If I type swig -verison in terminal it spits out the version. Eclipse keeps telling me that it can't find swig. I am using the liquidfun library http://google.github.io/liquidfun/SWIG/html/index.html and it told me to put this export SWIG_BIN=$("which" swig) in .bashrc, which I did. This enviroment variable registers through terminal as well. Eclipse STILL won't grab swig properly. What the hell?
Bash reads .bash_profile, .bash_login or .profile. I don't expect the Eclipse process to load such a file (although I could be wrong) nor the SWIG_BIN variable to augment its search path for executables, but if you launch Eclipse from the shell, it should inherit the shell's environment variables.
Try running swig from eclipse using a full absolute path (the one that "which" returns).
The eclipse.ini file can set some startup parameters but perhaps not the path. There might be other eclipse startup files.
Another possibility is to add swig's directory to the path in a login script. (To test that, log out and back in, then start eclipse.)
I'm trying to install Scalatra on windows seven and need to change a file to executable...the Scalatra documentation says to do this, which is unix. What is the windows equivalant?
chmod u+x srt
You can simply open the relevant folder with a unix command prompt (I use git bash) and execute the unix commands from there
To get scalatra-sbt going on Windows, either port you own sbt.bat from scalatra-sbt, or install chmod via cygwin.
Assuming you've successfully installed the rest of Conscript and giter8, you can start a project that downloads scalatra-sbt. From there, one can look through the ./sbt source, and port the bash script functionality to your own windows specific script, or install a unix compatibility layer into Windows. If you go down the "windows specific script" route, perhaps the scalatra-sbt would appreciate the project contribution.
The "unix compatibility layer" route will eventually allow you to run ./sbt. chmod is a unix command line function, and is provided in a default package of the tool set cygwin, which provides a complete lunix-like environment. Once inside a cygwin terminal, you can chmod your file, as mentioned in the scalatra-sbt first project.
Diving into the contents of ./sbt from scalatra-sbt, this is actually unix script wrapper around the scala build tool (also referred to, confusingly, as sbt). If while trying to run ./sbt you get strange '\r' errors, install the cygwin package dos2unix, and then run it on the sbt file. If you run into any "which: no curl in..." or "which: no wget in..." errors, go back to the cygwin installer, find those packages such as wget, and then install those programs.
By the way, the last thing the scalatra-sbt script runs is the Scala build tool. The Scala build tool sbt itself has many reported issues with cygwin's default configuration, so you will likely need to do more research. Depending on what issues you're running into on your specific setup, you may need to make changes to the end of the ./sbt script to adjust the parameters used to launch the Scala build tool.