ASDF不会加载通用的LISP文件



我目前正在共同的LISP中构建一个项目,并且正在使用ASDF。但是,我遇到了一些困难。也就是说,当我运行asdf:compile-system时,它似乎会编译。然后,我可以成功地进行asdf:load-system。但是,某些文件中的某些功能仍然不确定。为了使它们知道,我必须手动导航到该文件并编译。

这是系统的声明。有人可以告诉我我在做什么吗?

(defsystem "xxx-xxxx"
  :version "0.1.0"
  :author ""
  :license ""
  :depends-on ("cl-mongo" "hunchentoot" "clack" "ningle" "cl-json" "hermetic" "lack-middleware-session" "cl-markup")
  :components ((:module "src"
                :components
                ((:file "packages")
         (:file "lisp-utils")
         (:file "xxx-xxxx" :depends-on ("packages"))
         (:file "database" :depends-on ("packages"))
         (:file "database-config" :depends-on ("packages"))
         (:file "server" :depends-on ("packages"))
         (:file "clack" :depends-on ("packages"))
         (:file "routes/activities" :depends-on ("packages"))
         (:file "route-processors" :depends-on ("packages")))))
  :description ""
  :long-description
  #.(read-file-string
     (subpathname *load-pathname* "README.markdown"))
  :in-order-to ((test-op (test-op "xxx-xxxx-test"))))

特别是,我对文件routes/activities和可能的route-processors遇到了问题。

鉴于我在ASDF中的经验,系统定义的唯一内容是"路由/活动"文件,因为子文件夹被定义为模块。此文件应解决您的问题:

(defsystem "xxx-xxxx"
  :version "0.1.0"
  :author ""
  :license ""
  :depends-on ("cl-mongo" 
               "hunchentoot" 
               "clack" 
               "ningle" 
               "cl-json" 
               "hermetic" 
               "lack-middleware-session" 
               "cl-markup")
  :components ((:module "src"
                :components
                ((:file "packages")
                 (:file "lisp-utils")
                 (:file "xxx-xxxx" 
                        :depends-on ("packages"))
                 (:file "database" 
                        :depends-on ("packages"))
                 (:file "database-config" 
                        :depends-on ("packages"))
                 (:file "server" 
                        :depends-on ("packages"))
                 (:file "clack" 
                        :depends-on ("packages"))
                 (:module "routes"
                          :components ((:file "activities"))
                          :depends-on ("packages"))
                 (:file "route-processors" 
                        :depends-on ("packages")))))
  :description ""
  :long-description
  #.(read-file-string
     (subpathname *load-pathname* "README.markdown"))
  :in-order-to ((test-op (test-op "xxx-xxxx-test"))))

解决您的最后评论。例外的原因是,依赖关系在列表中解决了依赖关系的父母。/子文件夹,由于其不存在,找不到它。不管是无关紧要的还是无关紧要的,这就是它的工作原理。这也有意义,因为一个模块通常描述了一个逻辑连贯的单元,因此预期该单元的依赖项将相似,否则您可能需要重新考虑您的项目结构。

最新更新