| View previous topic :: View next topic |
| Author |
Message |
adamezra
Advanced Cheater
![]() Reputation: 0
Joined: 14 Feb 2007
Posts: 73
|
 Posted: Sun Oct 28, 2007 7:25 pm Post subject: [Question]Another question by me sorry >.> |
 |
|
im using visual studio 2005 and its troublesome...
i mean it doesent just compile a frigin source and .exe
it must make a million of useless files...
i compiled a very simple thing that only shows a few words
this is the things it got me
Cpp1(NCB file)
Cpp1(Html document)
Cpp1(source)
Cpp1.dsp(project file)
Cpp1.dsw(project workspace)
Cpp1.opt(OPT file)
now.. this is retarded
all i want is the exe and the source
can someone please explain what are the other files?
do i need them?
is it possible to get rid of them when compiling?...
thanks.
edit: OH and i almost forgot.. it made a folder called debug with a shitload of files and the .exe
_________________
...............................
.............................
............................
...........................
.........................
asagvsfdhg |
|
| Back to top |
|
 |
appalsap
Moderator
 Reputation: 0
Joined: 27 Apr 2006
Posts: 6753
Location: Pakistan
|
| Posted: Sun Oct 28, 2007 7:36 pm Post subject: |
|
|
Cpp1.ncb -> Intellisense Database (for dot autocompletion etc)
Cpp1.html -> HTML log of build in case you get errors
Cpp1.cpp -> your source code
Cpp1.dsp -> C++ Project
Cpp1.dsw -> Visual Studio project, you can add multiple dsps here
Cpp1.opt -> minimum rebuild file for faster compiles
Yes, you can set Visual Studio to delete certain files when you're done building, and it already has, but the files you just listed are very important.
_________________
|
|
| Back to top |
|
|
adamezra
Advanced Cheater
![]() Reputation: 0
Joined: 14 Feb 2007
Posts: 73
|
| Posted: Sun Oct 28, 2007 7:39 pm Post subject: |
|
|
so why did the other compiler just make source and .exe?
and what about the files in debug?
and i should keep them?... >.>
what is a project workspace? -.-
please this is confusing i need a more in depth explanation
_________________
...............................
.............................
............................
...........................
.........................
asagvsfdhg |
|
| Back to top |
|
|
appalsap
Moderator
Reputation: 0
Joined: 27 Apr 2006
Posts: 6753
Location: Pakistan
|
| Posted: Sun Oct 28, 2007 7:43 pm Post subject: |
|
|
| adamezra wrote: | | so why did the other compiler just make source and .exe? |
I very much doubt that, it probably created at least a few object files but cleaned them immediately afterwards.
| adamezra wrote: | | and what about the files in debug? |
The debug databases are only useful if you know how to use the visual studio debugger, if not, change the project options to Release.
| adamezra wrote: | | and i should keep them?... >.> |
Yes.
| adamezra wrote: | | what is a project workspace? -.- |
A file that keeps track of all the source files of a project. I know, it's shocking, but some projects are so big they need more than one source file!
| adamezra wrote: | | please this is confusing i need a more in depth explanation |
Visual Studio has its own help files if you need further explanation. Press F1.
_________________
|
|
| Back to top |
|
|
adamezra
Advanced Cheater
![]() Reputation: 0
Joined: 14 Feb 2007
Posts: 73
|
| Posted: Sun Oct 28, 2007 7:54 pm Post subject: |
|
|
so in order to keep track of whats what i gotta make a folder for ever source >.>
oh well thanks a lot for your time and help...
uhm wait one thing i didnt understand
how do i get rid of the debug files?
and what is debuging?...
_________________
...............................
.............................
............................
...........................
.........................
asagvsfdhg |
|
| Back to top |
|
|
appalsap
Moderator
Reputation: 0
Joined: 27 Apr 2006
Posts: 6753
Location: Pakistan
|
| Posted: Sun Oct 28, 2007 8:06 pm Post subject: |
|
|
| Description: |
|
| Filesize: |
3.2 KB |
| Viewed: |
5637 Time(s) |
|
_________________
|
|
| Back to top |
|
|
adamezra
Advanced Cheater
![]() Reputation: 0
Joined: 14 Feb 2007
Posts: 73
|
| Posted: Sun Oct 28, 2007 8:07 pm Post subject: |
|
|
Thank you i got all the help i need.
_________________
...............................
.............................
............................
...........................
.........................
asagvsfdhg |
|
| Back to top |
|
|
atom0s
Moderator
 Reputation: 205
Joined: 25 Jan 2006
Posts: 8587
Location: 127.0.0.1
|
| Posted: Mon Oct 29, 2007 4:19 am Post subject: |
|
|
| adamezra wrote: | so why did the other compiler just make source and .exe?
and what about the files in debug?
and i should keep them?... >.>
what is a project workspace? -.-
please this is confusing i need a more in depth explanation |
Just a quick toss-up, a lot of compilers are designed to compile and delete files that are only needed during compiling. Such as object files and so on. Reason why you don't see such things. The ncb file, as Appal pointed out is used for the intellisense engine in Visual Studio, other IDE/Compilers don't use the same setup which is why that file is not present on other IDE/Compilers.
The files spewed out from Debug are there for that exact purpose, for debugging. When you use the default debug compiler options in Visual Studio, it is setup to allow you to break and edit real time while debugging your application. Which some of those generated files are used for. Setting up a database to inform the compiler whats where and how to handle things when debugging. If you delete them you will probably get errors or 'unable to debug' messages if you attempt to debug without them. No they aren't crucial and yes, you can delete them if you don't plan on debugging.
But, you should always debug your application thoroughly before releasing it to the public to ensure there are no bugs that you can find through your own testing and such.
The project workspace is actually a pretty important thing. It's basically the spine of your project. It maintains keeping all the information that is your project. In stand-alone compilers, or command line compilers, you would use make files as your workspace to tell the compiler whats in your project and such, instead, the workspace file works the same way but from a visual aspect.
If you don't have the MSDN installed you can use the online version here:
http://msdn2.microsoft.com/en-us/default.aspx
_________________
- Retired. |
|
| Back to top |
|
|
adamezra
Advanced Cheater
![]() Reputation: 0
Joined: 14 Feb 2007
Posts: 73
|
| Posted: Mon Oct 29, 2007 1:03 pm Post subject: |
|
|
can u go more in depth about debuging please?
how do i debug?
what does it do?
_________________
...............................
.............................
............................
...........................
.........................
asagvsfdhg |
|
| Back to top |
|
|
Flyte
Peanuts!!!!
 Reputation: 6
Joined: 19 Apr 2006
Posts: 1887
Location: Canada
|
| Posted: Mon Oct 29, 2007 5:00 pm Post subject: |
|
|
| adamezra wrote: | can u go more in depth about debuging please?
how do i debug?
what does it do? |
To debug something is to view the ASM code of the program and monitor the registers/flags/stack of the program while it is running to make sure everything functions as it should. A common debugger that alot of people use is OllyDBG (it is free too).
|
|
| Back to top |
|
|
atom0s
Moderator
Reputation: 205
Joined: 25 Jan 2006
Posts: 8587
Location: 127.0.0.1
|
| Posted: Mon Oct 29, 2007 6:57 pm Post subject: |
|
|
| adamezra wrote: | can u go more in depth about debuging please?
how do i debug?
what does it do? |
Also with Visual Studio it has the ability to debug the code live, allow you to edit and continue if you use the compiler option, and such.
So when you have a basic code of something like..
| Code: | int main()
{
char szInputText[255];
cout << "Some sample output.." << endl;
cin >> szInputText;
cout << "You Entered: " << szInputText << endl;
return 0;
} |
Lets say the line
| Code: | | cout << "You Entered: " << szInputText << endl; |
Is crashing your application and you need to find out why. You can set a break point on that line and the line before it and find out whats happening to szIntputText before and after its filled with values.
Debugging is very useful when looking for whats causing bugs and glitches inside your program. Things that should have worked one why or have either not worked at all, errored, or are just working incorrectly all together.
_________________
- Retired. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
