Toolkit Pro - Performance issue with the MFC Toolkit

Print Page | Close Window

Performance issue with the MFC Toolkit

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=12444
Printed Date: 21 May 2024 at 2:22pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Performance issue with the MFC Toolkit

Posted By: FrankC
Subject: Performance issue with the MFC Toolkit
Date Posted: 15 October 2008 at 11:48am

I am using the version 12.0.2 Toolkit Pro C++ MFC on the Visual Studio 6.0 to add the new face to our old application. Out application links the libraries with the static method.

Before the Toolkit Pro, a complete compilation of our application takes about 12 minutes, after adding the new face just to the new toolbars, the compilation takes about 22 minutes, 83% more time is been used.

I understand that by using the Tookkit Pro, the compiler has to access more libraries, but 83% more of time seems that there is a room to be improved.

Any clues of this performance issue?

Thanks,

Frank

Replies:

Posted By: ABuenger
Date Posted: 15 October 2008 at 6:08pm

Are you using precompiled headers? You should only include XTToolkitPro.h in your StdAfx.h

How often do you get the "automatically linking to..." message?

-------------
Codejock support

Posted By: Oleg
Date Posted: 16 October 2008 at 4:30am

Hi,

Yes, check that you see only one automatically linking to..." message

also exclude some modules you don't use:

before include toolkit add

#define _XTP_EXCLUDE_CALENDAR
#define _XTP_EXCLUDE_SYNTAXEDIT
#define _XTP_EXCLUDE_REPORTCONTROL

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: FrankC
Date Posted: 16 October 2008 at 11:53am

Yes, I moved the include XTToolkitPro.h from the individual files to stdafx.h and getting less "automatically linking to..." messages.

Is it supposed to get only one such message when compiling the stdafx.cpp and not from compiling other source code?

Thanks,

Frank