simdjson 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 60fb178b1b5ecb6e64bf62a4c2dd8eff606f84d5165588d1c09050ba2034dc0f
-  data.tar.gz: 1aeebbf0945925d29e49dc2bfd9c60bd0fbb8d88a05c3f933f8d289dbf615cb4
+  metadata.gz: 2e2a377a5c7bd6caeecf1e33a96bea3c465435875d7298b302c55b9318d0edfc
+  data.tar.gz: 2ab3a122c119c0112030b9dfa5cb7e6ed03fdcfb37cb1c5565f0d97d0f7d8efc
 SHA512:
-  metadata.gz: fbe1f178fafbf6afabaa4240cbde24f1e6be875c03c7634daf23ff2278766acc167f6b2f3bbd5e6596e5f469bbfab74b65cc0fb7d571b96efe954ee85d700fed
-  data.tar.gz: defd9f50ffd8e0161d4330740a81d43a3e27f30ead61fd83e5cbc0e9d727d1a11442dec6e93afe615377658d44c2ac616f0f9977f51fdd047f1678fa23de83f5
+  metadata.gz: cd75b90268aa240437cdb6bcf277289814c5daebac79916854b1a50865609910a3c1ac4a3460b3cca6871d12b472574bc6f4adf21048838aeb287f586efbfdb9
+  data.tar.gz: fa3cbc8d4f31efed6cfe2bf306f6ee762a4bfb90bc4f4e25adeb93c981c6c8025fcd13523ed54375593be38ab0e878b7646ac3a1ae012703a9f7a6f3a6e18e5a

data/.gitmodules

@@ -1,3 +1,3 @@
 [submodule "vendor/simdjson"]
 	path = vendor/simdjson
-	url = git@github.com:lemire/simdjson.git
+	url = https://github.com/lemire/simdjson.git

data/.travis.yml

@@ -1,7 +1,14 @@
 ---
-sudo: false
 language: ruby
 cache: bundler
+dist: bionic
+os: linux
 rvm:
-  - 2.6.2
-before_install: gem install bundler -v 2.0.1
+  - 2.7
+  - 2.6
+  - 2.5
+git:
+  submodules: false
+before_install:
+  - git submodule update --init
+  - gem install bundler -v 2.0.1

data/README.md

@@ -1,4 +1,6 @@
 # simdjson gem
+[![Build Status](https://travis-ci.org/saka1/simdjson_ruby.svg?branch=master)](https://travis-ci.org/saka1/simdjson_ruby)
+[![Gem Version](https://badge.fury.io/rb/simdjson.svg)](https://badge.fury.io/rb/simdjson)
 
 A Ruby bindings for [simdjson](https://github.com/lemire/simdjson).
 

data/Rakefile

@@ -28,4 +28,4 @@ task :clean_vendor do
   end
 end
 
-task default: %i[clobber compile test rubocop clean_vendor]
+task default: %i[clobber compile test clean_vendor]

data/benchmark/run_benchmark.rb

@@ -3,6 +3,7 @@
 require 'benchmark/ips'
 require 'json'
 require 'simdjson'
+require 'oj'
 
 files = %w[
   apache_builds.json
@@ -18,6 +19,9 @@ def run_report(rep, name, src)
   rep.report("#{name} - simdjson") do
     Simdjson.parse(src)
   end
+  rep.report("#{name} - OJ") do
+    Oj.load(src)
+  end
   rep.report("#{name} - standard JSON") do
     JSON.parse(src)
   end

data/ext/simdjson/extconf.rb

@@ -2,7 +2,7 @@ require 'mkmf'
 
 # rubocop:disable Style/GlobalVars
 
-$CXXFLAGS += ' -std=c++1z -mpclmul -mbmi -mbmi2 -mavx -mavx2 '
+$CXXFLAGS += ' -std=c++1z -mpclmul -mbmi -mbmi2 -mavx -mavx2 -Wno-register '
 
 CWD = __dir__
 SIMDJSON_DIR = File.join(CWD, '..', '..', 'vendor', 'simdjson')

data/ext/simdjson/simdjson.cpp

@@ -11,44 +11,37 @@ VALUE rb_eSimdjsonParseError;
 using namespace simdjson;
 
 // Convert tape to Ruby's Object
-static VALUE make_ruby_object(ParsedJson::Iterator &it) {
-    if (it.is_object()) {
-        VALUE hash = rb_hash_new();
-        if (it.down()) {
-            do {
-                assert(it.is_string());
-                VALUE key = rb_str_new(it.get_string(), it.get_string_length());
-                it.next();
-                VALUE val = make_ruby_object(it);
-                rb_hash_aset(hash, key, val);
-            } while (it.next());
-            it.up();
-        }
-        return hash;
-    } else if (it.is_array()) {
+static VALUE make_ruby_object(dom::element element) {
+    auto t = element.type();
+    if (t == dom::element_type::ARRAY) {
         VALUE ary = rb_ary_new();
-        if (it.down()) {
-            VALUE e0 = make_ruby_object(it);
-            rb_ary_push(ary, e0);
-            while (it.next()) {
-                VALUE e = make_ruby_object(it);
-                rb_ary_push(ary, e);
-            }
-            it.up();
+        for (dom::element x : element) {
+            VALUE e = make_ruby_object(x);
+            rb_ary_push(ary, e);
         }
         return ary;
-    } else if (it.is_string()) {
-        return rb_str_new(it.get_string(), it.get_string_length());
-    } else if (it.is_integer()) {
-        return LONG2NUM(it.get_integer());
-    } else if (it.is_double()) {
-        return DBL2NUM(it.get_double());
-    } else if (it.is_null()) {
+    } else if (t == dom::element_type::OBJECT) {
+        VALUE hash = rb_hash_new();
+        for (dom::key_value_pair field : dom::object(element)) {
+            std::string_view view(field.key);
+            VALUE k = rb_str_new(view.data(), view.size());
+            VALUE v = make_ruby_object(field.value);
+            rb_hash_aset(hash, k, v);
+        }
+        return hash;
+    } else if (t == dom::element_type::INT64) {
+        return LONG2NUM(element.get<int64_t>());
+    } else if (t == dom::element_type::UINT64) {
+        return ULONG2NUM(element.get<uint64_t>());
+    } else if (t == dom::element_type::DOUBLE) {
+        return DBL2NUM(double(element));
+    } else if (t == dom::element_type::STRING) {
+        std::string_view view(element);
+        return rb_str_new(view.data(), view.size());
+    } else if (t == dom::element_type::BOOL) {
+        return bool(element) ? Qtrue : Qfalse;
+    } else if (t == dom::element_type::NULL_VALUE) {
         return Qnil;
-    } else if (it.is_true()) {
-        return Qtrue;
-    } else if (it.is_false()) {
-        return Qfalse;
     }
     // unknown case (bug)
     rb_raise(rb_eException, "[BUG] must not happen");
@@ -57,14 +50,14 @@ static VALUE make_ruby_object(ParsedJson::Iterator &it) {
 static VALUE rb_simdjson_parse(VALUE self, VALUE arg) {
     Check_Type(arg, T_STRING);
 
-    const padded_string p{RSTRING_PTR(arg)};
-    ParsedJson pj = build_parsed_json(p);
-    if (!pj.is_valid()) {
-        rb_raise(rb_eSimdjsonParseError, "parse error");
-        return Qnil;
+    dom::parser parser;
+    auto [doc, error] = parser.parse(RSTRING_PTR(arg), RSTRING_LEN(arg));
+    if (error == SUCCESS) {
+        return make_ruby_object(doc);
     }
-    ParsedJson::Iterator it{pj};
-    return make_ruby_object(it);
+    // TODO better error handling
+    rb_raise(rb_eSimdjsonParseError, "parse error");
+    return Qnil;
 }
 
 extern "C" {

data/lib/simdjson/version.rb

@@ -1,3 +1,3 @@
 module Simdjson
-  VERSION = '0.2.0'.freeze
+  VERSION = '0.3.0'.freeze
 end

data/simdjson.gemspec

@@ -28,7 +28,8 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'benchmark-ips'
   spec.add_development_dependency 'bundler', '~> 2.0'
   spec.add_development_dependency 'minitest', '~> 5.0'
-  spec.add_development_dependency 'rake', '~> 10.0'
+  spec.add_development_dependency 'oj'
+  spec.add_development_dependency 'rake', '>= 12.3.3'
   spec.add_development_dependency 'rake-compiler'
   spec.add_development_dependency 'rubocop'
   spec.add_development_dependency 'rubocop-performance'

data/vendor/simdjson/AUTHORS

@@ -1,3 +1,4 @@
-# List of authors for copyright purposes
+# List of authors for copyright purposes, in no particular order
 Daniel Lemire
 Geoff Langdale
+John Keiser

data/vendor/simdjson/CMakeLists.txt

@@ -1,52 +1,81 @@
 cmake_minimum_required(VERSION 3.9) # CMP0069 NEW
-include(CheckIPOSupported)
-check_ipo_supported(RESULT ltoresult)
-if(ltoresult)
-set(CMAKE_INTERPROCEDURAL_OPTIMIZATION TRUE)
-endif()
 
-# usage: cmake -DSIMDJSON_DISABLE_AVX=on ..
-option(SIMDJSON_DISABLE_AVX "Forcefully disable AVX even if hardware supports it" OFF)
+project(simdjson
+  DESCRIPTION "Parsing gigabytes of JSON per second"
+  LANGUAGES CXX C
+)
+
+set(PROJECT_VERSION_MAJOR 0)
+set(PROJECT_VERSION_MINOR 4)
+set(PROJECT_VERSION_PATCH 7)
+set(SIMDJSON_SEMANTIC_VERSION "0.4.7" CACHE STRING "simdjson semantic version")
+set(SIMDJSON_LIB_VERSION "2.0.0" CACHE STRING "simdjson library version")
+set(SIMDJSON_LIB_SOVERSION "2" CACHE STRING "simdjson library soversion")
+set(SIMDJSON_GITHUB_REPOSITORY https://github.com/simdjson/simdjson)
+
+include(GNUInstallDirs)
+include(cmake/simdjson-flags.cmake)
+include(cmake/simdjson-user-cmakecache.cmake)
 
-set(CMAKE_CXX_STANDARD 17)
-set(CMAKE_CXX_STANDARD_REQUIRED ON)
-set(CMAKE_MACOSX_RPATH OFF)
-if (NOT CMAKE_BUILD_TYPE)
-                message(STATUS "No build type selected, default to Release")
-                set(CMAKE_BUILD_TYPE Release CACHE STRING "Choose the type of build." FORCE)
+
+
+if(SIMDJSON_JUST_LIBRARY)
+  message( STATUS "Building just the library, omitting all tests, tools and benchmarks." )
 endif()
 
-project(simdjson)
-set(SIMDJSON_LIB_NAME simdjson)
-set(PROJECT_VERSION_MAJOR 0)
-set(PROJECT_VERSION_MINOR 2)
-set(PROJECT_VERSION_PATCH 1)
-set(SIMDJSON_LIB_VERSION "0.2.1" CACHE STRING "simdjson library version")
-set(SIMDJSON_LIB_SOVERSION "0" CACHE STRING "simdjson library soversion")
-
-if(NOT MSVC)
-option(SIMDJSON_BUILD_STATIC "Build a static library" OFF) # turning it on disables the production of a dynamic library
-else()
-option(SIMDJSON_BUILD_STATIC "Build a static library" ON) # turning it on disables the production of a dynamic library
+#
+# Set up test data
+#
+if(NOT(SIMDJSON_JUST_LIBRARY))
+  enable_testing()
+  add_subdirectory(jsonchecker)
+  add_subdirectory(jsonexamples)
+  add_library(test-data INTERFACE)
+  target_link_libraries(test-data INTERFACE jsonchecker-data jsonexamples-data)
 endif()
-option(SIMDJSON_SANITIZE "Sanitize addresses" OFF)
 
-set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/tools/cmake")
+#
+# Create the top level simdjson library (must be done at this level to use both src/ and include/
+# directories) and tools
+#
+add_subdirectory(include)
+add_subdirectory(src)
+add_subdirectory(windows)
+if(NOT(SIMDJSON_JUST_LIBRARY))
+  add_subdirectory(dependencies) ## This needs to be before tools because of cxxopts
+  add_subdirectory(tools)  ## This needs to be before tests because of cxxopts
+  add_subdirectory(singleheader)
+endif()
+install(FILES singleheader/simdjson.h DESTINATION ${CMAKE_INSTALL_INCLUDEDIR})
+
+#
+# Compile tools / tests / benchmarks
+#
+if(NOT(SIMDJSON_JUST_LIBRARY))
+  add_subdirectory(tests)
+  add_subdirectory(examples)
+  add_subdirectory(benchmark)
+  add_subdirectory(fuzz)
+endif()
 
-find_package(CTargets)
-find_package(Options)
+#
+# Source files should be just ASCII
+#
+find_program(FIND find)
+find_program(FILE file)
+find_program(GREP grep)
+if((FIND) AND (FILE) AND (GREP))
+    add_test(
+      NAME "just_ascii"
+      COMMAND sh -c "${FIND}  include src windows tools singleheader tests examples benchmark -path benchmark/checkperf-reference -prune -name '*.h'  -o -name '*.cpp' -type f  -exec ${FILE} '{}' \; |${GREP} -v ASCII || exit 0  && exit 1"
+      WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
+    )
+endif()
 
-install(DIRECTORY include/${SIMDJSON_LIB_NAME} DESTINATION include)
-set (TEST_DATA_DIR "${CMAKE_CURRENT_SOURCE_DIR}/jsonchecker/")
-set (BENCHMARK_DATA_DIR "${CMAKE_CURRENT_SOURCE_DIR}/jsonexamples/")
-add_definitions(-DSIMDJSON_TEST_DATA_DIR="${TEST_DATA_DIR}")
-add_definitions(-DSIMDJSON_BENCHMARK_DATA_DIR="${TEST_DATA_DIR}")
-enable_testing()
-add_subdirectory(src)
-add_subdirectory(tools)
-add_subdirectory(tests)
-add_subdirectory(benchmark)
 
+#
+# CPack
+#
 set(CPACK_PACKAGE_VENDOR "Daniel Lemire")
 set(CPACK_PACKAGE_CONTACT "lemire@gmail.com")
 set(CPACK_PACKAGE_DESCRIPTION_SUMMARY "Parsing gigabytes of JSON per second")

data/vendor/simdjson/CONTRIBUTING.md

@@ -0,0 +1,92 @@
+Contributing
+============
+
+The simdjson library is an open project written in C++. Contributions are invited. Contributors
+agree to the project's license.
+
+We have an extensive list of issues, and contributions toward any of these issues is invited.
+Contributions can take the form of code samples, better documentation or design ideas.
+
+In particular, the following contributions are invited:
+
+- The library is focused on performance. Well-documented performance optimization are invited.
+- Fixes to known or newly discovered bugs are always welcome. Typically, a bug fix should come with
+  a test demonstrating that the bug has been fixed.
+- The simdjson library is advanced software and maintainability and flexibility are always a
+  concern. Specific contributions to improve maintainability and flexibility are invited.
+
+We discourage the following types of contributions:
+
+- Code refactoring. We all have our preferences as to how code should be written, but unnecessary
+  refactoring can waste time and introduce new bugs. If you believe that refactoring is needed, you
+  first must explain how it helps in concrete terms. Does it improve the performance?
+- Applications of new language features for their own sake. Using advanced C++ language constructs
+  is actually a negative as it may reduce portability (to old compilers, old standard libraries and
+  systems) and reduce accessibility (to programmers that have not kept up), so it must be offsetted
+  by clear gains like performance or maintainability. When in doubt, avoid advanced C++ features
+  (beyond C++11).
+- Style formatting. In general, please abstain from reformatting code just to make it look prettier.
+  Though code formatting is important, it can also be a waste of time if several contributors try to
+  tweak the code base toward their own preference. Please do not introduce unneeded white-space
+  changes.
+
+In short, most code changes should either bring new features or better performance. We want to avoid unmotivated code changes.
+
+
+Specific rules
+----------
+
+We have few hard rules, but we have some:
+
+- Printing to standard output or standard error (`stderr`, `stdout`, `std::cerr`, `std::cout`) in the core library is forbidden. This follows from the [Writing R Extensions](https://cran.r-project.org/doc/manuals/R-exts.html) manual which states that "Compiled code should not write to stdout or stderr".
+- Calls to `abort()` are forbidden in the core library. This follows from the [Writing R Extensions](https://cran.r-project.org/doc/manuals/R-exts.html) manual which states that "Under no circumstances should your compiled code ever call abort or exit".
+- All source code files (.h, .cpp) must be ASCII.
+
+Tools, tests and benchmarks are not held to these same strict rules.
+
+General Guidelines
+----------
+
+Contributors are encouraged to :
+
+- Document their changes. Though we do not enforce a rule regarding code comments, we prefer that non-trivial algorithms and techniques be somewhat documented in the code.
+- Follow as much as possible the existing code style. We do not enforce a specific code style, but we prefer consistency.
+- Modify as few lines of code as possible when working on an issue. The more lines you modify, the harder it is for your fellow human beings to understand what is going on.
+- Tools may report "problems" with the code, but we never delegate programming to tools: if there is a problem with the code, we need to understand it. Thus we will not "fix" code merely to please a static analyzer if we do not understand.
+- Provide tests for any new feature. We will not merge a new feature without tests.
+
+Pull Requests
+--------------
+
+Pull requests are always invited. However, we ask that you follow these guidelines:
+
+- It is wiser to discuss your ideas first as part of an issue before you start coding. If you omit this step and code first, be prepare to have your code receive scrutiny and be dropped.
+- Users should provide a rationale for their changes. Does it improve performance? Does it add a feature? Does it improve maintainability? Does fix a bug? This must be explicitly stated as part of the pull request. Do not propose changes based on taste or intuition. We do not delegate programming to tools: that some tool suggested a code change is not reason enough to change the code.
+   1. When your code improves performance, please document the gains with a benchmark using hard numbers.
+   2. If your code fixes a bug, please be either fix a failing test, or propose a new test.
+   3. Other types of changes must be clearly motivated. We openly discourage changes with no identifiable benefits.
+- Changes should be focused and minimal. You should change as few lines of code as possible. Please do not reformat or touch files needlessly.
+- New features must be accompanied of new tests, in general.
+- Your code should pass our continuous-integration tests. It is your responsability to ensure that your proposal pass the tests. We do not merge pull requests that would break our build.
+
+If the benefits of your proposed code remain unclear, we may choose to discard your code: that is not an insult, we frequently discard our own code. We may also consider various alternatives and choose another path. Again, that is not an insult or a sign that you have wasted your time.
+
+Code of Conduct
+---------------
+
+Though we do not have a formal code of conduct, we will not tolerate bullying, bigotry or
+intimidation. Everyone is welcome to contribute. If you have concerns, you can raise them privately with the core team members (e.g., D. Lemire, J. Keiser).
+
+We welcome contributions from women and less represented groups. If you need help, please reach out.
+
+Consider the following points when engaging with the project:
+
+- We discourage arguments from authority: ideas are discusssed on their own merits and not based on who stated it.
+- Be mindful that what you may view as an aggression is maybe merely a difference of opinion or a misunderstanding.
+- Be mindful that a collection of small aggressions, even if mild in isolation, can become harmful.
+
+Getting Started Hacking
+-----------------------
+
+An overview of simdjson's directory structure, with pointers to architecture and design
+considerations and other helpful notes, can be found at [HACKING.md](HACKING.md).

data/vendor/simdjson/CONTRIBUTORS

@@ -23,5 +23,17 @@ Chang Liu
 Sunny Gleason
 John Keiser
 Zach Bjornson
+Vitaly Baranov
+Juho Lauri
+Michael Eisel
+Io Daza Dillon
+Paul Dreik
+Jeremie Piotte
+Matthew Wilson
+Dušan Jovanović
+Matjaž Ostroveršnik
+Nong Li
+Furkan Taşkale
+Brendan Knapp
 # if you have contributed to the project and your name does not 
 # appear in this list, please let us know!

data/vendor/simdjson/Dockerfile

@@ -1,10 +1,88 @@
-# docker build -t simdjson . && docker run --privileged -t simdjson
-FROM gcc:8.3
-COPY . /usr/src/
-WORKDIR /usr/src/
-RUN make clean
-RUN make amalgamate
-RUN make
-RUN make test
-RUN make parsingcompetition
-CMD ["bash", "scripts/selectparser.sh"]
+###
+#
+# Though simdjson requires only commonly available compilers and tools, it can
+# be convenient to build it and test it inside a docker container: it makes it
+# possible to test and benchmark simdjson under even relatively out-of-date
+# Linux servers. It should also work under macOS and Windows, though not
+# at native speeds, maybe.
+#
+# Assuming that you have a working docker server, this file
+# allows you to build, test and benchmark simdjson.
+#
+#  We build the library and associated files in the dockerbuild subdirectory.
+# It may be necessary to delete it before creating the image:
+#
+# rm -r -f dockerbuild
+#
+# The need to delete the directory has nothing to do with docker per se: it is
+# simply cleaner in CMake to start from a fresh directory. This is important: if you
+# reuse the same directory with different configurations, you may get broken builds.
+#
+#
+# Then you can build the image as follows:
+#
+# docker build -t simdjson --build-arg USER_ID=$(id -u)  --build-arg GROUP_ID=$(id -g) .
+#
+# Please note that the image does not contain a copy of the code. However, the image will contain the
+# the compiler and the build system. This means that if you change the source code, after you have built
+# the image, you won't need to rebuild the image. In fact, unless you want to try a different compiler, you
+# do not need to ever rebuild the image, even if you do a lot of work on the source code.
+#
+# We specify the users to avoid having files owned by a privileged user (root) in our directory. Some
+# people like to run their machine as the "root" user. We do not think it is cool.
+#
+# Then you need to build the project:
+#
+# docker run  -v $(pwd):/project:Z  simdjson
+#
+# Should you change a source file, you may need to call this command again. Because the output
+# files are persistent between calls to this command (they reside in the dockerbuild directory),
+# this command can be fast.
+#
+# Next you can test it as follows:
+#
+# docker run -it -v $(pwd):/project:Z   simdjson sh -c "cd dockerbuild && ctest . --output-on-failure -E checkperf"
+#
+# The run the complete tests requires you to have built all of simdjson.
+#
+# Building all of simdjson takes a long time. Instead, you can build just one target:
+#
+# docker run -it -v $(pwd):/project:Z  simdjson sh -c "[ -d dockerbuild ] || mkdir dockerbuild && cd dockerbuild && cmake ..  && cmake --build . --target parse"
+#
+# Note that it is safe to remove dockerbuild before call the previous command, as the repository gets rebuild. It is also possible, by changing the command, to use a different directory name.
+#
+# You can run performance tests:
+#
+# docker run -it --privileged -v $(pwd):/project:Z  simdjson sh -c "cd dockerbuild && for i in ../jsonexamples/*.json; do echo \$i; ./benchmark/parse \$i;  done"
+#
+# The "--privileged" is recommended so you can get performance counters under Linux.
+#
+# You can also grab a fresh copy of simdjson and rebuild it, to make comparisons:
+#
+# docker run -it -v $(pwd):/project:Z  simdjson sh -c "git clone https://github.com/simdjson/simdjson.git && cd simdjson && mkdir build && cd build && cmake .. && cmake --build . --target parse "
+#
+# Then you can run comparisons:
+#
+# docker run -it --privileged -v $(pwd):/project:Z  simdjson sh -c "for i in jsonexamples/*.json; do echo \$i; dockerbuild/benchmark/parse \$i| grep GB| head -n 1; simdjson/build/benchmark/parse \$i | grep GB |head -n 1;  done"
+#
+####
+FROM ubuntu:20.10
+################
+# We would prefer to use the conan io images but they do not support 64-bit ARM? The small gcc images appear to
+# be broken on ARM.
+# Furthermore, we would not expect users to frequently rebuild the container, so using ubuntu is probably fine.
+###############
+ARG USER_ID
+ARG GROUP_ID
+RUN apt-get update -qq
+RUN DEBIAN_FRONTEND="noninteractive" apt-get -y install tzdata
+RUN apt-get install -y cmake g++ git
+RUN mkdir project
+
+RUN addgroup --gid $GROUP_ID user; exit 0
+RUN adduser --disabled-password --gecos '' --uid $USER_ID --gid $GROUP_ID user; exit 0
+USER user
+RUN gcc --version
+WORKDIR /project
+
+CMD ["sh","-c","[ -d dockerbuild ] || mkdir dockerbuild && cd dockerbuild && cmake .. && cmake --build . "]