cannot build with meson

[Cyclone-S]

Describe the bug
I installed meson however I get an error when i type "meson --version" The error says

`
meson : The term 'meson' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

• meson --version

•   + CategoryInfo          : ObjectNotFound: (meson:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  

`

system parameters
meson-1.8.3
Ninja version 1.10.2
Python 3.6.2

[eli-schwartz]

How did you try installing?

[Cyclone-S]

Hi,

I used this in the console

"pip3 install meson"

[eli-schwartz]

Usually pip3 install will print a message such as:

  WARNING: The script meson is installed in '/some/venv/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.

If you saw such a warning, please add that directory to the windows %PATH%.

There is also an MSI installer at https://github.com/mesonbuild/meson/releases/tag/1.8.2 which does not need a separate Python. Maybe @jpakkane knows why there isn't one for 1.8.3...

[Cyclone-S]

yes i came across that error message. how do i add that path?

Also running that msi file, windows said it could be a virus....

[eli-schwartz]

If I upload that file to virustotal: https://www.virustotal.com/gui/file/073aa91e3f716cd49f1f37adbc767cad5a62ff4f3780c07838054aa93a23363f

2/50 security vendors flagged this file as malicious -- this is pretty good odds that it's safe. The two failures:

• Fortinet : W32/PossibleThreat
• Sangfor Engine Zero : Trojan.Win32.Save.a

They aren't even the usual vendors. Many big names say it's safe, including Microsoft, Malwarebytes, Kaspersky, AVG...

The issue is that Python software using pyinstaller/pyinstaller#6754 looks similar to each other because of how they ship Python, so as long as one software in the world uses PyInstaller to package a malicious virus written in Python, some antiviruses will report all PyInstaller based packages as "possibly a virus" and there is very little we can do about it.

You'll need to make your own evaluation of what antivirus you trust. It's a tough topic.

...

As far as adding PATH goes, I'm not a windows user but from a quick google I found https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/

[Cyclone-S]

ok. meson is now detected but I get an error when running it. See console image.

[Cyclone-S]

yes here is the other build file.
meson.build.txt

It already has the code you mentioned above

[eli-schwartz]

It has:

dep_png    = dependency('libpng')

I suggested:

dep_png    = dependency('libpng', 'PNG')

The additional 'PNG' is a fallback name in case libpng is installed but only with cmake-style config files. Meson can read those too, but it needs to know that both names are the same.

[eli-schwartz]

As another point, I noticed: dep_dkcomp = dependency('dkcomp', fallback: ['dkcomp', 'depdkcomp'])

As you already use subprojects, you can run: meson wrap install libpng and it will install the file subprojects/libpng.wrap into your project. This file knows how to build libpng for you directly via Meson, if no system copy is available. See https://mesonbuild.com/Wrapdb-projects.html for details.

[Cyclone-S]

It seems to have installed the libpng using the code you posted but I still get the same errors.
I came across this with a google search,

pkg-config Issues:
If CMake is trying to use pkg-config to find libpng, ensure pkg-config is correctly configured and that the .pc file for libpng is accessible in the PKG_CONFIG_PATH.

[Cyclone-S]

ok, I got a little closer. It no longer gives me a pkg error. However it still says it can't fined the subproject folder or the png.wrap files.