diff options
author | Jussi Pakkanen <jpakkane@gmail.com> | 2018-07-02 20:50:56 +0300 |
---|---|---|
committer | Jussi Pakkanen <jpakkane@gmail.com> | 2018-07-02 20:50:56 +0300 |
commit | 5d0821946404322152319f7f2b22b96477ac406e (patch) | |
tree | f238fa0696173e838585a17cf490e208cd14b825 /docs/markdown/snippets | |
parent | 1c44afdeed636f90a1e2685cba4143eacde21887 (diff) | |
download | meson-5d0821946404322152319f7f2b22b96477ac406e.zip meson-5d0821946404322152319f7f2b22b96477ac406e.tar.gz meson-5d0821946404322152319f7f2b22b96477ac406e.tar.bz2 |
Update everything for new release.0.47.0
Diffstat (limited to 'docs/markdown/snippets')
19 files changed, 0 insertions, 246 deletions
diff --git a/docs/markdown/snippets/armclang-cross.md b/docs/markdown/snippets/armclang-cross.md deleted file mode 100644 index f787876..0000000 --- a/docs/markdown/snippets/armclang-cross.md +++ /dev/null @@ -1,25 +0,0 @@ -## ARM compiler(version 6) for C and CPP - -Cross-compilation is now supported for ARM targets using ARM compiler version 6 - ARMCLANG. -The required ARMCLANG compiler options for building a shareable library are not included in the -current Meson implementation for ARMCLANG support, so it can not build shareable libraries. -This current Meson implementation for ARMCLANG support can not build assembly files with -arm syntax(we need to use armasm instead of ARMCLANG for the .s files with this syntax) -and only supports gnu syntax. -The default extension of the executable output is .axf. -The environment path should be set properly for the ARM compiler executables. -The '--target', '-mcpu' options with the appropriate values should be mentioned -in the cross file as shown in the snippet below. - -``` -[properties] -c_args = ['--target=arm-arm-none-eabi', '-mcpu=cortex-m0plus'] -cpp_args = ['--target=arm-arm-none-eabi', '-mcpu=cortex-m0plus'] - -``` - -Note: -- The current changes are tested on Windows only. -- PIC support is not enabled by default for ARM, - if users want to use it, they need to add the required arguments - explicitly from cross-file(c_args/c++_args) or some other way. diff --git a/docs/markdown/snippets/bitcode_support.md b/docs/markdown/snippets/bitcode_support.md deleted file mode 100644 index a0d7ad9..0000000 --- a/docs/markdown/snippets/bitcode_support.md +++ /dev/null @@ -1,15 +0,0 @@ -## New base build option for LLVM (Apple) bitcode support - -When building with clang on macOS, you can now build your static and shared -binaries with embedded bitcode by enabling the `b_bitcode` [base -option](Builtin-options.md#Base_options) by passing `-Db_bitcode=true` to -Meson. - -This is better than passing the options manually in the environment since Meson -will automatically disable conflicting options such as `b_asneeded`, and will -disable bitcode support on targets that don't support it such as -`shared_module()`. - -Since this requires support in the linker, it is currently only enabled when -using Apple ld. In the future it can be extended to clang on other platforms -too. diff --git a/docs/markdown/snippets/compiler_check_header.md b/docs/markdown/snippets/compiler_check_header.md deleted file mode 100644 index 8981d13..0000000 --- a/docs/markdown/snippets/compiler_check_header.md +++ /dev/null @@ -1,12 +0,0 @@ -## New compiler check: check_header() - -The existing compiler check `has_header()` only checks if the header exists, -either with the `__has_include` C++11 builtin, or by running the pre-processor. - -However, sometimes the header you are looking for is unusable on some platforms -or with some compilers in a way that is only detectable at compile-time. For -such cases, you should use `check_header()` which will include the header and -run a full compile. - -Note that `has_header()` is much faster than `check_header()`, so it should be -used whenever possible. diff --git a/docs/markdown/snippets/configure_file_copy.md b/docs/markdown/snippets/configure_file_copy.md deleted file mode 100644 index fee04e4..0000000 --- a/docs/markdown/snippets/configure_file_copy.md +++ /dev/null @@ -1,10 +0,0 @@ -## New action 'copy' for configure_file() - -In addition to `configuration:` and `command:`, -[`configure_file()`](#Reference-manual.md#configure_file) now accepts a keyword -argument `copy:` which specifies a new action: copying the file specified with -the `input:` keyword argument to a file in the build directory with the name -specified with the `output:` keyword argument. - -These three keyword arguments are, as before, mutually exclusive. You can only -do one action at a time. diff --git a/docs/markdown/snippets/configure_file_encoding.md b/docs/markdown/snippets/configure_file_encoding.md deleted file mode 100644 index 8082177..0000000 --- a/docs/markdown/snippets/configure_file_encoding.md +++ /dev/null @@ -1,12 +0,0 @@ -## New encoding keyword for configure_file - -Add a new keyword to [`configure_file()`](#Reference-manual.md#configure_file) -that allows the developer to specify the input and output file encoding. - -If the file encoding of the input is not UTF-8 meson can crash (see #1542). -A crash as with UTF-16 is the best case and the worst meson will silently -corrupt the output file for example with ISO-2022-JP. For additional details -see pull request #3135. - -The new keyword defaults to UTF-8 and the documentation strongly suggest to -convert the file to UTF-8 when possible. diff --git a/docs/markdown/snippets/configure_file_output_format.md b/docs/markdown/snippets/configure_file_output_format.md deleted file mode 100644 index e522885..0000000 --- a/docs/markdown/snippets/configure_file_output_format.md +++ /dev/null @@ -1,14 +0,0 @@ -## New keyword argument `output_format` for configure_file() - -When called without an input file, `configure_file` generates a -C header file by default. A keyword argument was added to allow -specifying the output format, for example for use with nasm or yasm: - -``` -conf = configuration_data() -conf.set('FOO', 1) - -configure_file('config.asm', - configuration: conf, - output_format: 'nasm') -``` diff --git a/docs/markdown/snippets/custom-target-depends.md b/docs/markdown/snippets/custom-target-depends.md deleted file mode 100644 index e2b2ed7..0000000 --- a/docs/markdown/snippets/custom-target-depends.md +++ /dev/null @@ -1,4 +0,0 @@ -## Substitutions in `custom_target(depends:)` - -The `depfile` keyword argument to `custom_target` now accepts the `@BASENAME@` -and `@PLAINNAME@` substitutions. diff --git a/docs/markdown/snippets/deprecate_build_always.md b/docs/markdown/snippets/deprecate_build_always.md deleted file mode 100644 index d6e54b5..0000000 --- a/docs/markdown/snippets/deprecate_build_always.md +++ /dev/null @@ -1,12 +0,0 @@ -## Deprecate `build_always` - -Setting `build_always` to `true` for a custom target not only marks the target -to be always considered out of date, but also adds it to the set of default -targets. This option is therefore deprecated and the new option -`build_always_stale` is introduced. - -`build_always_stale` *only* marks the target to be always considered out of -date, but does not add it to the set of default targets. The old behaviour can -be achieved by combining `build_always_stale` with `build_by_default`. - -The documentation has been updated accordingly. diff --git a/docs/markdown/snippets/dict_builtin.md b/docs/markdown/snippets/dict_builtin.md deleted file mode 100644 index 1bd24ce..0000000 --- a/docs/markdown/snippets/dict_builtin.md +++ /dev/null @@ -1,19 +0,0 @@ -## New built-in object dictionary - -Meson dictionaries use a syntax similar to python's dictionaries, -but have a narrower scope: they are immutable, keys can only -be string literals, and initializing a dictionary with duplicate -keys causes a fatal error. - -Example usage: - -```meson -dict = {'foo': 42, 'bar': 'baz'} - -foo = dict.get('foo') -foobar = dict.get('foobar', 'fallback-value') - -foreach key, value : dict - Do something with key and value -endforeach -``` diff --git a/docs/markdown/snippets/empty-array-opts.md b/docs/markdown/snippets/empty-array-opts.md deleted file mode 100644 index 6d3b05d..0000000 --- a/docs/markdown/snippets/empty-array-opts.md +++ /dev/null @@ -1,5 +0,0 @@ -## Array options treat -Dopt= and -Dopt=[] as equivalent - -Prior to this change passing -Dopt= to an array opt would be interpreted as -[''] (an array with an empty string), now -Dopt= is the same as -Dopt=[], an -empty list. diff --git a/docs/markdown/snippets/feature_new.md b/docs/markdown/snippets/feature_new.md deleted file mode 100644 index 94fb880..0000000 --- a/docs/markdown/snippets/feature_new.md +++ /dev/null @@ -1,32 +0,0 @@ -## Feature detection based on meson_version in project() - -Meson will now print a `WARNING:` message during configuration if you use -a function or a keyword argument that was added in a meson version that's newer -than the version specified inside `project()`. For example: - -```meson -project('featurenew', meson_version: '>=0.43') - -cdata = configuration_data() -cdata.set('FOO', 'bar') -message(cdata.get_unquoted('FOO')) -``` - -This will output: - -``` -The Meson build system -Version: 0.47.0.dev1 -Source dir: C:\path\to\srctree -Build dir: C:\path\to\buildtree -Build type: native build -Project name: featurenew -Project version: undefined -Build machine cpu family: x86_64 -Build machine cpu: x86_64 -WARNING: Project targetting '>=0.43' but tried to use feature introduced in '0.44.0': configuration_data.get_unquoted() -Message: bar -Build targets in project: 0 -WARNING: Project specifies a minimum meson_version '>=0.43' which conflicts with: - * 0.44.0: {'configuration_data.get_unquoted()'} -``` diff --git a/docs/markdown/snippets/feature_options.md b/docs/markdown/snippets/feature_options.md deleted file mode 100644 index 22d9201..0000000 --- a/docs/markdown/snippets/feature_options.md +++ /dev/null @@ -1,10 +0,0 @@ -## New feature option type - -A new type of option can be defined in `meson_options.txt` for the traditional -`enabled / disabled / auto` tristate. The value of this option can be passed to -the `required` keyword argument of functions `dependency()`, `find_library()`, -`find_program()` and `add_languages()`. - -A new global option `auto_features` has been added to override the value of all -`auto` features. It is intended to be used by packagers to have full control on -which feature must be enabled or disabled. diff --git a/docs/markdown/snippets/gdbus_codegen_options.md b/docs/markdown/snippets/gdbus_codegen_options.md deleted file mode 100644 index d3dd84c..0000000 --- a/docs/markdown/snippets/gdbus_codegen_options.md +++ /dev/null @@ -1,14 +0,0 @@ -## New options to gnome.gdbus_codegen - -You can now pass additional arguments to gdbus-codegen using the `extra_args` -keyword. This is the same for the other gnome function calls. - -Meson now automatically adds autocleanup support to the generated code. This -can be modified by setting the autocleanup keyword. - -For example: - - sources += gnome.gdbus_codegen('com.mesonbuild.Test', - 'com.mesonbuild.Test.xml', - autocleanup : 'none', - extra_args : ['--pragma-once']) diff --git a/docs/markdown/snippets/install_command.md b/docs/markdown/snippets/install_command.md deleted file mode 100644 index 68866c9..0000000 --- a/docs/markdown/snippets/install_command.md +++ /dev/null @@ -1,12 +0,0 @@ -## Made install a top level Meson command - -You can now run `meson install` in your build directory and it will do -the install. It has several command line options you can toggle the -behaviour that is not in the default `ninja install` invocation. This -is similar to how `meson test` already works. - -For example, to install only the files that have changed, you can do: - -```console -meson install --only-changed -``` diff --git a/docs/markdown/snippets/install_mode-extended.md b/docs/markdown/snippets/install_mode-extended.md deleted file mode 100644 index b0ee4c3..0000000 --- a/docs/markdown/snippets/install_mode-extended.md +++ /dev/null @@ -1,8 +0,0 @@ -## install_mode argument extended to all installable targets - -It is now possible to pass an install_mode argument to all installable targets, -such as executable(), libraries, headers, man pages and custom/generated -targets. - -The install_mode argument can be used to specify the file mode in symbolic -format and optionally the owner/uid and group/gid for the installed files. diff --git a/docs/markdown/snippets/install_umask.md b/docs/markdown/snippets/install_umask.md deleted file mode 100644 index b3a2427..0000000 --- a/docs/markdown/snippets/install_umask.md +++ /dev/null @@ -1,17 +0,0 @@ -## New built-in option install_umask with a default value 022 - -This umask is used to define the default permissions of files and directories -created in the install tree. Files will preserve their executable mode, but the -exact permissions will obey the install_umask. - -The install_umask can be overridden in the meson command-line: - - $ meson --install-umask=027 builddir/ - -A project can also override the default in the project() call: - - project('myproject', 'c', - default_options : ['install_umask=027']) - -To disable the install_umask, set it to 'preserve', in which case permissions -are copied from the files in their origin. diff --git a/docs/markdown/snippets/integer-base.md b/docs/markdown/snippets/integer-base.md deleted file mode 100644 index 0a27c9a..0000000 --- a/docs/markdown/snippets/integer-base.md +++ /dev/null @@ -1,9 +0,0 @@ -## Octal and binary string literals - -Octal and binary integer literals can now be used in build and option files. - -```meson -int_493 = 0o755 -int_1365 = 0b10101010101 -``` - diff --git a/docs/markdown/snippets/run_command_check.md b/docs/markdown/snippets/run_command_check.md deleted file mode 100644 index 35bdcdd..0000000 --- a/docs/markdown/snippets/run_command_check.md +++ /dev/null @@ -1,9 +0,0 @@ -## New keyword arguments: 'check' and 'capture' for run_command() - -If `check:` is `true`, then the configuration will fail if the command returns a -non-zero exit status. The default value is `false` for compatibility reasons. - -`run_command()` used to always capture the output and stored it for use in -build files. However, sometimes the stdout is in a binary format which is meant -to be discarded. For that case, you can now set the `capture:` keyword argument -to `false`. diff --git a/docs/markdown/snippets/windows-resources-dependencies.md b/docs/markdown/snippets/windows-resources-dependencies.md deleted file mode 100644 index e061778..0000000 --- a/docs/markdown/snippets/windows-resources-dependencies.md +++ /dev/null @@ -1,7 +0,0 @@ -## Windows resource files dependencies - -The `compile_resources()` function of the `windows` module now takes -the `depend_files:` and `depends:` keywords. - -When using binutils's `windres`, dependencies on files `#include`'d by the -preprocessor are now automatically tracked. |