From 2f9058750ff60bcf6170eff4c260620c910636b7 Mon Sep 17 00:00:00 2001
From: simonpj <unknown>
Date: Wed, 4 Jul 2001 15:52:24 +0000
Subject: [PATCH] [project @ 2001-07-04 15:52:24 by simonpj] Add notes

---
 ghc/compiler/main/SysTools.lhs |   24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/ghc/compiler/main/SysTools.lhs b/ghc/compiler/main/SysTools.lhs
index c42acb7..b3ea84f 100644
--- a/ghc/compiler/main/SysTools.lhs
+++ b/ghc/compiler/main/SysTools.lhs
@@ -120,6 +120,30 @@ Config.hs contains two sorts of things
 		
 
 
+---------------------------------------------
+NOTES for an ALTERNATIVE scheme (i.e *not* what is currently implemented):
+
+Another hair-brained scheme for simplifying the current tool location
+nightmare in GHC: Simon originally suggested using another
+configuration file along the lines of GCC's specs file - which is fine
+except that it means adding code to read yet another configuration
+file.  What I didn't notice is that the current package.conf is
+general enough to do this:
+
+Package
+    {name = "tools",    import_dirs = [],  source_dirs = [],
+     library_dirs = [], hs_libraries = [], extra_libraries = [],
+     include_dirs = [], c_includes = [],   package_deps = [],
+     extra_ghc_opts = ["-pgmc/usr/bin/gcc","-pgml${libdir}/bin/unlit", ... etc.],
+     extra_cc_opts = [], extra_ld_opts = []}
+
+Which would have the advantage that we get to collect together in one
+place the path-specific package stuff with the path-specific tool
+stuff.
+		End of NOTES
+---------------------------------------------
+
+
 %************************************************************************
 %*									*
 \subsection{Global variables to contain system programs}
-- 
1.7.10.4