1. 25 Dec, 2013 1 commit
  2. 21 Dec, 2013 1 commit
  3. 19 Dec, 2013 1 commit
  4. 16 Dec, 2013 1 commit
  5. 14 Dec, 2013 1 commit
  6. 13 Dec, 2013 5 commits
  7. 11 Dec, 2013 1 commit
  8. 10 Dec, 2013 1 commit
  9. 09 Dec, 2013 4 commits
  10. 08 Dec, 2013 3 commits
  11. 04 Dec, 2013 2 commits
  12. 30 Nov, 2013 1 commit
  13. 28 Nov, 2013 1 commit
    • Vittorio Giovara's avatar
      configure: add strip flags checks · 0673ede9
      Vittorio Giovara authored
      This will check if -wN '..@*' is available and fall back on -x if not;
      when none are available, do not run strip at all to prevent removing
      functions that might be actually needed.
      0673ede9
  14. 27 Nov, 2013 1 commit
  15. 26 Nov, 2013 2 commits
  16. 25 Nov, 2013 1 commit
  17. 24 Nov, 2013 1 commit
  18. 23 Nov, 2013 2 commits
  19. 21 Nov, 2013 1 commit
    • Martin Storsjö's avatar
      configure: Avoid requiring c99wrap for working around msys path issues · ea9f7173
      Martin Storsjö authored
      
      
      Msys is unable to convert unix style absolute paths to windows style
      paths when combined with certain multichar MSVC options such as
      -Fo<file>. We used to work around this issue by passing them as two
      separate parameters separated by a space to c99wrap, which then mapped
      them back to the actual parameter format that MSVC uses.
      
      The only paths that actually are an issue are absolute unix style
      paths, and the only place such absolute paths are used with the output
      arguments (-Fo, -Fe, -Fi, -out:) are for the temp files within configure.
      
      By setting TMPDIR to . for msvc/icl builds, we never need to use
      absolute unix style paths for the file output, and we can use the
      actual proper form of the file output parameters. This avoids requiring
      the c99wrap wrapper for remapping the parameters for cases where the
      c99 converter isn't invoked at all (MSVC2013 and ICL).
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
      ea9f7173
  20. 19 Nov, 2013 2 commits
  21. 15 Nov, 2013 1 commit
  22. 13 Nov, 2013 1 commit
    • Martin Storsjö's avatar
      configure: Check whether MSVC requires using the C89-to-C99 converter · 16381923
      Martin Storsjö authored
      
      
      MSVC does support enough of C99 to work without the converter since
      the 2013 version. Try to detect which version of the compiler in
      the path needs to run the C99 converter or not. When the converter
      is omitted, compilation time is reduced quite drastically.
      
      Prior to this, users could still use --cc="c99conv -noconv cl"
      when running MSVC 2013 to achieve the same.
      
      This checks the version number instead of doing a normal compile
      test, since this check needs to be done earlier in configure, before
      the normal compile test helpers are usable.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
      16381923
  23. 08 Nov, 2013 1 commit
  24. 05 Nov, 2013 1 commit
  25. 02 Nov, 2013 1 commit
  26. 01 Nov, 2013 2 commits
    • Diego Biurrun's avatar
      configure: Properly check for availability of -Wno-foo warning flags · 056fd4fe
      Diego Biurrun authored
      For some weird reason gcc does not check if the -Wno disabling variants
      of warning flags match existing warning flags. Instead it swallows them
      silently. That is, unless other warning or error messages are generated,
      because then - for some even more bizarre reason - a complaint about the
      unknown disable warning flag is issued along with the error or warning
      message.
      
      Thus to check for the availability of a warning disabling option, one
      needs to check for the enabling variant instead and then add the
      disabling variant to CFLAGS.
      056fd4fe
    • Diego Biurrun's avatar
      configure: Split test_cflags function off from check_cflags · 23157d72
      Diego Biurrun authored
      This is useful to test flags without directly adding them to CFLAGS.
      23157d72