Release dll

[phungus420]

So I've found that having a debug dll is useful, but only really for the asserts, I never debug stuff, whenever I try it gets me no where, at least no farther then the assert itself does. Also I need to give out a debug dll to achilleszero as it helps alot with checking art and such. But I don't really see the point in using a debug dll. All I want is the asserts, can't I just use a release dll for this? If so, what do I need to do to the makefile so that I can create a release dll?

 

[xienwolf]

most people's Makefile only contains information for a Final Release and a Debug version of builds. You would want to clone the Debug information and rename it to Release (basically, just search for Debug, and everywhere you find one, copy that entire line, then go through it and change any Debug to a Release).

Once you have cloned debug, then change the flags to remove whatever it is you don't want from the debug DLL. Honestly though I can only think that you are seeking to reduce the size of the DLL, and it is enabling the Asserts which added the size to it in the first place, so I doubt that you will notice any difference in any other manner (Far as I can recall, debug only enables the Asserts and the Profiler, otherwise it is the same as the Final Release, so the only gain from creating a Release build would be to disable the profiler while still enabling the Asserts, which is exactly backwards of what Release normally is used for (ie - normally it is used to disable the asserts, but retain the profiler for final checking of performance). I haven't done "pro" work though, so I can't say for certain)

 

[phungus420]

Ah, I thought there was a whole bunch of extra junk so that the debug dll could attach to process to MSV and "debug", which I can't use, or haven't been able to use to any effect anyway. I figured that doing a release version would drop the need for the pdb as well, which would save alot of space (the pdb is like 70Megs). I've just read a few times that a release dll is a final release with asserts, and that's all I need, don't need no fancy attaching to process or profilers or any of that other jazz. At the end of the day though, it really doesn't matter, just was wondering if I could simplify things for myself any.

 

[randomproof]

If you just want the asserts in you release build just define FASSERT_ENABLE. At the top of FAssert.h you'll see

#ifdef _DEBUG
#define FASSERT_ENABLE
#endif

change it to:

//#ifdef _DEBUG
#define FASSERT_ENABLE
//#endif

 

[xienwolf]

There may be something special about the debug to allow attachment, but you don't have to distribute anything except the .dll itself for people to utilize a debug DLL.

 

[davidlallen]

Also I need to give out a debug dll to achilleszero as it helps alot with checking art and such.

I am curious to know how a debug build helps with checking art. Are there things missing from civcheck which I could add?