I have a problem when i try to build my makefile project within Eclipse on Linux OS. Whole makefile executes fine except for the last command which is unsimgcr -pd input output. I get an error /bin/bash: unsimgcr: command not found.
The weirdest thing is that if i run make command from linux terminal the makefile executes fine no problems. I think I should set something within Eclipse IDE, but I don't know how and help would be appreciated.
Likely unsimgcr is in your path when you run it from the command line but not in the path when run from eclipse. Either fix the path issues, or put an absolute path to unsimgcr in the make file.
Related
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 am using ActivePerl and Eclipse Luna. I am trying to run Perl files through Eclipse but it's not working; it is giving following error
To operate correctly, EPIC requires a Perl interpreter" reason: Fail to execute command line "C:\Perl\bin\perl.exe
It was working fine earlier but for the last couple of days it is showing this error. I have reinstalled Eclipse/EPIC and tried every solution I can wind on the web like changing the perl executable path, but nothing is working for me.
I can run Perl from the command line.
So when I attempt to run Gradle 2.5 using the gradle command in cmd.exe I get the following exception.
Before attempting to run the program, the gradle client gives me the correct feedback when I enter gradle -v into cmd.exe indicating I have successfully added it to my PATH variable.
Is this a Read Write Execute problem in my System32 folder? I am administrator and as such believe I have all permission access?
Any help much appreciated.
Gradle assumes that you're running in a project directory and will create a cache in the current working directory as soon as you run anything other than gradle -v or gradle --version.
The system32 directory is rather special, so even if you run gradle as an administrator, you might not have write permissions for it as there maybe a secondary check that Windows performs.
If you really want to do this (I don't know why you would), have you tried running the command prompt as administrator? You can right-click on any shortcut for the command prompt and select 'Run as Administrator'.
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.
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.)