refactor: Move Meson build targets to top level directory #530
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes the Meson build generate targets more closely to the CMake build. Instead of building targets in src/nanoarrow this makes it so it builds things in the build directory root
The only exception is the "nanoarrow_config.h" file which gets built to
<build_directory>/src
. The CMake installation creates a separategenerated
directory, but Meson practically limits the structure of your build folder to how themeson.build
files are laid out in source. We could create agenerated
directory in the source if we so cared, or alternately could try to change the include to#include <nanoarrow/nanoarrow_config.>
for consistency with all other includes, placing that generated target in the same directory as the rest of the headers