Opened 15 years ago

Closed 15 years ago

#37 closed defect (fixed)

The Lisp based build system should be aligned with build.xml

Reported by: Mark Evenson Owned by: Mark Evenson
Priority: major Milestone: 0.14
Component: other Version: 1.0
Keywords: Cc:
Parent Tickets:


The Lisp based build system need some serious love to align with 'build.xml'.

This should be available for abcl-0.13.0

Change History (6)

comment:1 Changed 15 years ago by Mark Evenson

Comments from a post on armedbear-j-devel:

A) One has to copy the Lisp source over to the build/classes/org/armedbear/lisp directory as well for
the code in 'compile-system.lisp' to work correctly, making me worry
about platform dependent issues.

B) The JAR that results from the hosted-Lisp build is no longer
identical to the Ant build (it contains *.cls and *.abcl files, among
other difficulties)

C) Maintaining the two systems can be quite a chore (witness the recent
problem reported by Blake McBride? because the ABCL maintainers "forget"
to include the new org.armedbear.lisp.util classes in the hosted-Lisp build.

D) The hosted-lisp has a lot of platform dependent macros for a wide
variety of Lisp implementations. I can only really test with SBCL and
CLISP, so I was a little worried about breaking things that at least
work right now.

comment:2 Changed 15 years ago by Mark Evenson

Status: newaccepted

comment:3 Changed 15 years ago by ehuelsmann

With respect to point (A), this is no longer required as of r11676. If you build outside of the source tree, specify the abcl.home property (-Dabcl.home="some path") as a startup argument to the java process compiling ABCL. The property value will be used to find the lisp files required.

comment:4 Changed 15 years ago by ehuelsmann

With respect to point (C), I found out that the PatternSet? Ant task allows the specification of external pattern sources.

Both the Ant based build and the Lisp based build could use these sources, leading to a single source of maintenance, if well designed.

comment:5 Changed 15 years ago by ehuelsmann

Milestone: 0.130.14

As of r11681, the Lisp based build uses out-of-tree building on both *nix and Windows. This does not mean feature compatibility with the Ant build yet. Missing:

1) Verified the same output
2) Use of the same file patterns as described above w.r.t. point (C)
3) Lisp build system needs to use the same templates (make-jar, abcl, others?) as the Ant build

To name a few.

Moving this issue to 0.14 for full resolution.

comment:6 Changed 15 years ago by ehuelsmann

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.