aboutsummaryrefslogtreecommitdiffhomepage
path: root/scintilla.am
AgeCommit message (Collapse)AuthorFilesLines
2015-07-11fixed Scintilla/Scinterm build processRobin Haberkorn1-1/+1
the CURSES_CFLAGS variable from my patches has been renamed to CURSES_FLAGS in the upstream commits, so this was broken in SciTECO since 3770ea2e
2015-06-22added XCurses supportRobin Haberkorn1-1/+1
* enabled via --with-interface=xcurses, so we can configure it automatically via xcurses-config. This also adds XCURSES_CFLAGS and XCURSES_LIBS. * The X11 window class name is set to "SciTECO". X11 resource overrides can currently not be set via sciteco's command line. The user may use .Xdefaults though. * interruptions via CTRL+C are currently not supported. Apparently, XCurses also does send SIGINT in cbreak() mode. An XCurses-specific hack would be cumbersome. * ~InterfaceCurses() should probably be rewritten. Curses cleanup should be completely in restore_batch() as the destructor may be called after Curses-cleanup handlers. E.g. isendwin() SEGFAULTs on XCurses when called from the destructor.
2015-06-22pass curses CFLAGS into Scinterm build systemRobin Haberkorn1-7/+11
* requires a recent patch to Scinterm * can be overwritten in SciTECO's build system via NCURSES_CFLAGS or PDCURSES_CFLAGS. * NCURSES_LIBS has also been introduced. The check for ncurses will now use pkg-config if available. * eases multiple builds with different Curses variants (e.g. when cross-compiling for Windows) * pass more toolchain variables into Scintilla build process (CC and RANLIB). This should fix Cross-compiling Scintilla/Gtk * Pass GTK cflags into Scintilla/Gtk build system.
2015-06-17improved build speed by refining the rules for building ScintillaRobin Haberkorn1-7/+16
* Scintilla was built as a .PHONY target, so we trigger its build process always when we depend on scintilla.a. The problem was that a real file (scintilla.a) was declared .PHONY which meant that it was always considered updated by Make. This triggered a relink of everything depending on scintilla.a. Always. When doing a bootstrap build, this would always result in rebuilding the symbols-*.cpp files, etc... * Now the Scintilla build process will always be triggered, but scintilla.a is handled like an ordinary target. When we depend on scintilla.a our recipe will only be executed if the recursive make for Scintilla actually did update scintilla.a
2015-03-02define scintilla.a as a phony targetRobin Haberkorn1-1/+6
when hacking Scintilla, it is useful to recompile it as necessary. Since SciTECO calls the Scintilla/Scinterm Makefile recursively, we do not know the libraries dependencies in SciTECO's build system. It therefore makes sense to define externally built targets as phony, so the recursive make is called every time scintilla.a is required. If scintilla.a is already up to date, the additional recursive make call won't hurt.
2014-08-22automatically build Scintilla as part of SciTECO's build system:Robin Haberkorn1-0/+22
this should simplify building SciTECO for new users * compiler and archiver are passed down from Autoconf, so cross-compiling should work transparently * `make clean` will also clean the Scintilla source tree * there is no longer any need for "source bundles" as tar balls also contain Scintilla/Scinterm now * building from Git is not much more difficult than building from a tar ball * The versions of Scintilla/Scinterm embedded as submodules already contain all the patches necessary (currently none are necessary), so there's no need to have patch files in the repository * INSTALL instructions have been rewritten * the --with-scintilla and --with-scinterm site-config options have been kept. But they should be rarely necessary now.