Sign in to follow this  
Followers 0
phil67rpg

release code

4 posts in this topic

It works on your system. A debug build (usually) binds to debug libraries which not only will be slower due to run-time checks but rarely be available on a user system (Edit: for late binding). Have a look at what DLLs your exe loads with e.g. Process Explorer. Debug DLLs usually end with a 'd'. (Sure you could provide an installer, but that's not something you wanna do normally).

Edited by unbird
3

Share this post


Link to post
Share on other sites


Why I can't just go with debug result? I get .exe file and program works...

 

The debug build contains a lot of extra code used for debug purposes (such as bounds checking and other possible errors). The release build is highly optimized and does not contain this extra code, making it run significantly faster than a debug build.

1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0