Package Details: dexed 0.9.4-4

Git Clone URL: https://aur.archlinux.org/dexed.git (read-only)
Package Base: dexed
Description: A software synth closely modelled on the Yamaha DX7
Upstream URL: http://asb2m10.github.io/dexed/
Licenses: GPL3
Groups: vst-plugins
Submitter: SpotlightKid
Maintainer: SpotlightKid
Last Packager: SpotlightKid
Votes: 6
Popularity: 1.148537
First Submitted: 2018-03-24 00:10
Last Updated: 2018-08-14 21:19

Latest Comments

« First ‹ Previous 1 2

SpotlightKid commented on 2018-04-26 13:11

@io7m: Sorry, I can't reproduce the error you get. I reinstalled the normal juce AUR package and rebuild this package with makepkg. I also tried building with trizen. Both times the package was built successfully.

I admit, I don't know much about how .jucer files are supposed to work, so maybe those outdated paths are a problem. I suggest you try commenting out lines 23-27 in the PKGBUILD and see if the build still fails. If yes, this should be reported upstream.

SpotlightKid commented on 2018-04-25 17:42

I just noticed that I have installed a custom PKGBUILD for juce. I'll try to reproduce the error with the normal juce AUR package. In the meantime, if you want, you can try my PKGBUILD: https://gist.github.com/SpotlightKid/a5db04ea9c259ea57b3ea72719b23c57

io7m commented on 2018-04-25 16:58

yaourt -G dexed; cd dexed; makepkg leads to the exact same error, unfortunately.

SpotlightKid commented on 2018-04-25 15:55

@io7m: can you try and confirm whether it builds on your system with plain makepkg (e.g. "yaourt -G dexed; cd dexed; makepkg")?

io7m commented on 2018-04-25 15:07

Hello.

Seem to be having trouble building this:

==> Making package: dexed 0.9.4-2 (Wed 25 Apr 16:06:17 BST 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found dexed-0.9.4.tar.gz
  -> Found dexed.desktop
==> Validating source files with md5sums...
    dexed-0.9.4.tar.gz ... Passed
    dexed.desktop ... Passed
==> Extracting sources...
  -> Extracting dexed-0.9.4.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
  -> Building Dexed stand-alone...
JUCE v5.3.0

**********************************************************
Projucer 5.3.0  ---  Build date: Apr 25 2018
Log started: 25 Apr 2018 4:06:18pm

Linux
CPU: 2513MHz  Cores: 4  14010MB
Loading project: /tmp/trizen-rm/dexed/src/dexed-0.9.4/Dexed.jucer
Re-saving file: /tmp/trizen-rm/dexed/src/dexed-0.9.4/Dexed.jucer
Error when saving: At least one of your JUCE module paths is invalid!
Please go to the Modules settings page and ensure each path points to the correct JUCE modules folder.

==> ERROR: A failure occurred in build().
    Aborting...

This is building using trizen. I see some relative paths in Dexed.jucer: Is it possible that the build script is making some assumptions about where things will be (and those assumptions are violated depending on which AUR frontend tool you're using)?

SpotlightKid commented on 2018-03-31 18:26

Heads up: unfortunately the Dexed VST plugin does not work on Linux in release 0.9.4. I've filed a bug in Dexed's Github issue tracker. Until this is resolved I can only recommend to return to release 0.9.3 if you need the VST plugin. The new standalone version in release 0.9.4 seems to work ok, though.

Here's a PKGBUILD, which you can use for version 0.9.3:

https://gist.github.com/SpotlightKid/c0e8abec8af3686d5495b5dfd2b7c399