I 've a c++ code. but its with .cpp,v extension. I want to debug and compile the code. Can anyone please throw some light on that topic. I want to know what v indicates? & how to debug the code?
It's a file from CVS or some related version control system. The files ending with ",v" are not the actual source files, rather these are housekeeping files used by CVS.
You will need to go back to the CVS repository and get the .cpp and .h source file(s).
Related
Recently, newer versions of cppcheck (2.8.2) are create files ending with .analyzerinfo for every source file in my repository.
So example.c would have a file created called example.c.analyzerinfo.
Is there a way to control where these files are stored?
The --cppcheck-build-dir is set and populated with files but the analyzerinfo files are still created in my source directory.
It's a recent bug, as mentioned here. It hasn't yet been fixed since the offending commit.
I'm using Xcode as an IDLE editor of C language. I downloaded an SDK package from a algorithm competition website and compiled it successfully on the terminal, but now I have a need to compile and run the source .cpp file(that inside the SDK packadge) directly by Xcode, so:
Is there a way to replace the CPP source file of command-line-tools project with the CPP source file that I specify the path of it?
Or is there a way to creat a new command-line-tools project from the specified path CPP source file?
I've now Solved this problem through the method one whitch says "Is there a way to replace the CPP source file of command-line-tools project with the CPP source file that I specify the path of it?", but still have no idea about method two.
Just creat a symbolink of CPP source file and right-click the project, add the alias to project. Because the "add" is copy in fact, instead of "import" or "open". Only by copying the alias can the purpose of modifying the source file be achieved.
I was wondering how to convert my source code to a working application.
What I mean is after I write my code I want to make app out of it. So I can use it with out a compiler running it.
After you compile, an executable file is created in the location the source code is saved to. For example, if you save your source code to a folder named C++, then in that very folder, an executable file is created which has the same name as the source code. Here's an example, I saved my source code as "aa" into the folder "C++". Now as you can see in the image, there are two "aa"'s, one is the source code, while the other is the executable program ( Well, this is the case in most C++ compilers anyway ).
Well, hope this helps you :)
I'm using Wischik's example code for creating AVI files, however after I run the code and it exits successfully no AVI file is created. I looked through the code and cannot find where it writes/saves/creates an AVI file on your computer. Does anyone know where the code saves AVI file or if it doesn't, a way to make it save the AVI file created to your computer? Thanks
link to source code here
Wischik source code
You should find test.avi in the project directory. Since you know it's name, you could also use Windows explorer to search for it.
To examine further, (assuming you are using VC++), goto
Tools > Options > Projects and Solutions > VC++ Directories,
and Show Directories for Include files.
That will tell you where the headers are.
Alternatively, set a break point at the line where AVIFileOpen is called, and follow the execution path to see what it does.
I have a very large VC++-Project which takes a long time to Rebuild after i edited a file. Maybe it's a central-class and so the following classes have to be rebuild, too. I'm using class-definitions and do include the header in the cpp-file, not .h-file in .h-file ;-)
Is there a way to find out which class/file is resposible? Are some useful tools to visualize the includes in a graph/dependencygraph? How do you get it?
Any file which directly or indirectly (through another include) #includes the file you changed will have to be rebuilt. Also if you have custom rules (say, the file you are editing is part of a custom rule that generates new source files), then any files changed by this rule and their dependencies will also have to be rebuilt.
MSDN Doc for visualizing the dependency graph:
http://msdn.microsoft.com/en-us/library/ff657798.aspx
ElectricAccelerator can help you answer this question by giving you an XML-annotated build log that includes information about which files are accessed during the compilation of each object, and the build time for each object. It has a Visual Studio plugin so it integrates right into your current environment.
Disclaimer: I'm the architect of ElectricAccelerator