Borland-specific bad flag for LinkFlags tests

The Borland librarian actually creates a BADFLAG.obj when the object is
missing the first time!  This causes later tests to not reject it.
Instead use a Borland-specific variation on the flag.

Tests/LinkFlags/CMakeLists.txt

@@ -3,23 +3,26 @@ project(LinkFlags C)
 
 string(TOUPPER "${TEST_CONFIG}" TEST_CONFIG_UPPER)
 set(obj "${CMAKE_C_OUTPUT_EXTENSION}")
+if(BORLAND)
+  set(pre -)
+endif()
 
 add_library(LinkFlags_lib STATIC LinkFlagsLib.c)
-set_property(TARGET LinkFlags_lib PROPERTY STATIC_LIBRARY_FLAGS BADFLAG${obj})
+set_property(TARGET LinkFlags_lib PROPERTY STATIC_LIBRARY_FLAGS ${pre}BADFLAG${obj})
 
 add_library(LinkFlags_dll SHARED LinkFlagsLib.c)
-set_property(TARGET LinkFlags_dll PROPERTY LINK_FLAGS BADFLAG${obj})
+set_property(TARGET LinkFlags_dll PROPERTY LINK_FLAGS ${pre}BADFLAG${obj})
 
 add_executable(LinkFlags_exe LinkFlags.c)
-set_property(TARGET LinkFlags_exe PROPERTY LINK_FLAGS BADFLAG${obj})
+set_property(TARGET LinkFlags_exe PROPERTY LINK_FLAGS ${pre}BADFLAG${obj})
 
 add_library(LinkFlags_lib_config STATIC LinkFlagsLib.c)
-set_property(TARGET LinkFlags_lib_config PROPERTY STATIC_LIBRARY_FLAGS_${TEST_CONFIG_UPPER} BADFLAG_${TEST_CONFIG}${obj})
+set_property(TARGET LinkFlags_lib_config PROPERTY STATIC_LIBRARY_FLAGS_${TEST_CONFIG_UPPER} ${pre}BADFLAG_${TEST_CONFIG}${obj})
 
 add_library(LinkFlags_dll_config SHARED LinkFlagsLib.c)
-set_property(TARGET LinkFlags_dll_config PROPERTY LINK_FLAGS_${TEST_CONFIG_UPPER} BADFLAG_${TEST_CONFIG}${obj})
+set_property(TARGET LinkFlags_dll_config PROPERTY LINK_FLAGS_${TEST_CONFIG_UPPER} ${pre}BADFLAG_${TEST_CONFIG}${obj})
 
 add_executable(LinkFlags_exe_config LinkFlags.c)
-set_property(TARGET LinkFlags_exe_config PROPERTY LINK_FLAGS_${TEST_CONFIG_UPPER} BADFLAG_${TEST_CONFIG}${obj})
+set_property(TARGET LinkFlags_exe_config PROPERTY LINK_FLAGS_${TEST_CONFIG_UPPER} ${pre}BADFLAG_${TEST_CONFIG}${obj})
 
 add_executable(LinkFlags LinkFlags.c)