[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: 2.6.8 ....

From: Gabriel Dos Reis
Subject: [Gcl-devel] Re: 2.6.8 ....
Date: Thu, 04 Nov 2010 13:46:06 -0500

Camm Maguire <address@hidden> writes:


| > [...]
| >
| > | Corrections/additions to this table most welcome.  We should probably
| > | include similar in the release notes and on the web page.
| >
| > One question: does compiler::*default-system-p* still control whether
| > the built GCL uses a copy of its C header file from its image or from
| > its system directory?  It is extremely convenient to be able to use GCL,
| > `built on the fly as part of building AXIOM' without having to install it
| > permanently on the target system.
| >
| In essence, yes.  The :system-p flag to compile-file, which defaults
| to compiler::*default-system-p*, has two effects on the C output:
| 1) The .data file appended to the .o file is written in verbose
| legible lisp, as opposed to the byte compiled 'fasl' form
| 2) The cmpinclude.h header contents, normally written at the head of
| the .c file, is replaced with #include "cmpinclude.h".  A -I is
| appended to the gcc command to point to the ../h dir relative to the
| current setting of si::*system-directory*, which should point to the
| location of the binary.  There are a few other paths which key off of
| this one, so best to (reset-sys-paths ...) when moving the compiled
| tree or installing.

Thank you very much!

-- Gaby

reply via email to

[Prev in Thread] Current Thread [Next in Thread]