![]() |
complile warnings & errors |
Post Reply
|
| Author | |
securigy
Groupie
Joined: 23 November 2007 Status: Offline Points: 41 |
Post Options
Thanks(0)
Quote Reply
Topic: complile warnings & errorsPosted: 11 December 2007 at 2:33pm |
|
I am migrating from v8.6 to v11.2.1 and getting compile warnings (very long ones) like this:
Generating Code...
Automatically linking with ToolkitPro1121vc60D.dll C:\Program Files\Microsoft Visual Studio\VC98\MFC\INCLUDE\afx.h(969) : warning C4786: 'XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexObj_SpecCollT<XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexVariantPtrArrayExAutomatT<&XTPSyntaxEditLexAnalyser::FnName_en d_class>,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexVariantPtrArrayExAutomatT<&XTPSyntaxEditLexAnalyser::FnName_end_tag>,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexVariantPtrArrayExAutomatT<&XTPSyntaxEditLexAnalyser::FnName_end_separators>,XTPSyntax EditLexAnalyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAn alyser::CXTPSyntaxEditLexNULL,XTPSyntaxEditLexAnalyser::CXTPSyntaxEditLexNULL>' : identifier was truncated to '255' characters in the debug information any ideas?
I also get compile error:
LINK : fatal error LNK1104: cannot open file "..\CodejockSoftware\CodeJock_XTremeToolkitPro_v11_2_1\Xtreme.obj"
I search for Xtreme.obj throuout all the tree but cannot find any...
|
|
![]() |
|
Oleg
Senior Member
Joined: 21 May 2003 Location: United States Status: Offline Points: 11234 |
Post Options
Thanks(0)
Quote Reply
Posted: 11 December 2007 at 3:34pm |
|
Hm.
strange errors. toolkit don't create Xtreme.obj . Maybe you manaully add some such file to project ?
|
|
|
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS |
|
![]() |
|
securigy
Groupie
Joined: 23 November 2007 Status: Offline Points: 41 |
Post Options
Thanks(0)
Quote Reply
Posted: 11 December 2007 at 5:06pm |
|
the compile error was resolved: the initial/original path of the toolkit installation has spaces... ;-) so, when you copy and paste the path of the library for the linker it should be enclosed in parenthasis...
|
|
![]() |
|
Post Reply
|
|
|
Tweet
|
| Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |