From ed7104094b14109ab5cbf8b696e01eebadb764dd Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Tue, 12 Jul 2016 10:16:01 +0200
Subject: Translate most link.exe options, other minor cleanups

---
 msvc-lib-common | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'msvc-lib-common')

diff --git a/msvc-lib-common b/msvc-lib-common
index 8b23f4f..7f10223 100755
--- a/msvc-lib-common
+++ b/msvc-lib-common
@@ -1,9 +1,11 @@
 #! /usr/bin/env bash
 
-# @@ Do we really need LIB? What's /LIBPATH for?
-#
 # Common lib.exe driver that expects the VC and LIB variables to be set for
 # the specific MSVC version/configuration.
+#
+# It's not clear/documented why we need LIB or what the /LIBPATH option is
+# for. Perhaps for link-time code generation (/LTCG).
+#
 
 trap "{ exit 1; }" ERR
 set -o errtrace # Trap in functions.
@@ -27,7 +29,7 @@ source $(dirname $(realpath ${BASH_SOURCE[0]}))/msvc-common
 args=()
 
 while [ $# -gt 0 ]; do
-  case $1 in
+  case ${1^^} in # Uppercase for case-insensitive comparison.
 
     # /DEF[:filename]
     # /OUT:filename
@@ -86,8 +88,6 @@ while [ $# -gt 0 ]; do
   esac
 done
 
-# @@ Do we need this?
-#
 export LIB
 
 # lib.exe always sends diagnostics to stdout.
-- 
cgit v1.1