From ec671288cb026e8f4f4e2bc946a43bd9278efd2e Mon Sep 17 00:00:00 2001 From: Ben Sima Date: Mon, 30 Mar 2020 07:53:06 -0700 Subject: Add idea about file-based dependencies More generally, we could extend this to other settings, like 'main-is' and target architecture to compile for and so on. It would be best to define the parameters in Nix first, then later inline them to the code comments after we've worked out the interface. --- Com/Simatime/Bild.scm | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Com/Simatime/Bild.scm b/Com/Simatime/Bild.scm index aa6fa94..6b8c2ea 100755 --- a/Com/Simatime/Bild.scm +++ b/Com/Simatime/Bild.scm @@ -103,7 +103,10 @@ ;; 2 the target.nix could be the build description for target.hs ;; 3 just use a default.nix for the com.whatever ;; 4 have a deps.nix file -;; 5 list them in the file with other settings +;; 5 list them in the file with other settings. Starting with Haskell, +;; have comments like `{-: PACKAGE base <5.0.0.0 :-}' or `-- : PACKAGE base <5.0.0.0'. +;; Other languages could use `#:` for the special prefix, basically just +;; a comment plus colon. ;; - how to handle multiple output formats? ;; - e.g. that ghcjs and ghc take the same input files... ;; - say you have a .md file, you want to bild it to pdf, html, and more. What do? -- cgit v1.2.3