WIP: Solve meson warnings and deprecations #47

Draft
dimmus wants to merge 14 commits from dimmus/efl:devs/dimmus/meson into master
Contributor

Tested on meson 0.61.2 (ubuntu 20.04), 1.2.1 (Ubuntu 23.10).
Needs to be tested on other platforms (OS X, Windows).
Need more tests on linux platform as well.

Bug reports, notices and advices are wellcome!

Tested on meson 0.61.2 (ubuntu 20.04), 1.2.1 (Ubuntu 23.10). Needs to be tested on other platforms (OS X, Windows). Need more tests on linux platform as well. Bug reports, notices and advices are wellcome!
dimmus added 5 commits 2023-12-05 05:08:54 -08:00
First-time contributor

A lot of this isn't really necessary. Meson will log an informational notice but not escalate to a deprecation warning for things that you don't have the ability to change yet due to meson_version minimums support levels.

A lot of this isn't really necessary. Meson will log an informational notice but not escalate to a deprecation warning for things that you don't have the ability to change yet due to meson_version minimums support levels.
eschwartz requested changes 2023-12-05 06:06:04 -08:00
@ -39,21 +38,21 @@ foreach cmake_file : cmake_src
input: cmake_file+'Config.cmake.in',
output: cmake_file+'Config.cmake',
install_dir: join_paths(dir_lib, 'cmake', cmake_file),
copy: true,
configuration : conf
First-time contributor

In this case I would advise not using configure_file at all. It seems to have nothing to configure, so usong configuration: conf is "wrong" (newer meson actually wants you to use fs.copy()!!) but the purpose of either one is supposed to be for files that you need in the build directory. For installing files, just (rename them to avoid the useless .in and) use install_data() instead.

In this case I would advise not using configure_file at all. It seems to have nothing to configure, so usong configuration: conf is "wrong" (newer meson actually wants you to use fs.copy()!!) but the purpose of either one is supposed to be for files that you need in the build directory. For installing files, just (rename them to avoid the useless .in and) use install_data() instead.
Author
Contributor

caught it

caught it
@ -109,12 +109,12 @@ foreach text_filter_property : text_filter_properties
font = text_filter_property[1]
size = text_filter_property[2]
name = text_filter_property[3]
filter_code = run_command('cat', join_paths(meson.source_root(), 'src', 'examples', 'evas', 'filters', 'filter_'+name+'.lua'))
filter_code = run_command('cat', join_paths(source_root, 'src', 'examples', 'evas', 'filters', 'filter_'+name+'.lua'), check: false)
First-time contributor

There's a useful if/else you can do here: on new enough meson versions, use import('fs').read('../src/examples/......') for portability reasons.

There's a useful if/else you can do here: on new enough meson versions, use `import('fs').read('../src/examples/......')` for portability reasons.
Author
Contributor

A valuable remark, thanks

A valuable remark, thanks
Author
Contributor

but we have to set projects meson_version to >=0.57 to realize this

but we have to set projects meson_version to >=0.57 to realize this
@ -365,1 +364,4 @@
iconv = dependency('iconv', required: false)
if meson.version().version_compare('>=0.60')
iconv = dependency('iconv', method: 'auto')
else
iconv = dependency('iconv', required: false)
First-time contributor

If you're looking up iconv in both sides of the branch, what's the point? Just use dependency('', required: false) to get a null dependency.

If you're looking up iconv in both sides of the branch, what's the point? Just use `dependency('', required: false)` to get a null dependency.
Author
Contributor

It is a try to fight with the warning:
* 0.60.0: {'dep 'iconv' custom lookup'}

It is a try to fight with the warning: ` * 0.60.0: {'dep 'iconv' custom lookup'}`
First-time contributor

The thing is that you are still hitting the bad codepath for older versions of meson...

The thing is that you are still hitting the bad codepath for older versions of meson...
Author
Contributor

Would be very appreciated if you could provide a link to the example with the novel meson coding approach.

Would be very appreciated if you could provide a link to the example with the novel meson coding approach.
Author
Contributor

Hi, Eli. Thanks a lot. Valuable as usual.

Hi, Eli. Thanks a lot. Valuable as usual.
dimmus added 1 commit 2023-12-06 06:16:36 -08:00
bd12bf23e7
meson: revert commented 'fork' header
Noticed that with defined HAVE_FORK we have a lot of timeouts in tests. Commented 'fork' solves this. Tried #undef in efl_check.h as well. Experiments to be continued.
dimmus added 8 commits 2023-12-22 04:41:39 -08:00
This pull request has changes conflicting with the target branch.
  • src/tests/elementary/meson.build
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b dimmus-devs/dimmus/meson master
git pull devs/dimmus/meson

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff dimmus-devs/dimmus/meson
git push origin master
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: enlightenment/efl#47
No description provided.