racket/collects/setup/setup.ss

111 lines
4.3 KiB
Scheme

;; Because Setup PLT is used to rebuild .zos, we may need to turn off
;; the use of compiled code or install cm before we do anything. This
;; startup stub parses the command line and either disables .zos or
;; installs cm for loading Setup PLT.
;; Note that this file is listed in "info.ss" so that it never gets a
;; .zo file. Do not `require' this module from anywhere, otherwise it
;; could get a .zo anyway.
(module setup mzscheme
(when (file-stream-port? (current-output-port))
(file-stream-buffer-mode (current-output-port) 'line))
(define-values (flags specific-collections specific-planet-packages archives)
;; Load the command-line parser without using .zos,
;; and in its own namespace to avoid poluuting the cm-managed
;; namespace later
(parameterize ([use-compiled-file-paths null]
[current-namespace (make-namespace)])
((dynamic-require '(lib "setup-cmdline.ss" "setup") 'parse-cmdline)
(current-command-line-arguments))))
;; Checks whether a flag is present:
(define (on? flag-name not)
(let ([a (assq flag-name flags)])
(and a (not (cadr a)))))
(define (print-bootstrapping)
(fprintf (current-error-port) "setup-plt: bootstrapping from source...\n"))
(if (or (on? 'clean values)
(on? 'make-zo not))
;; Don't use .zos, in case they're out of date, and don't load
;; cm:
(when (on? 'clean values)
(use-compiled-file-paths null)
(print-bootstrapping))
;; Load the cm instance to be installed while loading Setup PLT.
;; This has to be dynamic, so we get a chance to turn off compiled
;; file loading, and so it can be in a separate namespace.
(let-values ([(mk trust-zos)
;; Load cm.ss into its own namespace, so that cm compiles
;; itself and its required modules in the right order
;; (i.e., when some module requires cm or one of its
;; required modules)
;; Since cm.ss pulls in quite a lot of code itself, we
;; would like to load using .zo files. But if we discover
;; any date mismatch in the loading process, abort and
;; try again without .zo files. If .zo files are newer
;; than .ss files but a required file is newer than its
;; requring file, we won't notice, but that
;; shouldn't happen for a reaonsbaly maintained
;; tree, and there's always --clean to turn this
;; off. If an .so file is used, we give up using
;; compiled files.
(let loop ([skip-zo? (null? (use-compiled-file-paths))])
(when skip-zo?
(print-bootstrapping))
((let/ec escape
;; Create a new namespace, and also install load handlers
;; to check file dates, if necessary.
(parameterize ([current-namespace (make-namespace)]
[use-compiled-file-paths
(if skip-zo?
null
(use-compiled-file-paths))]
[current-load
(let ([orig-load (current-load)])
(if skip-zo?
orig-load
(lambda (path modname)
(if (regexp-match #rx#"[.]zo$" (path->bytes path))
;; It's a .zo:
(orig-load path modname)
;; Not a .zo! Don't use .zo files at all...
(escape (lambda ()
;; Try again without .zo
(loop #t)))))))]
[current-load-extension
(if skip-zo?
(current-load-extension)
(lambda (path modname)
(escape (lambda ()
;; Try again without .zo
(loop #t)))))])
;; Other things could go wrong, such as a version mismatch.
;; If something goes wrong, of course, give up on .zo files.
(with-handlers ([exn:fail? (lambda (exn)
(if skip-zo?
(raise exn)
(escape
(lambda () (loop #t)))))])
;; Here's the main dynamic load of "cm.ss":
(let ([mk
(dynamic-require '(lib "cm.ss")
'make-compilation-manager-load/use-compiled-handler)]
[trust-zos
(dynamic-require '(lib "cm.ss") 'trust-existing-zos)])
;; Return the two extracted functions:
(lambda () (values mk trust-zos))))))))])
(when (on? 'trust-existing-zos values)
(trust-zos #t))
(current-load/use-compiled (mk))))
;; This has to be dynamic, so we get a chance to turn off
;; .zo use and turn on the compilation manager.
(dynamic-require '(lib "setup-go.ss" "setup") #f))