Kdevelop keeps automatically inserting
#include <../../home/blah/tmp/llvm35/lib/Target/ARM/ARMInstrFormats.td>
and other similar includes at what feels like random times into my code, causing compile errors. I'm guessing this is some autocomplete script gone rogue. Anyone have any idea how to disable it?
Issue tracked at: https://bugs.kde.org/show_bug.cgi?id=315505
Which KDevelop issue are you using? This should be fixed in KDevelop 4.7.2.
Related
I just wanted to ask that can we debug a code without creating a project. I have tried many times but the debugger was not working when I am not under any project.
Debugging C files alone (without having a project) is not supported by CodeBlocks, you won't find a way with this IDE.
I just installed Eclipse CDT. Now, Eclipse works fine for me with Java, but it's not working at all with C. I'm trying to write a simple Hello World program, and I've even loaded the Hello World ANSI premade project. However, regardless of what I do, I get a "Unresolved Inclusion: _" error on all my #include.
I've looked around for half an hour trying to figure out why, installed MiniGW and tried a ton of different configurations. Can someone tell me how to fix this? I'm guessing it's because Eclipse has no idea where the .h files are. How do I set this?
I'm on Windows 7.
Thanks!
Go to the project property (right click on the project in the left panel) then C/C++ General then Paths & Symbols.
You can configure the include paths in the Include tab (the first one normally).
The include paths must be something like $MINGW_DIR/include or something like that (can't be more precise, for me it's /usr/include so...)
I've got a problem with Silverlight, or maybe more with VS2010 Ultimate. I was fooling around playing with it, when in one moment a fix that I wrote didn't fix anything. Investigating why I found out that VS is not running the new version which it just compiled, but rather an old version of application - that's why my changes don't affect it. How to fix it, and what can be the source of the problem? Maybe project configuration file got corrupted or there's something wrong with ASP.NET dev server?
Have you look at the output window? Sometimes it gives errors that aren't listed in the Error List.
Side note: I didn't see you mentioning extra libraries, but I've had this happen when a change I was making in a library wasn't reflected in another Silverlight application. For whatever reason, when I was adding a reference to the library it was copying it to the debug directory of my project and only using that version (Specific Version was off). if you're using custom libraries, you can try deleting the references and re-adding them (this works, a more permanent solution is to add the library to the solution and add it as a project reference).
I've resolved the problem which I had. The thing I did is just painfully simple - I cleared browser's cache :P
I'm new to Windows development, having messed around in Linux for a while. I need to access console functions and am having trouble getting a comprehensive list of console text attributes off the web. I would like to read wincon.h and windows.h to get the info, but I can't figure out how to get at them. Help please!
Windows does not come with these by default. If you are looking for them, you need to install the Windows SDK and dig around in the %PROGRAMFILES%\Microsoft SDKs\Windows directory.
They're normally stored along with the other SDK headers. Assuming you're using Visual Studio, the easy to look at them is to create a file, add a line to #include the file you care about, right click it, and click on the open document <whatever.h> line in the pop-up menu.
You'll have to install the Windows SDK to get the header files. Windows doesn't come with the software development tools out of the box and depending on which compiler you're using, they might not come with the compiler either.
I would try looking up the console function listing on MSDN
Has anybody found a fix for Visual Studio crashing with this error (eventlog)?
.NET Runtime version 2.0.50727.3082 - Fatal Execution Engine Error (7A2E1132) (0)
It does this when I start debugging with a problem in the xaml. Visual Studio will then silently disappear.
I've looked at SO and MS Connect but haven't found a fix or workaround. I often read that you should disable all addins but I don't have any.
EDIT: Yes, I have SP1 and the following fixes installed:
Version 9.0.30729.1 SP
KB944899 KB945140 KB945282 KB946040 KB946308 KB946344 KB946581 KB947171 KB947173 KB947180 KB947540 KB947789 KB947888 KB948127 KB953256 KB956453 KB957912 KB958017
Every time I've seen this, it's because you end up with two different versions of WPF loaded at the same time (i.e. one from GAC and one from Reference Assemblies).
In the .csproj file, is there a line called something to the effect of "Allow XAML to be Compiled in Same AppDomain"? (Sorry I can't actually remember the real name) - Blend likes to put this in and it causes problems.
I have had crashing problems with VS2008's WPF designer too. I workaround by avoiding the designer and editing the XAML by hand.
Thanks to Paul I found a very strange workaround (I verified it a few times)
open the solution
unload the project (context menu)
edit the csproj (context menu), don't make any changes
reload the project (contect menu)
If I do that before I start the debugger VS will not crash.
I just found another strange way of getting around this problem. I load the solution and before opening any xaml page, I rebuild the project. The xaml pages loads fine afterward and VS2008 does not crash.
Have you updated your VS install to SP1? There are a number of crashes fixed in the SP1 patch.
If you have installed SP1, try installing the following patch as well. It's a further fix for debugger related issues in VS 2008 SP1
http://support.microsoft.com/kb/957912
I had the same problem when trying to edit an ASP.NET MVC master page or view. I found this link. I had MBUnit Gallio installed on my machine with VS2008 integration. The problem went away when I uninstalled Gallio.
I just solved this problem (well the symptom anyway) by creating a new solution and adding all the projects in the "problem" solution into this new solution. After doing this and discarding the old solution, everything works fine.
I had the same problem after installing devart code compare V2.80.11 - earlier versions did not have this problem. After removing devart the problem went away. Reinstalled and problem came back.
I like devart code compare so I intalled it without VS2008 integration. Everything works fine now.