Commits on Apr 26, 2024

1. msvc: handle flags that come from native-static-libs …

   As of https://github.com/rust-lang/rust/pull/122268/files, rust emits /defaultlib:msvcrt in native-static-libs
   
   This ends up in INTERFACE_LINK_LIBRARIES, and then ninja thinks it's a file:
   
   ninja: error: '/defaultlib:msvcrt', needed by 'cpp-exe.exe', missing and no known rule to make it
   
   This check to see if libraries start with a slash, and then assuming that they are a flag, and putting those in INTERFACE_LINK_OPTIONS instead. If there is some better way to detect flags, I'm all for it. We could also have it have anything that starts with `-` but not start with `-l` be detected as a flag, but that seems a bit more likely to be disruptive.
   
   I checked commandlines and it does indeed get propaged properly to the commandline.

   

   russelltg committed Apr 26, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 26d5e43
   • Browse repository at this point

   Copy the full SHA

   26d5e43 View commit details

   Browse the repository at this point in the history

2. only detect flags as starting with / on *msvc targets

   

   russelltg committed Apr 26, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 91232d9
   • Browse repository at this point

   Copy the full SHA

   91232d9 View commit details

   Browse the repository at this point in the history

3. add line in RELEASES.md

   

   russelltg committed Apr 26, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for d4ad661
   • Browse repository at this point

   Copy the full SHA

   d4ad661 View commit details

   Browse the repository at this point in the history