From d73486fbaf29e0f90e10a84c50a4b12ed487b4d3 Mon Sep 17 00:00:00 2001 From: Robert Boehne Date: Sun, 17 Mar 2002 20:13:44 +0000 Subject: [PATCH] Remove obsolete comment --- exe/compile-txt.tpl | 21 +-------------------- 1 file changed, 1 insertion(+), 20 deletions(-) diff --git a/exe/compile-txt.tpl b/exe/compile-txt.tpl index 5e04dc08d..96d24c6ec 100644 --- a/exe/compile-txt.tpl +++ b/exe/compile-txt.tpl @@ -1,26 +1,7 @@ [++ AutoGen5 Template ++] [++ IF (getenv "SCRIPT") ++][++ # -This twisty little maze is very hard to follow. Here is what is -happening: - -The first non-flagged argument has already been pulled from the arg list -and stashed in "nonopt". - -The script assumes that the last unrecognized argument must, perforce, -be the name of the file being compiled. We know we are compiling and -not producing an executable because we were told so, or else we stumbled -upon a ``-c'' command line argument. Therefore, the command won't end -with library names. - -We strip out all the options we recognize and stuff the information -into shell variables. Everything else gets dropped into the "base_compile" -shell variable massaged so that when it is eval-ed, the compiler will -see the same characters as we have here in our arguments. It's an -ugly process that goes through two layers of quoting: double quotes -inside of single quotes. - -A final interesting note: -Xcompiler can appear anywhere and the following +NOTE: -Xcompiler can appear anywhere and the following argument will be inserted whereever we happen to be in the "base_compile" variable. It is not clear what the purpose here is, but if it is supposed to mark the compiler, then it won't work unless it is the first argument. -- 2.47.3