axiom-developer
[Top][All Lists]
Advanced

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

Re: [Axiom-developer] Re: [build-improvements] make clean and xgcl


From: Gabriel Dos Reis
Subject: Re: [Axiom-developer] Re: [build-improvements] make clean and xgcl
Date: 29 Aug 2006 23:28:17 -0500

Vanuxem Grégory <address@hidden> writes:

| Le mardi 29 août 2006 à 10:01 -0500, Gabriel Dos Reis a écrit : 
| > Vanuxem Grégory <address@hidden> writes:
| > 
| > | Hello Gaby,
| > | 
| > | I tested the build-improvements branch and if we build gcl the XLIB
| > | (xgcl) package is compiled in (gcl and AXIOMsys are thus linked against
| > | the X libraries). Don't know what you think about this, it's just a
| > | remark.
| > 
| > Ah, I have no particular idea about which direction to go here.  What
| > would be your recommendation?
| 
| Personally I think that if we don't use a package we can remove it. So
| for gcl it can be removed from the lisp image and added later if
| necessary. In fact there is also the TK package that Axiom doesn't use
| but I don't know if and how it is possible to remove it.

I see.  I havw a working patch that builds GCL-2.6.8pre with
--disable-xgcl.  I came to it when solving the other GCL issue I
mentioned earlier today.  

[...]

| > But, please, list your priority about the build machinery.
| 
| I haven't no priority at all for this branch, it's not the silver
| branch, it's a work in progress branch (as silver you can say). So if
| there are some problems that will be fixed later because some
| preliminary work has to be done it's not a problem. But what about
| adding a file, say README.build-improvement, that quickly explain how to
| build Axiom and lists the known issues, the workarounds and why not the
| TODO (it can refer to the "gold" README for more information about
| Axiom).

that is a very good suggestion.  Thanks!

-- Gaby




reply via email to

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