I did the following instruction.
```console
% PKG_CONFIG_PATH=$(brew --prefix libffi)/lib/pkgconfig:$PKG_CONFIG_PATH meson
build -Darrow_cpp_build_dir=$PWD/../cpp/debug -Darrow_cpp_build_type=debug
```
I got the following result.
```
% PKG_CONFIG_PATH=$(brew --prefix libffi)/lib/pkgconfig:$PKG_CONFIG_PATH meson
build -Darrow_cpp_build_dir=$PWD/../cpp/debug -Darrow_cpp_build_type=debug
The Meson build system
Version: 0.47.2
Source dir: /Users/shiro/arrow/c_glib
Build dir: /Users/shiro/arrow/c_glib/build
Build type: native build
Project name: arrow-glib
Project version: undefined
Native C compiler: ccache cc (clang 9.0.0 "Apple LLVM version 9.0.0
(clang-900.0.38)")
Native C++ compiler: ccache c++ (clang 9.0.0 "Apple LLVM version 9.0.0
(clang-900.0.38)")
Build machine cpu family: x86_64
Build machine cpu: x86_64
meson.build:68:2: ERROR: Tried to form an absolute path to a source dir. You
should not do that but use
relative paths instead.
To get include path to any directory relative to the current dir do
incdir = include_directories(dirname)
After this incdir will contain both the current source dir as well as the
corresponding build dir. It can then be used in any subdirectory and
Meson will take care of all the busywork to make paths work.
Dirname can even be '.' to mark the current directory. Though you should
remember that the current source and build directories are always
put in the include directories by default so you only need to do
include_directories('.') if you intend to use the result in a
different subdirectory.
```
Do we need to specify relative paths on this line? Or is there a mistake in
specifying options?
[ Full content available at: https://github.com/apache/arrow/pull/2600 ]
This message was relayed via gitbox.apache.org for [email protected]
