File: PORTING

package info (click to toggle)
yuma123 2.11-1
  • links: PTS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 20,900 kB
  • sloc: ansic: 179,975; cpp: 10,968; python: 5,839; sh: 2,287; makefile: 1,021; xml: 621; exp: 592; perl: 70
file content (38 lines) | stat: -rw-r--r-- 1,644 bytes parent folder | download | duplicates (11)
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
The Tecla library was written with portability in mind, so no
modifications to the source code should be needed on UNIX or LINUX
platforms. The default compilation and linking arrangements should
also work unchanged on these systems, but if no specific configuration
has been provided for your system, shared libraries won't be compiled.
Configuring these requires modifications to be made to the file:

  configure.in

This file is heavily commented (comments start with the word dnl) and
is relatively simple, so the instructions and suggestions that you
find in this file should be sufficient to help you figure out how to
add a configuration for your system. This file is an input file to the
GNU autoconf program, which uses it as a template for generating the
distributed configure script. If autoconf is installed on your system,
creating a new configure script is a simple matter of typing.

  autoconf

To avoid confusion with the leftovers of the previous configuration,
you should then do the following:

 rm -f config.cache
 ./configure
 make clean
 ./configure
 make

The first ./configure creates a new makefile for your system, allowing
you to type 'make clean' to discard any files that were compiled with
the previous configuration. Since 'make clean' also deletes the new
makefile, a second invokation of the configure script is then
performed to re-create the makefile. The final make then creates the
tecla library from scratch.

Once you have confirmed that the new configuration works, please send
the modified "configure.in" template to mcs@astro.caltech.edu, so that
your changes can be included in subsequent releases.