Licensing Home

LCT Overview

LCT Installation

LCT Example

CCSC Paper

PN Home

LCT Installation Instructions

Download the tar file containing the tool and untar (tar -xvf lct030923.tar) it into a directory where you would like to store the executables. You may find it expedient to put all this code in a dedicated directory to avoid name conflicts.

Add this directory to your PATH and PERLLIB. The source contains the following perl library modules:

libSharedProc.pm
License.pm

and the following perl executables:

source/map_tracer/mapTracer.pl
source/postprocessor/Postprocessor.pl
source/preprocessor/Preprocessor.pl

cd to the directory in which you untarred the Licence Compliance Toolkit files.

Edit all .c files in the dummy directory:
Change LICOMPO.PL_PATH to the full path of the directory in which you untarred the Licence Compliance Toolkit files.

Install lidesc:
See www.mibsoftware.com/librock/lidesc/build.htm for instructions for obtaining and building lidesc.

Ensure that the lidesc executable is on your PATH.

Release notes:

  • licompr.pl considers source files to be files that have one of the following extensions: .h, .c, .cpp. Makefiles and other files used to build the sources are also source files, but are not included in the scan.
  • licompo.pl handles only GPL and LPGL, but could be very easily modified to handle any licenses in licompr's list of licenses.'
  • licompr and licompos' exit codes do not reflect whether or not lidesc had errors or found' license conflicts. You must inspect licompr's log file and licompo's standard output to determine these things.
  • When adding a license to licfile.txt, if the new license does not have a version number, enter V0 for the version and add this version number and the LIDESC short description in your source or copying file(s).
  • Relative paths in .d files (generated by relative paths in #include directives) can result in the same file being listed multiple times.
  • Run mapTracer.pl once for each executable or library you are releasing.
  • My apologies for the following:
    • The PERL code does not conform to the CPAN coding and distribution conventions.
    • We have done no stress testing of the code.

Please email Pete Nordquist if you have suggestions or corrections.