Skip to content
  1. Jan 31, 2013
  2. Jul 24, 2012
  3. Nov 05, 2011
  4. Sep 26, 2011
  5. Jun 15, 2011
  6. Jun 09, 2011
  7. Jun 08, 2011
  8. Jun 01, 2011
    • Peter Keller's avatar
      Implementing real executable targets. · 08f1523b
      Peter Keller authored
      + Partial changes to get xcvb to build a binary of xcvb.
      + Extending :create-image to support executables.
      + Support for command line arguments when resuming the executable.
        These are passed to the entry-point. However, each lisp vendor
        mangles the argv a little and it needs work to be really right.
        For now it is good enough.
      + dump-image for ecl got hacked upon, but it is currently broken.
      + Changed example-1 to produce an executable, but currently this
        only works for lisp implementations which can produce them. This
        needs more consideration in the future, for example, the
        "executable" could be a script which invokes an image.
      + simple-build can now accept targets with empty computations.
        This implements the "phony target" idea in simple-build.
      08f1523b
  9. May 30, 2011
  10. May 27, 2011
    • Francois-Rene Rideau's avatar
      working toward a release: · 024d95bf
      Francois-Rene Rideau authored
      * extract fasl type from target:
       at least lispworks depends on pathname type and its fasl type varies!
      * rucksack not available on clisp (and needed fixes; see our xcvb repo of it)
      * accept compile-file failure semantics of clisp
      * suppress duplicate entries for a directory in the source-registry:
       The first one wins, with its recurse and exclude flags.
      * fix hello and test/runme
      * fix various option parsing mistakes
      024d95bf
  11. May 18, 2011
  12. Apr 13, 2011
  13. May 20, 2010
  14. May 07, 2010
  15. May 06, 2010
  16. Apr 28, 2010
    • Francois-Rene Rideau's avatar
      .508: · 23b12721
      Francois-Rene Rideau authored
      * fix various bugs left over from .507.
      * back out generation of Lisp files in object tree
       until we can provide build processes with a mapping from name to pathname.
      * pass self-test.
      23b12721
    • Francois-Rene Rideau's avatar
      .507: small fixes · b8f2b2a1
      Francois-Rene Rideau authored
      * cfasl support: *use-cfasls*, not *has-cfasls*.
      * Normalize lisp module names to (:lisp ...).
      * Validate names of grains.
      * Tweak parse-module-declaration signature.
      * Generated files go in object directory, not source!
      b8f2b2a1
  17. Apr 15, 2010
  18. Apr 14, 2010
  19. Apr 03, 2010
  20. Apr 02, 2010
  21. Mar 24, 2010
  22. Mar 17, 2010
  23. Dec 02, 2009
  24. Nov 24, 2009
  25. Nov 11, 2009
  26. Nov 08, 2009
    • Francois-Rene Rideau's avatar
      XCVB .421: now with an example and a test suite · 69835e41
      Francois-Rene Rideau authored
      * Fix output-path defaulting in asdf backend.
      * Trivial refactorings in driver, alias rmx for remove-xcvb,
      * Created XCVB hello, an example CL application using XCVB.
      * Trivial test a2x-test for a2x and rmx
      * Created a test suite -- itself still mostly untested.
      * new checking function (still unused) in names
      * More TODO items.
      69835e41
  27. Oct 25, 2009
  28. Oct 23, 2009
  29. Aug 22, 2009
  30. Aug 20, 2009
  31. Aug 19, 2009
    • Joyce Chen's avatar
      Update asdf-to-xcvb to call ADG's fine-grain-instrumented-load. · 85a7d660
      Joyce Chen authored
      Because many run-time forward-references in QRES cause ADG to believe there are circular dependencies, we use the order of components in ASDF file to remove forward-references.
      Using the ASDF file to remove run-time forward-reference dependencies is cheating a little.
      
      TODO:
      Because QRES uses modules with relative pathnames, I've currently relaxed the restriction that XCVB component paths be absolute.
      We should clean up relative pathnames sometime; currently XCVB will print "core/../messaging/" for component pathnames
      
      I currently use a list-lookup instead of a hash-lookup for checking for forward-references.  We should replace the list-lookup with a hash-lookup
      85a7d660
  32. Jul 08, 2009
    • Francois-Rene Rideau's avatar
    • Francois-Rene Rideau's avatar
      XCVB 0.315: fix pre-image & make it optional. · 6e959561
      Francois-Rene Rideau authored
      Simpler and more robust Makefile.
      Updated TODO.
      
      Timings on my dual-core box:
      Compiling XCVB 0.315 using ASDF, from clean fasl cache:
      make xcvb  12.44s user 1.64s system 95% cpu 14.703 total
      
      Compiling XCVB 0.315 using XCVB 0.315, from clean obj cache, no pre-image:
      make xcvb-bootstrapped  22.53s user 4.84s system 116% cpu 23.413 total
      
      Compiling XCVB 0.315 using XCVB 0.315, from clean obj cache, with pre-image for XCVB:
      make xcvb-bootstrapped  16.22s user 5.29s system 112% cpu 19.087 total
      6e959561
  33. Jun 23, 2009
    • Joyce Chen's avatar
      Add support for generated Lisp source files in XCVB. · a4fa2df4
      Joyce Chen authored
      Support for generated code was added by extending
      the "extension-forms" of Lisp grains.
      
      Example declaration of the "generate" Lisp grain extension form (from cl-unicode):
       (:generate
        ((:gen-lisp "lists"
      	      :depends-on ("conditions" "util" "specials" "packages"))
         (:gen-lisp "hash-tables"
      	      :depends-on ("lists"))
         (:gen-lisp "methods"
      	      :depends-on ("api" "hash-tables")))
        :generate-depends-on ("build/dump"))
      
      Here, "lists", "hash-tables", and "methods" are files that are
      generated by loading "build/dump" Each (:gen-lisp ...)  is like
      a (module ...) and is parsed as such.  The dependencies of the
      generated files (lists, hashtables, and methods) are keyed
      as :depends-on, just like in a module.
      
      Each :gen-lisp is parsed into a Lisp grain and stored in a
      hashtable mapping the fullname of the :gen-lisp file to its grain
      and generation dependencies.
      
      Tested support for generated code by generating the make file for
      cl-unicode, then building cl-unicode with the generated
      cl-unicode-xcvb.mk make file.
      
      Example of make command for generated files:
      hash-tables.lisp: lists.lisp
      methods.lisp: lists.lisp
      lists.lisp: obj/cl-unicode/packages.fasl obj/cl-unicode/specials.fasl obj/cl-unicode/util.fasl obj/cl-unicode/build/util.fasl obj/cl-unicode/build/char-info.fasl obj/cl-unicode/build/read.fasl obj/cl-unicode/build/dump.fasl ${XCVB_EOD}
      	./obj/_pre/cl-unicode.image --noinform --userinit /dev/null --disable-debugger --eval "(xcvb-driver:run (:load-file \"obj/cl-unicode/packages.fasl\")(:load-file \"obj/cl-unicode/specials.fasl\")(:load-file \"obj/cl-unicode/util.fasl\")(:load-file \"obj/cl-unicode/build/util.fasl\")(:load-file \"obj/cl-unicode/build/char-info.fasl\")(:load-file \"obj/cl-unicode/build/read.fasl\")(:load-file \"obj/cl-unicode/build/dump.fasl\"))"
      a4fa2df4
  34. Jun 09, 2009
    • Joyce Chen's avatar
      XCVB 0.306: got it to compile itself! · 159ae0bb
      Joyce Chen authored
      * ensure installation directories exist
      * add module forms to every file
      * fix nickname registration
      * add an eval-when for compile-time functions
      * add support for xcvb.mk in the main Makefile
      * trivially tested the result
      159ae0bb