Arch Linux User Repository

@tiko: Fixed.

Got this error when building

tiko@stella ~ $ yay -S viper4linux-gui-git
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  viper4linux-gui-git-2.2.r14.g034f3fe-1

  1 viper4linux-gui-git              (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: PKGBUILD up to date, Skipping (1/0): viper4linux-gui-git
  1 viper4linux-gui-git              (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: (1/1) Parsing SRCINFO: viper4linux-gui-git
==> Making package: viper4linux-gui-git 2.2.r14.g034f3fe-1 (Kam 02 Jun 2022 09:49:29 )
==> Retrieving sources...
  -> Updating viper4linux-gui git repo...
Fetching origin
  -> Found viper4linux-gui.desktop
==> Validating source files with sha256sums...
    viper4linux-gui ... Skipped
    viper4linux-gui.desktop ... Passed
==> Making package: viper4linux-gui-git 2.2.r14.g034f3fe-1 (Kam 02 Jun 2022 09:49:32 )
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating viper4linux-gui git repo...
Fetching origin
  -> Found viper4linux-gui.desktop
==> Validating source files with sha256sums...
    viper4linux-gui ... Skipped
    viper4linux-gui.desktop ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of viper4linux-gui git repo...
Cloning into 'viper4linux-gui'...
done.
==> Starting pkgver()...
==> Updated version: viper4linux-gui-git 2.2.r24.g2d0c84d-1
==> Sources are ready.
==> Making package: viper4linux-gui-git 2.2.r24.g2d0c84d-1 (Kam 02 Jun 2022 09:49:37 )
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Usage: qmake-qt5 [mode] [options] [files]

QMake has two modes, one mode for generating project files based on
some heuristics, and the other for generating makefiles. Normally you
shouldn't need to specify a mode, as makefile generation is the default
mode for qmake, but you may use this to test qmake on an existing project

Mode:
  -project       Put qmake into project file generation mode
                 In this mode qmake interprets [files] as files to
                 be added to the .pro file. By default, all files with
                 known source extensions are added.
                 Note: The created .pro file probably will 
                 need to be edited. For example add the QT variable to 
                 specify what modules are required.
  -makefile      Put qmake into makefile generation mode (default)
                 In this mode qmake interprets files as project files to
                 be processed, if skipped qmake will try to find a project
                 file in your current working directory

Warnings Options:
  -Wnone         Turn off all warnings; specific ones may be re-enabled by
                 later -W options
  -Wall          Turn on all warnings
  -Wparser       Turn on parser warnings
  -Wlogic        Turn on logic warnings (on by default)
  -Wdeprecated   Turn on deprecation warnings (on by default)

Options:
   * You can place any variable assignment in options and it will be *
   * processed as if it was in [files]. These assignments will be    *
   * processed before [files] by default.                            *
  -o file        Write output to file
  -d             Increase debug level
  -t templ       Overrides TEMPLATE as templ
  -tp prefix     Overrides TEMPLATE so that prefix is prefixed into the value
  -help          This help
  -v             Version information
  -early         All subsequent variable assignments will be
                 parsed right before default_pre.prf
  -before        All subsequent variable assignments will be
                 parsed right before [files] (the default)
  -after         All subsequent variable assignments will be
                 parsed after [files]
  -late          All subsequent variable assignments will be
                 parsed right after default_post.prf
  -norecursive   Don't do a recursive search
  -recursive     Do a recursive search
  -set <prop> <value> Set persistent property
  -unset <prop>  Unset persistent property
  -query <prop>  Query persistent property. Show all if <prop> is empty.
  -qtconf file   Use file instead of looking for qt.conf
  -cache file    Use file as cache           [makefile mode only]
  -spec spec     Use spec as QMAKESPEC       [makefile mode only]
  -nocache       Don't use a cache file      [makefile mode only]
  -nodepend      Don't generate dependencies [makefile mode only]
  -nomoc         Don't generate moc targets  [makefile mode only]
  -nopwd         Don't look for files in pwd [project mode only]
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: viper4linux-gui-git

@toxygen: What error? It builds fine for me.

seems like the target is still needed with qmake-qt5, I get an error without any target like current PKGBUILD, but adding

V4L_Frontend.pro \ QMAKE_CFLAGS="$CFLAGS" \ QMAKE_CXXFLAGS="$CXXFLAGS" \ QMAKE_LFLAGS="$LDFLAGS"

works to build the package

@toxygen: Thanks, it's fixed. I updated both packages, apparently I forgot to test this one.

looks like PKGBUILD changed

qmake V4L_Frontend.pro

to

qmake

and fails to build without it