File: COMPILE.txt

package info (click to toggle)
saods9 3.0.3-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 86,868 kB
  • ctags: 82,021
  • sloc: ansic: 663,637; tcl: 111,403; cpp: 52,727; sh: 27,784; makefile: 6,177; asm: 3,355; lex: 2,890; ada: 1,637; pascal: 1,621; xml: 1,221; yacc: 883; f90: 84; perl: 82; python: 33; fortran: 17; ruby: 13; sed: 12; php: 11
file content (73 lines) | stat: -rw-r--r-- 3,201 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
                       HOW TO COMPILE THE TKHTML WIDGET

The TkHtml widget is written in C code.  But many of the C source code
files are automatically generated.  This makes the compilation more
complex that many people are used to.

The source code is contained in the directory where this file was found
and its subdirectories.  You should not compile in the source code directory.
Instead, compile in a parallel directory.  Like this:

    mkdir ../bld
    cd ../bld

All the build products will be placed in the "bld" directory which is a
sibling directory of the source code directory.

You will need a working installation of Tcl/Tk in order to compile.  If
you installation is not complex, and you are not trying to do anything
clever like cross-compile, then you should be able to compile as follows:

    ../htmlwidget/configure
    make

This above assumes that the name of the top-level directory containing
source code is "htmlwidget" and that you are building in a sibling directory
named "bld".

The configure script makes a valiant attempt to figure out how to compile
on your system.  It is successful many times.  But a lot of times you have
to give it some hints.

The most common problem that configure has is in locating appropriate
Tcl/Tk header files and libraries.  If you have compiled Tcl/Tk yourself,
you can point the configure script to the directories where you compiled
Tcl/Tk and the makefile will use libraries and header files found in
those directories.  Note that you do NOT have to install Tcl/Tk in order
for this to work.  You merely have to compile it.  Suppose I have
compiled Tcl in a directory named /home/drh/tcltk/tcl8.2 and I compiled
Tk in /home/drh/tcltk/tk8.2.  Then I might type:


   ../htmlwidget/configure --with-tcl=/home/drh/tcltk/tcl8.2 \
      --with-tk=/home/drh/tcltk/tk8.2
   make


If you are trying to do something really strange, like cross-compile,
you will probably need to give configure some specific hints about
the locations of compiles, linkers, libraries and so forth.  You can
do this with environment variables.  See the comment at the beginning
of the "configure.in" file for additional information.

Even if configure is not able to locate all the necessary libraries,
it will probably find enough information for you to type:

   make srcdir

The "srcdir" make target generates all of the C code and header files
and makes copies of them into the subdirectory named "srcdir".  Given
those source files, you should probably be able to concoct your own
build procedure that will do what you need.

The Makefile does not know how to build DLLs.  There is a script for
that purpose in the source directory.  (mkdll.sh).  The script works
as a cross-compiler using the Cygwin/Mingw32 compiler suite on a
Linux host.  It is setup for my particular machine.  You will probably
need to adjust some paths to get it to work at your site.

Note that that Makefile for TkHtml is generated by a tcl script.  The
configure script first collects information that will be needed and 
uses this information to construct "makemake.tcl" from "makemake.tcl.in".
Once "makemake.tcl" has been constructed, it is executed to generate
the Makefile.