Menu

#96 VS.NET 2003 Compiler Errors - Solved

Bug
closed-fixed
Scintilla (812)
5
2003-10-21
2003-05-18
Anonymous
No

For Anybody wishing to Develop this on Vs.NET 2003
this is what I had to do (with the 1.53 build off of
SourceForge)

open up the \vcbuild Directory after Successfully
Extracing the Files to your Directory. Double click on
the .mak File. Select Yes to all of Conversion Warnings.
Go to your Solution Explorer-> Expand the Project ->
Expand your Source Files. Apparently
the "ExternalLexxer.cxx" file showed up in the \win32\
directory. You can see if this happens to you by clicking
on the file and then looking at its property sheet.
the "Relative directory" should look like .\src\..... If it
says .\win32\..... then click on the file and Delete it and
then go to your Explorer and navigate down the \src
directory. Find the File and drag it into your Solution
Explorer and drop it.
Recompile the Program.
You will probably get 2 or 3 Link errors like:
SciLexer error LNK2001: unresolved external
symbol "class LexerModule lmESCRIPT" (?
lmESCRIPT@@3VLexerModule@@A)
SciLexer error LNK2001: unresolved external
symbol "class LexerModule lmLout" (?
lmLout@@3VLexerModule@@A)
SciLexer fatal error LNK1120: 2 unresolved externals

If you get these Errors open up "KeyWords.cxx" and
comment out any LINK_LEXXER(...) line that has the
missing thing.
Example above we note that we are missing
lmESCRIPT and lmLout. So we find the lines with those
in it and put a // in front of it.
An Alternative would be going online and grabbing the
source files for those 2 languages and adding them to
your src directory and to your project and recompiling.

With that the Scintilla Part should work just fine

Discussion

  • Neil Hodgson

    Neil Hodgson - 2003-07-20
    • labels: --> Scintilla
    • milestone: --> Bug
    • assigned_to: nobody --> nyamatongwe
     
  • Neil Hodgson

    Neil Hodgson - 2003-10-21
    • status: open --> closed-fixed
     

Log in to post a comment.