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
  
Glad you found this file :) 
 
After checking out the files from CVS you will notice that some files 
are missing compared to a regular distribution... To bootstrap your 
Pike development environment you must do the following steps: 
 
1) cd src ; ./run_autoconfig 
        This creates configure files and Makefile.in files. 
 
2) Create a build directory an cd to it 
        Do NOT build in the source dir, doing so will make it impossible 
        to do 'make export' later. 
 
3) Run the newly created configure file located in the src dir from the 
   build dir. Make sure to use an absolute path! 
        This creates the Makefiles you need. 
        If you don't use an absolute path the debug information will 
        be all warped... 
 
4) 'make depend' 
        This updates all the Makefile.in files in the source dir to 
        contain the correct dependencies 
 
5) run configure again 
        This updates your Makefiles to include the dependencies. 
        The config.cache file will make this a lot faster. 
 
6) If needed, modify your Makefile 
 
7) 'make' 
        This builds pike. 
 
8) 'make new_peep_engine' 
        This creates the peephole optimizer 
 
9) 'make' 
        This builds a new pike with the peephole optimizer 
 
After doing this, DO NOT, commit the generated files. They are placed in 
.cvsignore files so you shouldn't have to bother with them. 
Doing 'make export' will create a tar file with all the needed files, 
but they should NOT be in the CVS archive! 
 
        /Fredrik Hubinette