I am encountering the same problem that many others have in Eclipse, as is apparent by the many questions. I found an answer in [this question] (How can I enable breakpoints in Eclipse/CDT)
So I checked my Run-->Breakpoint Types and there were none available. How do I change that?
BTW: I don't believe this should matter, but I have set up my Eclipse project by hand and added the CMake files. I have to run CMake to generated dependencies in the code. But by creating my Eclipse project by hand I should be able to debug it. So, again, how do I add Breakpoint Types?
Thank you.
I hate it when I post a question and then find the answer!
I fixed this problem by following the instructions in the Eclipse Community Forums Question, which took me to CDT/User/FAQ Eclipsepedia - Enable the C/C++ Tracepoint functionality that told me what to do.
It worked! Yay! I hope this information helps others.
Related
I want to build C++ GUI programs using Codeblocks+Wxwidgets+cmake. I tried to configure Wxwidgets with codeblocks IDE following the instructions given in the wxWidgets Discussion Forum as well as other Youtube tutorials.
I followed the youtube tutorials below.
Youtube tutorial
But, when 'DEBUG' and 'RELEASE' are being built, it keeps showing some kind of errors. As a result, the building was failed.
Please help me to solve this or suggest another easy way to do C++ GUI projects.
Thank you!
There is an excellent document explaining how to set up C::B with wxWidgets. It can be found here.
It is not about CMake-thingy, but it is written with enough details to help people understand how to setup the IDE.
So I suggest to delete C::B, delete wxWidgets, delete all projects you setup before and start all over, following the instructions from PB to a T.
If you hit a wall or something will not work - please comeback with the exact explanation.
Problem is the same as here:
Visual Studio 2017 - Not Able to see Publish - Missing Profile / Deployment Options
https://developercommunity.visualstudio.com/content/problem/129404/missing-publish-menu-in-netcore-web-project-right.html
except the fact that I didn't see the button earlier (I've started coding in Visual Studio just recently). I've installed some packages, which were adviced in mentioned topics, like "Azure" and "ASP.NET", but it didn't solve the problem. I don't understand, how it could help (I code on C++ and have not to use these packages, do I?) and what exactly I should do (maybe I've downloaded something wrong).
Thank you in advance!
Update
If I understand right, there is no way to "publish" C++ code, according to:
https://social.msdn.microsoft.com/Forums/en-US/6998eadb-36fb-4a97-bba5-0de49d533732/how-can-i-publish-a-visual-c-project-?forum=vsclassdesigner
Then, how to make standalone exe-file, that doesn't require something other like .pdb, .ipdb and .iobj and can be run on another coumputer without Visual Studio?
The command that creates the binary is called "Build".
I can't say for sure, but I think that "Debug" builds to run on another computer need vcredist, while "Release" builds can run without anything else. Again, I am not sure.
according to this link Xcode 5 should be able to interpret doxygen-like documentation, and make them show up in quick help. A similar question was already asked here, however there was no info on what to do if it doesn't work.
I'm working on an external c++ makefile project, using Xcode only to make coding and debugging easier. The project is compiling and running correctly. I'm using a framework called COIN-BCP, which is fully doxygen documented. I can also create the doxygen html documentation from the terminal, it works fine. However, in the quick help in Xcode it doesn't show up
My questions are:
Do I have to turn on any extra settings in Xcode to make this work?
Does the makefile project have anything to do with the problem? I'm not exactly sure when Xcode is supposed to interpret the doxygen comments. During compilation?
Does anyone have a working makefile project, where the quick help documentation works?
Any suggestions how I could fix this? Also, I'd be happy to try any workarounds.
Thanks in advance!
I have managed to solve this by following this guide.
i am debugging c++ with eclipse on a linux VM.
The eclipse I am using is Kepler Service Release 1.
I compile the files using Automake.
When I try to debug in Eclipse and do stepover it sometimes jump to backward lines, sometimes it goes into the line. Also when there is a problem it just shows nothing. When I try to see variables it doesn't always succeed. It seems the Eclipse behavior is not so good.
I come from Windows programming and it looks very much like I saw when we compiled release version and tried to debug it in Visual.
Can anyone plesae assist? I can't debug like this. Is there any configuration? something I do wrong?
Thanks
As Martin James stated all I needed was to turn off all optimizations.
I had -o2 flag and needed to remove it.
I have a fairly large fortran90 project in Photran. I find that sometimes the editor just hangs or is very slow. Saving a file or using ctrl+/ for commenting lines seems to trigger this slowness. Any solutions to this?
I do have refactoring turned on as I find it useful to navigate, turning that off seems to help some. Any other solutions?
I am using eclipse-Galileo, photran 5.0 on linux OS. I have jdk 6 as my java environment. Will updating to Helios and a later photran make a difference? Is it easy to update to Helios?
Edit: Just checked TOP, the cpu is working at 100% when I am trying to save a file! And I even have the refactoring turned off.
Here is the answer to this question from the photran mailing list...
http://dev.eclipse.org/mhonarc/lists/photran/msg01691.html
See the rest of the thread for more information.
The only solution for now seems to be to turn off refactoring.
I was able to reproduce the issues with Photran refactoring on and off when using the same workspace with different Eclipse versions. I think you have to remove your ~/.eclipse and ~/workspace/.metadata directories and have a fresh start. I have been using the latest Eclipse (Kepler) with Photran refactoring on/off without any issue.