Skip to content

Conversation

@joaoantoniocardoso
Copy link
Contributor

This PR depends on #483 , #481 and #476.

JPTIZ and others added 17 commits October 21, 2020 15:00
By creating so many build scripts, they must be maintained, which
considering the current scripts are batch-scripts it means it will
sometimes be too hard to fix/update them to get too little benefit.

There were two main purposes in having those scripts:
- Ensuring pre-build procedures (setting environment variables and
  running vcvars64) have been done.
- Setting windows-specific project option values, such as disabling
  wayland/x11 support and some Unix-specific EFL modules.

For the first one, after quite a lot of changes in the codebase, there's
only one environment variable to be set: CMAKE_TOOLCHAIN_FILE, which
must then be passed to -Dcmake_args project option to meson. This is now
done by creating a simple native-file with the cmake_args value on it,
so a script to check/define it is above overkill. About vcvars64, this
might be a simple "run vcvars64" (or "start a Develop Console from
Visual Studio") instruction in compile and installation guides.

For the second one, since meson 0.55 and further more on 0.56, there
were some serious updates on cross/native-file definitions, which now
fixes the issue mesonbuild/meson#6783 that was
the one that blocked EFL most from relying solely on native/cross-files.

Given these, there's no good reason left to keep relying on these
scripts, thus simplifying the build procedure a lot and making it more
reliable and customizable, since now we only depend on meson defaults
and not on another language (in this case, batch-script).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants