I am using Eclipse for Windows and have this error:
Build of configuration Debug for project helloworld
(Cannot run program "make": Launching failed)
What do I do to solve this?
Eclipse CDT on Windows depends on 3rd party tools.
You may find this useful: Setting up a compiler
I faced the same problem while installing Eclipse for c/c++ applications .I downloaded Mingw GCC ,put its bin folder in your path ,used it in toolchains while making new C++ project in Eclipse and build which solved my problem. Referred to this video
Related
I have a project that complies while linking to lib quazip.a. But the project crashes in the Qt IDE when trying to run it. In VS 2017 with Qt VS Tools I built the dll quazip.dll because the deployed project needs it. But the dll doesn't load with the error "Procedure entry point not found". Is there a way to link the dll in my project so an entry point can be found? Or is there a way to get the project to run in the IDE as well as deploy with the quazip.a lib? Or is there a way to build the quazip.dll in Qt MinGW?
I got the quazip.dll from a Qt MinGW build of quazip. All is fine now.
I need some help with trying to setup C++/Java build using Eclipse. I am following this tutorial (http://www.raywenderlich.com/11283/cocos2d-x-for-ios-and-android-getting-started) but just can't understand why I keep getting "please define NDK_ROOT".
I updated the create-android-project.sh file and applied this cmd in Terminal: export NDK_ROOT="same path to NDK as in create-android-project.sh file". When I ran the 'create-android-project.sh', I had no problem with creating the project, Running the newly created project's build_native.sh also ran with any issues.
So after following the steps to update 'Build Command' from default to whatever the tutorial is asking should compile the C++ and Java files in the project, without having to run the build_native.sh in terminal and the project in Eclipse.
If I remove the custom build to default all compiles and runs on the project on both the emulator and device.
I've attached a screenshot of the settings and Console log of the project build.
Dev Environment:
Mac OS 10.8 (Lion)
Eclipse Juno 64-BIT
Cocos2d-x v2.0-x-2.0.3
NDK: android-ndk-r7-crystax-5.beta2
Please advise.
I solved the issue by adding the NDK_ROOT variable to ADT > Preferences > C/C++ > Build > Build Variables.
Hope it helps someone, I know I've been looking for a solution for quite some time.
This error is not related to eclipse. It tell that the NDK_ROOT is not define in build_native.sh file. I solve the issue by adding NDK_ROOT at the top of the build_native.sh file
build_native.sh
NDK_ROOT="path of your ndk "
Actually you noly need to set it in C/C++ build-> Environment.
Just like this. It works for me eventually.
Refer to this picture for configuration
In the Left side pane of your eclipse , As I can read that Resources,Android ..etc
In that go in Android, there will be one option to set NDK path
Eclipse -> Window -> Preferences -> Android -> NDK -> set path to the NDK
It is same as you do it for android SDK , here you have to specify NDK path ...
EDITED:
If you still face the problem ...then it is the same problem which I faced while setting it up for my windows version
there is an issue with android ndk version for export NDK_Path .... You may try with crystax ndk version for android it will work for sure
Any more help please feel free to ask
I have been receiving the following error and have done a lot of research and tried all of the offered solutions to no avail.
junitreport:
[junitreport] Processing C:\workspace\test123\junit\TESTS-TestSuites.xml to C:\Users\Matt\AppData\Local\Temp\null1903337257
[junitreport] Loading stylesheet jar:file:/C:/Users/Matt/Documents/Selenium/eclipse/plugins/org.apache.ant_1.8.3.v20120321-1730/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
[junitreport] : Error! The first argument to the non-static Java function 'replace' is not a valid object reference.
[junitreport] : Error! Cannot convert data-type 'void' to 'reference'.
[junitreport] : Fatal Error! Could not compile stylesheet
[junitreport] Failed to process C:\workspace\test123\junit\TESTS-TestSuites.xml
BUILD FAILED
C:\Users\Matt\workspace\Test1\build.xml:122: Errors while applying transformations: Fatal error during transformation
I found a solution at ant junit build error inside eclipse and saying that the issue was caused by a newer version of JDK and using 1.6_31 would solve it and I tried that following instructions I found online on how to change the version of Java eclipse is using. Every time I run the build ant it returns the same error regardless of which version of Java I am using. I have tried JRE7, jdk1.7.0_05, jdk1.6.0, jdk1.6.0_31 and others that I don't have installed anymore.
I am running the following
Windows 7 Pro SP1 x64
Eclipse IDE for Java Developers Version: Juno Release Build id: 20120614-1722
org.apache.ant_1.8.3.v20120321-1730
If anyone could provide any assistance in getting this report running it would be greatly appreciated. I'm new to programming and this is very frustrating especially since I'm still learning all of the jargon and trying to be sure I am following the instructions properly. If you require anymore information from me I will provide it and I will follow any instruction given to the best of my ability. Thank you very much in advance.
While an Ant Bug Report 384757 claims that this is caused by the XSL Tranformer build into the Oracle JDK - which may be true - the problem can be fixed by changing the Ant version:
I tried some of the workarounds mentioned there. After a while, I found that the bug appears with Ant 1.8.3 (distributed in Eclipse), but not with Ant 1.8.2 (distributed in Eclipse 3.7).
The bug also does not appear with Ant 1.9.0.
I have downloaded Ant 1.9.0 and in configured Eclipse's "Run As -> Ant build..." to use the Ant 1.9.0 folder as ANT HOME. This worked.
PS: My Eclipse used Ant 1.8.3 (which did not work), but running Ant from the console used Ant 1.8.2 (which worked). This was confusing at first.
I have solved the issue by downloading apache-ant-1.9.1 and configuring it in Eclipse by changing the ANT HOME from windows--> Preferences and setting the ANT HOME to apache-ant-1.9.1.
Below workaround fixed the build issue I had...
Download the 2 jar files from the urls given below and add those to Ant-Runtime Classpath located on Eclipse at:
Window>Preferences> Ant>Runtime>Ant Home Entries
http://www.java2s.com/Code/Jar/x/Downloadxalanjar.htm
http://www.java2s.com/Code/Jar/a/Downloadapachexmlxercesjar.htm
Restart eclipse and run the Ant build.
eclipse executable launcher was unable to locate shared lib in windows xp OS..I keep getting this error when i launch eclipse and i browsed through but not able to find any correct solution . can anyone help me out i really in the need of eclipse right now?
Install the Java JRE/JDK ? Otherwise a more detailed error message would be helpful.
What got it all working for me was to download eclipse indigo 3.7.2 and (this is very important) EXTRACT IT DIRECTLY INTO MY PROGRAMS FOLDER. Before I would extract it to my desktop and copy into the programs folder (C:\Program Files) but I would jus get an error message saying "The Eclipse executable launcher was unable to locate its companion shared library" when trying to run eclipse.
After extracting eclipse directly to my programs folder I ran it and so far all is working well :)
I installed eclipse Helios a week ago. First I installed it without the CDT.
Today I installed the CDT along with the autotool (this it what can be seen in the list of possible updates). Afterwards, I installed also the minGW (Wascana) as written in the manual of CDT.
but after I create an Hello World project in eclipse I get this error (blinking non stopable) in the console tab:
Invoking autoreconf in build directory: D:/eclipse/proj/workspace/testcpp
Configuration failed with error
(Cannot run program "autoreconf": Launching failed)
Can anyone help me with this? What else do I need to install or config so my CDT will work?
thanks,
Eli
The autotools plug-in doesn't work on Windows yet. There is a fix in place for the upcoming Indigo Eclipse release.
The main problem is that Windows doesn't know how to run shell scripts (which is what autoreconf is). You have to launch the shell manually and ask it to run it. And that's what the fix is.