diff --git a/BUILDING.md b/BUILDING.md index 581fbddb..36d4e7e9 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -27,7 +27,7 @@ package for CMake that you can install. The same goes for all of the major flavors of BSD UNIX (Free/Net/Open/Dragonfly), OpenSolaris, and Cygwin. If you're using Mac OS X or Windows, you can download CMake binaries from: -http://www.cmake.org/download/ +https://www.cmake.org/download/ On Mac or Windows, be sure to let the installer put links to the CMake command- line tools in bin or add them to your PATH. diff --git a/Doxyfile b/Doxyfile index c0109274..70eac765 100644 --- a/Doxyfile +++ b/Doxyfile @@ -20,7 +20,7 @@ # This tag specifies the encoding used for all characters in the config file # that follow. The default is UTF-8 which is also the encoding used for all text # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv -# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv +# built into libc) for the transcoding. See https://www.gnu.org/software/libiconv # for the list of possible encodings. # The default value is: UTF-8. @@ -272,7 +272,7 @@ EXTENSION_MAPPING = # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments # according to the Markdown format, which allows for more readable -# documentation. See http://daringfireball.net/projects/markdown/ for details. +# documentation. See https://daringfireball.net/projects/markdown/ for details. # The output of markdown processing is further processed by doxygen, so you can # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in # case of backward compatibilities issues. @@ -305,7 +305,7 @@ BUILTIN_STL_SUPPORT = YES CPP_CLI_SUPPORT = NO # Set the SIP_SUPPORT tag to YES if your project consists of sip (see: -# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen +# https://riverbankcomputing.com/software/sip/intro) sources only. Doxygen # will parse them like normal C++ but will assume all classes use public instead # of private inheritance when no explicit protection keyword is present. # The default value is: NO. @@ -656,7 +656,7 @@ LAYOUT_FILE = # The CITE_BIB_FILES tag can be used to specify one or more bib files containing # the reference definitions. This must be a list of .bib files. The .bib # extension is automatically appended if omitted. This requires the bibtex tool -# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. +# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info. # For LaTeX the style of the bibliography can be controlled using # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the # search path. Do not use file names with spaces, bibtex cannot handle them. See @@ -738,7 +738,7 @@ INPUT = # This tag can be used to specify the character encoding of the source files # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses # libiconv (or the iconv built into libc) for the transcoding. See the libiconv -# documentation (see: http://www.gnu.org/software/libiconv) for the list of +# documentation (see: https://www.gnu.org/software/libiconv) for the list of # possible encodings. # The default value is: UTF-8. @@ -930,7 +930,7 @@ SOURCE_TOOLTIPS = YES # If the USE_HTAGS tag is set to YES then the references to source code will # point to the HTML generated by the htags(1) tool instead of doxygen built-in # source browser. The htags tool is part of GNU's global source tagging system -# (see http://www.gnu.org/software/global/global.html). You will need version +# (see https://www.gnu.org/software/global/global.html). You will need version # 4.8.6 or higher. # # To use it do the following: @@ -1073,7 +1073,7 @@ HTML_EXTRA_FILES = # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen # will adjust the colors in the stylesheet and background images according to # this color. Hue is specified as an angle on a colorwheel, see -# http://en.wikipedia.org/wiki/Hue for more information. For instance the value +# https://en.wikipedia.org/wiki/Hue for more information. For instance the value # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 # purple, and 360 is red again. # Minimum value: 0, maximum value: 359, default value: 220. @@ -1131,12 +1131,12 @@ HTML_INDEX_NUM_ENTRIES = 100 # If the GENERATE_DOCSET tag is set to YES, additional index files will be # generated that can be used as input for Apple's Xcode 3 integrated development -# environment (see: http://developer.apple.com/tools/xcode/), introduced with +# environment (see: https://developer.apple.com/tools/xcode/), introduced with # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a # Makefile in the HTML output directory. Running make will produce the docset in # that directory and running make install will install the docset in # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at -# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html +# startup. See https://developer.apple.com/tools/creatingdocsetswithdoxygen.html # for more information. # The default value is: NO. # This tag requires that the tag GENERATE_HTML is set to YES. @@ -1176,7 +1176,7 @@ DOCSET_PUBLISHER_NAME = Publisher # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three # additional HTML index files: index.hhp, index.hhc, and index.hhk. The # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop -# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on +# (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on # Windows. # # The HTML Help Workshop contains a compiler that can convert all HTML output @@ -1251,7 +1251,7 @@ QCH_FILE = # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help # Project output. For more information please see Qt Help Project / Namespace -# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). +# (see: https://www.qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). # The default value is: org.doxygen.Project. # This tag requires that the tag GENERATE_QHP is set to YES. @@ -1259,7 +1259,7 @@ QHP_NAMESPACE = org.doxygen.Project # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt # Help Project output. For more information please see Qt Help Project / Virtual -# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- +# Folders (see: https://www.qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- # folders). # The default value is: doc. # This tag requires that the tag GENERATE_QHP is set to YES. @@ -1268,7 +1268,7 @@ QHP_VIRTUAL_FOLDER = doc # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom # filter to add. For more information please see Qt Help Project / Custom -# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# Filters (see: https://www.qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # filters). # This tag requires that the tag GENERATE_QHP is set to YES. @@ -1276,7 +1276,7 @@ QHP_CUST_FILTER_NAME = # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the # custom filter to add. For more information please see Qt Help Project / Custom -# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# Filters (see: https://www.qt-project.org/doc/qt-4.8/qthelpproject.html#custom- # filters). # This tag requires that the tag GENERATE_QHP is set to YES. @@ -1284,7 +1284,7 @@ QHP_CUST_FILTER_ATTRS = # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this # project's filter section matches. Qt Help Project / Filter Attributes (see: -# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). +# https://www.qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). # This tag requires that the tag GENERATE_QHP is set to YES. QHP_SECT_FILTER_ATTRS = @@ -1389,7 +1389,7 @@ FORMULA_FONTSIZE = 10 FORMULA_TRANSPARENT = YES # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see -# http://www.mathjax.org) which uses client side Javascript for the rendering +# https://www.mathjax.org) which uses client side Javascript for the rendering # instead of using prerendered bitmaps. Use this if you do not have LaTeX # installed or if you want to formulas look prettier in the HTML output. When # enabled you may also need to install MathJax separately and configure the path @@ -1401,7 +1401,7 @@ USE_MATHJAX = NO # When MathJax is enabled you can set the default output format to be used for # the MathJax output. See the MathJax site (see: -# http://docs.mathjax.org/en/latest/output.html) for more details. +# https://docs.mathjax.org/en/latest/output.html) for more details. # Possible values are: HTML-CSS (which is slower, but has the best # compatibility), NativeMML (i.e. MathML) and SVG. # The default value is: HTML-CSS. @@ -1416,11 +1416,11 @@ MATHJAX_FORMAT = HTML-CSS # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax # Content Delivery Network so you can quickly see the result without installing # MathJax. However, it is strongly recommended to install a local copy of -# MathJax from http://www.mathjax.org before deployment. -# The default value is: http://cdn.mathjax.org/mathjax/latest. +# MathJax from https://www.mathjax.org before deployment. +# The default value is: https://cdn.mathjax.org/mathjax/latest. # This tag requires that the tag USE_MATHJAX is set to YES. -MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest +MATHJAX_RELPATH = https://cdn.mathjax.org/mathjax/latest # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax # extension names that should be enabled during MathJax rendering. For example @@ -1431,7 +1431,7 @@ MATHJAX_EXTENSIONS = # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces # of code that will be used on startup of the MathJax code. See the MathJax site -# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an +# (see: https://docs.mathjax.org/en/latest/output.html) for more details. For an # example see the documentation. # This tag requires that the tag USE_MATHJAX is set to YES. @@ -1478,7 +1478,7 @@ SERVER_BASED_SEARCH = NO # # Doxygen ships with an example indexer ( doxyindexer) and search engine # (doxysearch.cgi) which are based on the open source search engine library -# Xapian (see: http://xapian.org/). +# Xapian (see: https://xapian.org/). # # See the section "External Indexing and Searching" for details. # The default value is: NO. @@ -1491,7 +1491,7 @@ EXTERNAL_SEARCH = NO # # Doxygen ships with an example indexer ( doxyindexer) and search engine # (doxysearch.cgi) which are based on the open source search engine library -# Xapian (see: http://xapian.org/). See the section "External Indexing and +# Xapian (see: https://xapian.org/). See the section "External Indexing and # Searching" for details. # This tag requires that the tag SEARCHENGINE is set to YES. @@ -1662,7 +1662,7 @@ LATEX_SOURCE_CODE = NO # The LATEX_BIB_STYLE tag can be used to specify the style to use for the # bibliography, e.g. plainnat, or ieeetr. See -# http://en.wikipedia.org/wiki/BibTeX and \cite for more info. +# https://en.wikipedia.org/wiki/BibTeX and \cite for more info. # The default value is: plain. # This tag requires that the tag GENERATE_LATEX is set to YES. @@ -1823,7 +1823,7 @@ DOCBOOK_OUTPUT = docbook #--------------------------------------------------------------------------- # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen -# Definitions (see http://autogen.sf.net) file that captures the structure of +# Definitions (see http://autogen.sourceforge.net/) file that captures the structure of # the code including all documentation. Note that this feature is still # experimental and incomplete at the moment. # The default value is: NO. @@ -2027,7 +2027,7 @@ HIDE_UNDOC_RELATIONS = YES # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is # available from the path. This tool is part of Graphviz (see: -# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent +# https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent # Bell Labs. The other options in this section have no effect if this option is # set to NO # The default value is: NO. diff --git a/WORKING_WITH_AN_IDE.md b/WORKING_WITH_AN_IDE.md index f9139ab0..d2e57380 100644 --- a/WORKING_WITH_AN_IDE.md +++ b/WORKING_WITH_AN_IDE.md @@ -29,7 +29,7 @@ and the assocaited command line tools. Unfortunately, the command line tools do not package `cmake`, which is needed to build Quickstep. You can install cmake using brew as follows: -Visit http://brew.sh to determine the instructions to install brew. It will look +Visit https://brew.sh to determine the instructions to install brew. It will look something like: ``` diff --git a/build/vagrant/ubuntu-precise-amd64/Vagrantfile b/build/vagrant/ubuntu-precise-amd64/Vagrantfile index 903dedcd..b5b75123 100644 --- a/build/vagrant/ubuntu-precise-amd64/Vagrantfile +++ b/build/vagrant/ubuntu-precise-amd64/Vagrantfile @@ -21,8 +21,8 @@ Vagrant.configure(2) do |config| sudo apt-get update sudo apt-get install -y python-software-properties sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test - wget -O - http://llvm.org/apt/llvm-snapshot.gpg.key|sudo apt-key add - - sudo add-apt-repository -y 'deb http://llvm.org/apt/jessie/ llvm-toolchain-jessie-3.7 main' + wget -O - https://llvm.org/apt/llvm-snapshot.gpg.key|sudo apt-key add - + sudo add-apt-repository -y 'deb https://llvm.org/apt/jessie/ llvm-toolchain-jessie-3.7 main' sudo apt-get update sudo apt-get install -y \ build-essential gcc-4.9 g++-4.9 clang-3.7 gdb cmake git \ diff --git a/parser/SqlParser.ypp b/parser/SqlParser.ypp index 1202d66e..16c8fc42 100644 --- a/parser/SqlParser.ypp +++ b/parser/SqlParser.ypp @@ -44,7 +44,7 @@ typedef struct YYLTYPE { /* * Modified from the default YYLLOC_DEFAULT - * (http://www.gnu.org/software/bison/manual/html_node/Location-Default-Action.html). + * (https://www.gnu.org/software/bison/manual/html_node/Location-Default-Action.html). * The assignments for last_line and last_column are removed as they are not used. */ #define YYLLOC_DEFAULT(current, rhs, n) \ diff --git a/parser/preprocessed/SqlParser_gen.cpp b/parser/preprocessed/SqlParser_gen.cpp index f2cb8ca2..174810ab 100644 --- a/parser/preprocessed/SqlParser_gen.cpp +++ b/parser/preprocessed/SqlParser_gen.cpp @@ -15,7 +15,7 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License - along with this program. If not, see . */ + along with this program. If not, see . */ /* As a special exception, you may create a larger work that contains part or all of the Bison parser skeleton and distribute that work @@ -81,7 +81,7 @@ typedef struct YYLTYPE { /* * Modified from the default YYLLOC_DEFAULT - * (http://www.gnu.org/software/bison/manual/html_node/Location-Default-Action.html). + * (https://www.gnu.org/software/bison/manual/html_node/Location-Default-Action.html). * The assignments for last_line and last_column are removed as they are not used. */ #define YYLLOC_DEFAULT(current, rhs, n) \ diff --git a/parser/preprocessed/SqlParser_gen.hpp b/parser/preprocessed/SqlParser_gen.hpp index 72fa9ef6..ca845a9a 100644 --- a/parser/preprocessed/SqlParser_gen.hpp +++ b/parser/preprocessed/SqlParser_gen.hpp @@ -15,7 +15,7 @@ GNU General Public License for more details. You should have received a copy of the GNU General Public License - along with this program. If not, see . */ + along with this program. If not, see . */ /* As a special exception, you may create a larger work that contains part or all of the Bison parser skeleton and distribute that work diff --git a/storage/CountedReference.hpp b/storage/CountedReference.hpp index 10a8a874..b7557c32 100644 --- a/storage/CountedReference.hpp +++ b/storage/CountedReference.hpp @@ -87,7 +87,7 @@ class CountedReference { * MutableBlockReference to a BlockReference. The weird template stuff is to * ensure that this code is only generated when T = const StorageBlockBase or const * StorageBlob. See - * http://stackoverflow.com/questions/17842478/select-class-constructor-using- + * https://stackoverflow.com/questions/17842478/select-class-constructor-using- * enable-if. * @param other The other block. **/ diff --git a/third_party/benchmark/CONTRIBUTING.md b/third_party/benchmark/CONTRIBUTING.md index 43de4c9d..60b6327e 100644 --- a/third_party/benchmark/CONTRIBUTING.md +++ b/third_party/benchmark/CONTRIBUTING.md @@ -54,5 +54,5 @@ of your first [pull request][]. 1. Finally, push the commits to your fork and submit a [pull request][]. [forking]: https://help.github.com/articles/fork-a-repo -[well-formed commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html +[well-formed commit messages]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html [pull request]: https://help.github.com/articles/creating-a-pull-request diff --git a/third_party/benchmark/src/cycleclock.h b/third_party/benchmark/src/cycleclock.h index 5b284171..f9d849bd 100644 --- a/third_party/benchmark/src/cycleclock.h +++ b/third_party/benchmark/src/cycleclock.h @@ -35,7 +35,7 @@ // environments, and have conflicting // declarations of some other intrinsics, breaking compilation. // Therefore, we simply declare __rdtsc ourselves. See also -// http://connect.microsoft.com/VisualStudio/feedback/details/262047 +// https://connect.microsoft.com/VisualStudio/feedback/details/262047 #if defined(COMPILER_MSVC) && !defined(_M_IX86) extern "C" uint64_t __rdtsc(); #pragma intrinsic(__rdtsc) @@ -45,7 +45,7 @@ extern "C" uint64_t __rdtsc(); namespace benchmark { // NOTE: only i386 and x86_64 have been well tested. // PPC, sparc, alpha, and ia64 are based on -// http://peter.kuscsik.com/wordpress/?p=14 +// https://peter.kuscsik.com/wordpress/?p=14 // with modifications by m3b. See also // https://setisvn.ssl.berkeley.edu/svn/lib/fftw-3.0.1/kernel/cycle.h namespace cycleclock { diff --git a/third_party/benchmark/src/sysinfo.cc b/third_party/benchmark/src/sysinfo.cc index ee3c238e..afaaa135 100644 --- a/third_party/benchmark/src/sysinfo.cc +++ b/third_party/benchmark/src/sysinfo.cc @@ -201,7 +201,7 @@ void InitializeSystemInfo() { // SMP, APIC, or APM support. hz should be 64-bit in freebsd 7.0 // and later. Before that, it's a 32-bit quantity (and gives the // wrong answer on machines faster than 2^32 Hz). See -// http://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001846.html +// https://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001846.html // But also compare FreeBSD 7.0: // http://fxr.watson.org/fxr/source/i386/i386/tsc.c?v=RELENG70#L223 // 231 error = sysctl_handle_quad(oidp, &freq, 0, req); diff --git a/third_party/cpplint/cpplint.py b/third_party/cpplint/cpplint.py index 28b8afa0..e5826489 100755 --- a/third_party/cpplint/cpplint.py +++ b/third_party/cpplint/cpplint.py @@ -70,7 +70,7 @@ [file] ... The style guidelines this tries to follow are those in - http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml + https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Every problem is given a confidence score from 1-5, with 5 meaning we are certain of the problem, and 1 meaning it could be a legitimate construct. @@ -2854,7 +2854,7 @@ def CheckForFunctionLengths(filename, clean_lines, linenum, """Reports for long function bodies. For an overview why this is done, see: - http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Write_Short_Functions + https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Write_Short_Functions Uses a simplistic algorithm assuming other style guidelines (especially spacing) are followed. @@ -4878,7 +4878,7 @@ def CheckLanguage(filename, clean_lines, linenum, file_extension, and line[-1] != '\\'): error(filename, linenum, 'build/namespaces', 4, 'Do not use unnamed namespaces in header files. See ' - 'http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Namespaces' + 'https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Namespaces' ' for more information.') diff --git a/third_party/farmhash/README b/third_party/farmhash/README index 146936d2..4bb717a8 100644 --- a/third_party/farmhash/README +++ b/third_party/farmhash/README @@ -135,7 +135,7 @@ Hash Quality We like to test hash functions with SMHasher, among other things. SMHasher isn't perfect, but it seems to find almost any significant flaw. -SMHasher is available at http://code.google.com/p/smhasher/ +SMHasher is available at https://code.google.com/p/smhasher/ SMHasher is designed to pass a 32-bit seed to the hash functions it tests. For our functions that accept a seed, we use the given seed directly (padded @@ -156,7 +156,7 @@ there is never going to be as portable as the other parts of FarmHash.) For more information ==================== -http://code.google.com/p/farmhash/ +https://code.google.com/p/farmhash/ farmhash-discuss@googlegroups.com diff --git a/third_party/farmhash/Understanding_Hash_Functions b/third_party/farmhash/Understanding_Hash_Functions index 8d203c45..e89c2c90 100644 --- a/third_party/farmhash/Understanding_Hash_Functions +++ b/third_party/farmhash/Understanding_Hash_Functions @@ -153,10 +153,10 @@ REFERENCES [Murmur] Appleby, Austin. https://code.google.com/p/smhasher, https://sites.google.com/site/murmurhash/ [SMHasher] Appleby, Austin. https://code.google.com/p/smhasher -[SHA-3] Bertoni, Guido, et al. http://keccak.noekeon.org/ -[Jenkins] Jenkins, Bob. http://burtleburtle.net/bob/hash/doobs.html +[SHA-3] Bertoni, Guido, et al. https://keccak.team/keccak.noekeon.org/ +[Jenkins] Jenkins, Bob. https://burtleburtle.net/bob/hash/doobs.html [VHASH] Krovetz, Ted. Message authentication on 64-bit architectures. In Selected Areas of Cryptography – SAC 2006. Springer-Verlag, 2006. [CityHash] Pike, Geoff and Alakuijala, Jyrki. https://code.google.com/p/cityhash [FarmHash] Pike, Geoff. https://code.google.com/p/farmhash -[Pike] Pike, Geoff. http://www.stanford.edu/class/ee380/Abstracts/121017-slides.pdf +[Pike] Pike, Geoff. https://www.stanford.edu/class/ee380/Abstracts/121017-slides.pdf diff --git a/third_party/farmhash/farmhash.h b/third_party/farmhash/farmhash.h index 74ffc370..be5bbbed 100644 --- a/third_party/farmhash/farmhash.h +++ b/third_party/farmhash/farmhash.h @@ -21,7 +21,7 @@ // FarmHash, by Geoff Pike // -// http://code.google.com/p/farmhash/ +// https://code.google.com/p/farmhash/ // // This file provides a few functions for hashing strings and other // data. All of them are high-quality functions in the sense that diff --git a/third_party/gflags/CMakeLists.txt b/third_party/gflags/CMakeLists.txt index 54b5c358..8035e109 100644 --- a/third_party/gflags/CMakeLists.txt +++ b/third_party/gflags/CMakeLists.txt @@ -22,7 +22,7 @@ if (CMAKE_VERSION VERSION_LESS 100) # C language still needed because the following required CMake modules # (or their dependencies, respectively) are not correctly handling # the case where only CXX is enabled. - # - CheckTypeSize.cmake (fixed in CMake 3.1, cf. http://www.cmake.org/Bug/view.php?id=14056) + # - CheckTypeSize.cmake (fixed in CMake 3.1, cf. https://www.cmake.org/Bug/view.php?id=14056) # - FindThreads.cmake (--> CheckIncludeFiles.cmake <--) enable_language (C) endif () @@ -435,7 +435,7 @@ if (BUILD_PACKAGING) # RPM package information -- used in cmake/package.cmake.in also for DEB set (CPACK_RPM_PACKAGE_GROUP "Development/Libraries") set (CPACK_RPM_PACKAGE_LICENSE "BSD") - set (CPACK_RPM_PACKAGE_URL "http://schuhschuh.github.com/gflags") + set (CPACK_RPM_PACKAGE_URL "https://schuhschuh.github.com/gflags") set (CPACK_RPM_CHANGELOG_FILE "${CMAKE_CURRENT_LIST_DIR}/ChangeLog.txt") if (INSTALL_HEADERS) diff --git a/third_party/gflags/INSTALL.md b/third_party/gflags/INSTALL.md index d054193d..79c5c09a 100644 --- a/third_party/gflags/INSTALL.md +++ b/third_party/gflags/INSTALL.md @@ -14,7 +14,7 @@ following command: Compiling the source code ========================= -The build system of gflags is since version 2.1 based on [CMake](http://cmake.org). +The build system of gflags is since version 2.1 based on [CMake](https://cmake.org). The common steps to build, test, and install software are therefore: 1. Extract source files. diff --git a/third_party/gflags/README.md b/third_party/gflags/README.md index 640e436c..dea3fc2c 100644 --- a/third_party/gflags/README.md +++ b/third_party/gflags/README.md @@ -50,7 +50,7 @@ When fixing an issue for a pull request through either of these hosting platforms, please reference the issue number as [described here](https://code.google.com/p/support/wiki/IssueTracker#Integration_with_version_control). For the further development, I am following the -[Git branching model](http://nvie.com/posts/a-successful-git-branching-model/) +[Git branching model](https://nvie.com/posts/a-successful-git-branching-model/) with feature branch names prefixed by "feature/" and bugfix branch names prefixed by "bugfix/", respectively. @@ -76,7 +76,7 @@ More than a year has past since I (Andreas) took over the maintenance for To get more involved and stimulate participation in the further development of the library, I moved the project source code today to [GitHub](https://github.com/schuhschuh/gflags). -I believe that the strengths of [Git](http://git-scm.com/) will allow for better community collaboration +I believe that the strengths of [Git](https://git-scm.com/) will allow for better community collaboration as well as ease the integration of changes made by others. I encourage everyone who would like to contribute to send me pull requests. Git's lightweight feature branches will also provide the right tool for more @@ -95,7 +95,7 @@ Please continue to report any issues with gflags on Google Code. The GitHub proj only be used to host the Git repository. One major change of the project structure I have in mind for the next weeks -is the migration from autotools to [CMake](http://www.cmake.org/). +is the migration from autotools to [CMake](https://www.cmake.org/). Check out the (unstable!) [cmake-migration](https://github.com/schuhschuh/gflags/tree/cmake-migration) branch on GitHub for details. @@ -192,7 +192,7 @@ all tests pass. I **really** never thought non-unix-y Windows folks would want gflags, but at least some of them do. The major news, though, is that I've separated out the python package -into its own library, [python-gflags](http://code.google.com/p/python-gflags). +into its own library, [python-gflags](https://code.google.com/p/python-gflags). If you're interested in the Python version of gflags, that's the place to get it now. diff --git a/third_party/gflags/cmake/package.cmake.in b/third_party/gflags/cmake/package.cmake.in index aaec7925..5e7ac001 100644 --- a/third_party/gflags/cmake/package.cmake.in +++ b/third_party/gflags/cmake/package.cmake.in @@ -1,5 +1,5 @@ # Per-generator CPack configuration file. See CPACK_PROJECT_CONFIG_FILE documented at -# http://www.cmake.org/cmake/help/v2.8.12/cpack.html#variable:CPACK_PROJECT_CONFIG_FILE +# https://www.cmake.org/cmake/help/v2.8.12/cpack.html#variable:CPACK_PROJECT_CONFIG_FILE # # All common CPACK_* variables are set in CMakeLists.txt already. This file only # overrides some of these to provide package generator specific settings. diff --git a/third_party/gflags/cmake/version.cmake.in b/third_party/gflags/cmake/version.cmake.in index 1e1af050..e23bd503 100644 --- a/third_party/gflags/cmake/version.cmake.in +++ b/third_party/gflags/cmake/version.cmake.in @@ -8,7 +8,7 @@ set (PACKAGE_VERSION "@PACKAGE_VERSION@") # check compatibility # Perform compatibility check here using the input CMake variables. -# See example in http://www.cmake.org/Wiki/CMake_2.6_Notes. +# See example in https://www.cmake.org/Wiki/CMake_2.6_Notes. set (PACKAGE_VERSION_COMPATIBLE TRUE) set (PACKAGE_VERSION_UNSUITABLE FALSE) diff --git a/third_party/gflags/doc/index.html b/third_party/gflags/doc/index.html index 3a667139..218ddff4 100644 --- a/third_party/gflags/doc/index.html +++ b/third_party/gflags/doc/index.html @@ -93,7 +93,7 @@

Introduction, and Comparison to Other Commandline

Finding and Linking to gflags using CMake

-

Using gflags within a project which uses CMake for its build system is easy. Therefore, simply add the following CMake code to your CMakeLists.txt file. +

Using gflags within a project which uses CMake for its build system is easy. Therefore, simply add the following CMake code to your CMakeLists.txt file.

    find_package (gflags REQUIRED)
diff --git a/third_party/gflags/src/gflags.h.in b/third_party/gflags/src/gflags.h.in
index 0324d390..08b1a1be 100644
--- a/third_party/gflags/src/gflags.h.in
+++ b/third_party/gflags/src/gflags.h.in
@@ -546,7 +546,7 @@ inline clstring* dont_pass0toDEFINE_string(char *stringspot,
 // great together!
 // The weird 'using' + 'extern' inside the fLS namespace is to work around
 // an unknown compiler bug/issue with the gcc 4.2.1 on SUSE 10.  See
-//    http://code.google.com/p/google-gflags/issues/detail?id=20
+//    https://code.google.com/p/google-gflags/issues/detail?id=20
 #define DEFINE_string(name, val, txt)                                       \
   namespace fLS {                                                           \
     using ::fLS::clstring;                                                  \
diff --git a/third_party/gflags/src/mutex.h b/third_party/gflags/src/mutex.h
index 0bdd9d5f..0f5fef6c 100644
--- a/third_party/gflags/src/mutex.h
+++ b/third_party/gflags/src/mutex.h
@@ -51,7 +51,7 @@
 // in the code below.
 //
 // CYGWIN NOTE: Cygwin support for rwlock seems to be buggy:
-//    http://www.cygwin.com/ml/cygwin/2008-12/msg00017.html
+//    https://www.cygwin.com/ml/cygwin/2008-12/msg00017.html
 // Because of that, we might as well use windows locks for
 // cygwin.  They seem to be more reliable than the cygwin pthreads layer.
 //
diff --git a/third_party/gflags/src/windows_port.h b/third_party/gflags/src/windows_port.h
index c8ff24f8..e5281c98 100644
--- a/third_party/gflags/src/windows_port.h
+++ b/third_party/gflags/src/windows_port.h
@@ -34,7 +34,7 @@
  * easier to compile this code under VC++.
  *
  * Several of these are taken from glib:
- *    http://developer.gnome.org/doc/API/glib/glib-windows-compatability-functions.html
+ *    https://developer.gnome.org/doc/API/glib/glib-windows-compatability-functions.html
  */
 
 #ifndef GFLAGS_WINDOWS_PORT_H_
@@ -80,7 +80,7 @@ inline void setenv(const char* name, const char* value, int) {
   // We handle this by setting it to "0" and the NUL-ing out the \0.
   // That is, we putenv("FOO=0") and then find out where in memory the
   // putenv wrote "FOO=0", and change it in-place to "FOO=\0".
-  // c.f. http://svn.apache.org/viewvc/stdcxx/trunk/tests/src/environ.cpp?r1=611451&r2=637508&pathrev=637508
+  // c.f. https://svn.apache.org/viewvc/stdcxx/trunk/tests/src/environ.cpp?r1=611451&r2=637508&pathrev=637508
   static const char* const kFakeZero = "0";
   if (*value == '\0')
     value = kFakeZero;
diff --git a/third_party/gflags/test/gflags_unittest.cc b/third_party/gflags/test/gflags_unittest.cc
index 80f7398a..4be945c9 100644
--- a/third_party/gflags/test/gflags_unittest.cc
+++ b/third_party/gflags/test/gflags_unittest.cc
@@ -535,7 +535,7 @@ TEST(SetFlagValueTest, OrdinaryValues) {
 
 // Tests that flags can be set to exceptional values.
 // Note: apparently MINGW doesn't parse inf and nan correctly:
-//    http://www.mail-archive.com/bug-gnulib@gnu.org/msg09573.html
+//    https://www.mail-archive.com/bug-gnulib@gnu.org/msg09573.html
 // This url says FreeBSD also has a problem, but I didn't see that.
 TEST(SetFlagValueTest, ExceptionalValues) {
 #if defined(isinf) && !defined(__MINGW32__)
diff --git a/third_party/glog/COPYING b/third_party/glog/COPYING
index 38396b58..107760f8 100644
--- a/third_party/glog/COPYING
+++ b/third_party/glog/COPYING
@@ -30,7 +30,7 @@ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 A function gettimeofday in utilities.cc is based on
 
-http://www.google.com/codesearch/p?hl=en#dR3YEbitojA/COPYING&q=GetSystemTimeAsFileTime%20license:bsd
+https://www.google.com/codesearch/p?hl=en#dR3YEbitojA/COPYING&q=GetSystemTimeAsFileTime%20license:bsd
 
 The license of this code is:
 
diff --git a/third_party/glog/INSTALL b/third_party/glog/INSTALL
index 0babe243..1c9182a6 100644
--- a/third_party/glog/INSTALL
+++ b/third_party/glog/INSTALL
@@ -25,7 +25,7 @@ InstallFailureSignalHandler(), we strongly recommend you install
 libunwind before trying to configure or install google glog.
 libunwind can be found at
 
-   http://download.savannah.nongnu.org/releases/libunwind/libunwind-snap-070410.tar.gz
+   https://download.savannah.nongnu.org/releases/libunwind/libunwind-snap-070410.tar.gz
 
 Even if you already have libunwind installed, you will probably still
 need to install from the snapshot to get the latest version.
diff --git a/third_party/glog/README.windows b/third_party/glog/README.windows
index 74ff6904..4cc29925 100644
--- a/third_party/glog/README.windows
+++ b/third_party/glog/README.windows
@@ -18,8 +18,8 @@ I have little experience with Windows programming, so there may be
 better ways to set this up than I've done!  If you run across any
 problems, please post to the google-glog Google Group, or report
 them on the google-glog Google Code site:
-   http://groups.google.com/group/google-glog
-   http://code.google.com/p/google-glog/issues/list
+   https://groups.google.com/group/google-glog
+   https://code.google.com/p/google-glog/issues/list
 
 -- Shinichiro Hamaji
 
diff --git a/third_party/glog/doc/glog.html b/third_party/glog/doc/glog.html
index 8b200bac..0ce1dd88 100644
--- a/third_party/glog/doc/glog.html
+++ b/third_party/glog/doc/glog.html
@@ -5,7 +5,7 @@
 How To Use Google Logging Library (glog)
 
 
-