Hello.

When compiling my projects (both Win32 Static Library projects and MFC Application projects) every file is automatically linked with the XTP Toolkit library when compiled. Is this necessary - the compilation time is extremely high when using the XTP Toolkit.

PS: I have to use the XTP Toolkit static library - and not the DLL! 

RedirNumRes.cpp
Automatically linking with XTP8700LibStaticd.lib
scriptopencreate.cpp
Automatically linking with XTP8700LibStaticd.lib
ScriptPackageDlg.cpp
Automatically linking with XTP8700LibStaticd.lib
ScriptPackageInfo.cpp
Automatically linking with XTP8700LibStaticd.lib

Best regards,
Frode Gorseth

Hello.

The following are included in StdAfx.h:
#define _XTP_STATICLINK
#pragma pack(push, 8)
#include <XTToolkitPro.h>
#pragma pack(pop)

Project Settings:
"Use MFC in a Static Library"

rc2 file:
#include <XTToolkitPro.rc>

BR,
Frode.

Is there any other ways to avoid each file to be automatically linked with the Codejock libary - what about using dynamic linking (linking to the Codejock DLL instead of the LIB)?

We are using 1 Byte struct member alignment in our project setting - while the Codejock libraries are using 8 Bytes struct member alignment. For this reason we are using "pragma" as seen above.

I also found the slow down of compilation a pain. Over 100 files and only a dozen or so needed XTP. I removed XTToolkitPro.h from the StdAfx.h and added it to all files that actually need it.

This sped up compilation for the project as a whole even though it slowed down the compilation files that use XTP.