configuration data on Windows OS

"Paul Werkowski" <[email protected]>
Newsgroups gmane.lisp.clsql.devel
Message-ID <000b01c4c5c8$43118810$fb01a8c0@moby>
I have gotten the current svn version of CLSQL running under Lispworks for
Windows
and MySQL 4.1.7 via the "mysql-4-1-7-essential-win" installer package.

To get it all to work, I load a file containing these forms
~~~~~~~~~~~~~~~
#-ASDF
(load "CL-LIBRARY:ASDF;ASDF.LISP")

#-UFFI
(progn
  (pushnew #P"CL-LIBRARY:UFFI;" asdf:*central-registry* :test 'equal)
  (asdf:oos 'asdf:load-op :uffi))

#-CLSQL
(progn
  (pushnew #P"CL-LIBRARY:CLSQL;" asdf:*central-registry* :test 'equal)
  (asdf:oos 'asdf:load-op :clsql))

;;; Override bogus default locations
(unless (find-package "MYSQL")
  (make-package "MYSQL"))

(in-package #:mysql)
(defparameter *mysql-library-candidate-drive-letters* '( "F"))
(defparameter *mysql-library-candidate-directories*
  `("F:/Program Files/MySQL/MySQL Server 4.1/bin/"))

;;;;
(in-package #:cl-user)

(asdf:oos 'asdf:load-op :clsql-mysql)


(setq clsql:*default-database-type* :mysql)

~~~~~~~~~~~~~~~~~~~~~~~~
In addition, I had to manually add the path to the mysql bin directory to
the
Windows 2000 PATH environment variable.

The need to know package details and the *mysql-library-candidate-xxx*
variables
seems especially hackish. Is there a better way to inform the CLSQL system
of where
these files reside? Maybe taking a peek at the Windows registry would work?

Thanks,
Pual Werkowski
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.