• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

DepGen.pyH A D10-Apr-20201.3 KiB4021

Lexilla.cxxH A D10-Apr-202010.8 KiB339303

Lexilla.hH A D10-Apr-2020351 143

LexillaVersion.rcH A D10-Apr-20201 KiB3834

READMEH A D10-Apr-20201.5 KiB4330

deps.makH A D10-Apr-202041.3 KiB1,5201,519

lexilla.makH A D10-Apr-20205.4 KiB225199

makefileH A D10-Apr-20202.8 KiB12680

nmdeps.makH A D10-Apr-202042.6 KiB1,5201,519

README

1README for Lexilla library.
2
3The Lexilla library contains a set of lexers and folders that provides support for
4programming, mark-up, and data languages for the Scintilla source code editing
5component.
6
7Lexilla is made available as both a shared library and static library.
8The shared library is called lexilla.so / lexilla.dylib / lexilla.dll on Linux / macOS /
9Windows.
10The static library is called liblexilla.a when built with GCC or Clang and liblexilla.lib
11when built with MSVC.
12
13Lexilla is developed on Windows, Linux, and macOS and requires a C++17 compiler.
14It may work on other Unix platforms like BSD but that is not a development focus.
15MSVC 2019.4, GCC 9.0, Clang 9.0, and Apple Clang 11.0 are known to work.
16
17MSVC is only available on Windows.
18
19GCC and Clang work on Windows and Linux.
20
21On macOS, only Apple Clang is available.
22
23To use GCC, run lexilla/src/makefile:
24	make
25
26To use Clang, run lexilla/test/makefile:
27	make CLANG=1
28On macOS, CLANG is set automatically so this can just be
29	make
30
31To use MSVC, run lexilla/test/lexilla.mak:
32	nmake -f lexilla.mak
33
34To build a debugging version of the library, add DEBUG=1 to the command:
35	make DEBUG=1
36
37The built libraries are copied into scintilla/bin.
38
39Lexilla relies on a list of lexers from the scintilla/lexers directory. If any changes are
40made to the set of lexers then source and build files can be regenerated with the
41lexilla/scripts/LexillaGen.py script which requires Python 3 and is tested with 3.7+.
42	python LexillaGen.py
43