January 20, 2022, 08:03:19 PM

News:

--


Script Error: Exception: (_tp_dict_get) KeyError: splitext

Started by Grim Reaper, January 11, 2022, 09:15:22 PM

Previous topic - Next topic

Grim Reaper

January 14, 2022, 12:47:16 AM #15 Last Edit: January 14, 2022, 12:54:35 AM by Grim Reaper
It won't make the MacOS .dmg install package. It can't find qmake or an executable file that uses it to do that. Is there a way to link to it so it will be found?

I have standalone Cmake.app installed, can the .dmg install package be made with that?

eumagga0x2a

Quote from: Grim Reaper on January 14, 2022, 12:47:16 AMIt won't make the MacOS .dmg install package. It can't find qmake or an executable file that uses it to do that. Is there a way to link to it so it will be found?

The bootstrap script aborts early because qmake from Qt is not in $PATH. This has nothing to do with linking. Have you installed qt@5 in Homebrew?

Quote from: Grim Reaper on January 14, 2022, 12:47:16 AMI have standalone Cmake.app installed, can the .dmg install package be made with that?

Never tried. Please use the one supplied by Homebrew.

Grim Reaper

January 14, 2022, 05:31:04 PM #17 Last Edit: January 14, 2022, 06:14:46 PM by Grim Reaper
Yes, QT@5 is installed.

I tried to build the installer again, it failed with this:

-- Checking for module 'libass'
--   No package 'libass' found
CMake Error at /usr/local/Cellar/cmake/3.22.1/share/cmake/Modules/FindPkgConfig.cmake:603 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.22.1/share/cmake/Modules/FindPkgConfig.cmake:825 (_pkg_check_modules_internal)
  CMakeLists.txt:81 (PKG_CHECK_MODULES)

-- Configuring incomplete, errors occurred!
See also "/Users/admin1/avidemux2/buildPluginsCommon/CMakeFiles/CMakeOutput.log".
+ fail cmakeZ
+ echo '** Failed at cmakeZ**'
** Failed at cmakeZ**
+ exit 1
Admins-Mac-mini:avidemux2 admin1$



I ran this:

pkg-config --exists --print-errors libass

This is the result:

Admins-Mac-mini:avidemux2 admin1$ pkg-config --exists --print-errors libass
Package libass was not found in the pkg-config search path.
Perhaps you should add the directory containing `libass.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libass' found
Admins-Mac-mini:avidemux2 admin1$

How do I "add the directory containing `libass.pc'
to the PKG_CONFIG_PATH environment variable"?



eumagga0x2a

You misread the error. The build fails because cmake (again) doesn't find pkg-config. What does

which pkg-config
report? Maybe you have another pkg-config executable somewhere higher in the $PATG which eclipses the one from Homebrew?

eumagga0x2a

I should have mentioned that the fact that cmake was searching for libass means that the Avidemux Qt GUI executable and libs had been built successfully.

Grim Reaper

This is the output of 'which pkg-config':

Admins-Mac-mini:~ admin1$ which pkg-config
/usr/local/bin/pkg-config
Admins-Mac-mini:~ admin1$

eumagga0x2a


eumagga0x2a

I think I was wrong, my apologies. On macOS, when building Avidemux with external libass,libass is indeed marked as required package. Thus it may be really libass which pkg-config fails to find which in turn triggers build failure in common plugins.

eumagga0x2a

Additionally to the question about the target of pkg-config symlink in /usr/local/bin, please post the output of

brew ls -v libass
brew ls -v pkg-config
pkg-config --libs libass

Grim Reaper

January 14, 2022, 08:54:13 PM #24 Last Edit: January 14, 2022, 09:16:15 PM by Grim Reaper
This is the output:


Admins-Mac-mini:~ admin1$ ls -l /usr/local/bin/pkg-config
lrwxr-xr-x  1 admin1  admin  44 14 Jan 12:53 /usr/local/bin/pkg-config -> ../Cellar/pkg-config/0.29.2_3/bin/pkg-config
Admins-Mac-mini:~ admin1$

I ran the Avidemux2.8.app from the Avidemux2 folder and the GUI opens and a file can be selected from 'Open' but nothing else works. I suppose that's because the files such as the modules, etc., aren't installed. I also saw that saving a project and selecting a project are not available in the 'File' list.

Attached is a pdf of the Avidemux2 folder contents.You cannot see attachments on this board.

eumagga0x2a

Quote from: Grim Reaper on January 14, 2022, 08:54:13 PMls -l /usr/local/bin/pkg-config
lrwxr-xr-x  1 admin1  admin  44 14 Jan 12:53 /usr/local/bin/pkg-config -> ../Cellar/pkg-config/0.29.2_3/bin/pkg-config

So far so good, please post the output of the other commands.

.pc files in Homebrew are by default symlinked into /usr/local/lib/pkgconfig where pkg-config expects them.

Quote from: Grim Reaper on January 14, 2022, 08:54:13 PMI ran the Avidemux2.8.app from the Avidemux2 folder and the GUI opens and a file can be selected from 'Open' but nothing else works. I suppose that's because the files such as the modules, etc., aren't installed. I also saw that saving a project and selecting a project are not available in the 'Open' list.

Yes, this is the reason as script engines (actually just tinyPy) and all demuxers are plugins.

eumagga0x2a

Quote from: Grim Reaper on January 14, 2022, 08:54:13 PMAttached is a pdf of the Avidemux2 folder contents

This is irrelevant at the current point, please provide the requested info.

Grim Reaper

Here is the output:

Admins-Mac-mini:~ admin1$ ls -l /usr/local/bin/pkg-config
lrwxr-xr-x  1 admin1  admin  44 14 Jan 12:53 /usr/local/bin/pkg-config -> ../Cellar/pkg-config/0.29.2_3/bin/pkg-config
Admins-Mac-mini:~ admin1$ lrwxr-xr-x  1 admin1  admin  44 14 Jan 12:53 /usr/local/bin/pkg-config -> ../Cellar/pkg-config/0.29.2_3/bin/pkg-config
-bash: ../Cellar/pkg-config/0.29.2_3/bin/pkg-config: No such file or directory
Admins-Mac-mini:~ admin1$

Attached is a pdf of the contents of the Avidemux2 folder You cannot see attachments on this board.

eumagga0x2a

Please re-read https://avidemux.org/smif/index.php/topic,19757.msg93161.html#msg93161 regarding requested info, but juding from your replies, I guess it doesn't make sense to continue this topic, at least tonight.

Grim Reaper

Attached is a pdf file containing the results of the 4 file queries you asked for. I couldn't post them normally because the text content is considered to be spam. You cannot see attachments on this board.