Command Line File Handling and ASCII Tools

Compiling Glindra From Source

Required Components

To compile the Glindra source code, you need the following components installed:

The gcc compiler and tool chain
The MinGW/MSYS libraries on Windows (not required on Linux)
The Boost C++ Library (version 1.33, earlier versions no longer supported). Used for various header files, file handling primtives, and for the regex package.

Please consult the documentation for the respective package for instructions on how to download and install each of them.

As of version 0.2.1, the Glindra programs no longer use the wxWidgets C++ Library. Earlier versions used the basic file handling functions from wxWidgets, but now the Boost file handling library is used instead.

Building Glindra Under Windows

The build Directory

Assuming that the glindra top directory was placed in e:\, the directory e:\glindra\win32\build\ contains the follwing files:

Directory of e:\glindra\win32\build\

         360   build_all.bat
         620   build_main.bat
         311   build_sub.bat
          40   cleanup.bat
          26   install.bat
  ----------
        2 kb   total, 5 files

Go to this directory to build Glindra from source.

Editing The Batch Files

The batch files included in the distribution assume that the Glindra top directory is e:\glindra, and that various other files can be found in certain specific places.

You will probably have chosen other directories during installation, so you'll have to edit the batch files build_sub and build_main before you can run them. (build_all does not have to be edited, as it just calls the other batch files.)

build_sub.bat and build_main.bat use the following filenames:

Include files
c:\app\Boost\include\
e:\glindra\src\
Object libraries
c:\app\Boost\lib\
e:\glindra\win32\build\
The Glindra library is created by the build_all / build_sub batch file, so it does not have to exist beforehand. The name has to be correct in the batch file, though.
Object file
c:\app\mingw\lib\CRT_noglob.o
This file needs to be linked into the binaries as the first object file, in order to suppress Unix-style "globbing" of the command line arguments.

Edit build_sub.bat and build_main.bat so that they reflect the actual locations of these directories.

Building And Installing

After editing the batch files, you just type

> build_all

This will build the libglindra.a library and the executables, and leave them in the build\ directory.

To copy them to the e:\glindra\bin\ directory, type

> install

After you have done this, you can type

> cleanup

to delete the temporary files, the binaries, and the Glindra object library from the build\ directory.

Building Glindra Under Linux

The build Directory

Assuming that the glindra top directory was placed in /home/chris/, the directory /home/chris/glindra/linux/build/ contains the follwing files:

Directory of /home/chris/glindra/linux/build/

         457   build_all.sh
         461   build_main.sh
         287   build_sub.sh
          25   cleanup.sh
          53   install.sh
  ----------
        2 kb   total, 5 files

Go to this directory to build Glindra from source.

Editing The Batch Files

The batch files included in the distribution assume that the Glindra top directory is /home/chris/glindra, and that various other files can be found in certain specific places.

build_sub.bat and build_main.bat use the following filenames:

Include files
/usr/local/include/boost
/home/chris/glindra/src/
Object libraries
/usr/local/lib/libboost_regex-gcc.a
/usr/local/lib/-lboost_filesystem-gcc.a
/home/chris/glindra/linux/build/libglindra.a
The Glindra library is created by the build_all / build_sub batch file, so it does not have to exist beforehand. The name has to be correct in the batch file, though.

Edit build_sub.bat and build_main.bat so that they reflect the actual locations of these directories.

Building And Installing

After editing the batch files, you just type

> build_all.sh

This will build the libglindra.a library and the executables, and leave them in the build/ directory.

To move them to the /home/chris/glindra/bin/ directory, type

> install.sh

After you have done this, you can type

> cleanup.sh

to delete the temporary files and the Glindra object library from the build/ directory.