Bug #535

3rd party externals are not included in Windows installer

Added by Trond Lossius over 9 years ago. Updated over 6 years ago.

Status:ClosedStart date:2010-06-09
Priority:HighDue date:
Assignee:Adrian Gierakowski% Done:

100%

Category:-Estimated time:1.00 hour
Target version:(Jamoma Platform) - Windows ManagementSpent time:1.00 hour
Branch: OS:Windows

Description

So e.g. ambimonitor is missing. Didn't find a link to download separately on the download website

JamomaDependencies-0.5.4-rc1.msi (3.08 MB) Adrian Gierakowski, 2011-11-01 09:52 pm

History

#1 Updated by Julien Rabin over 9 years ago

Trond Lossius wrote:

Didn't find a link to download separately on the download website

My fault. Given the dependencies are now included in the Mac installer, I removed the link, thinking it was now useless.

Do the dependencies still have to be downloaded separately on Windows or should this particular external be included in the Windows distri ?

It is probably a good idea to bring back the DL link anyway.

#2 Updated by Nils Peters over 9 years ago

we have to create a new dependency installer for Windwos to include the new versions of the ICST ambisonics externals.

#3 Updated by Trond Lossius about 9 years ago

  • Project changed from Modular to Tools
  • Target version deleted (0.5.1)

#4 Updated by Adrian Gierakowski almost 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Adrian Gierakowski
  • Priority changed from Normal to High
  • Target version set to Windows Management
  • Estimated time set to 1.00
  • OS changed from Windows 7 64bit to Windows

There is a ruby script for making the installer however: I've run the script and it produced an installer (with a couple of warnings) but windows doesn't let me run it because it's product ID is set to the same value as main Jamoma installer (the system says that "another version of the program is already installed, blah, blah...."). I could manually change the product ID in the main.wxs file, but I think there might be some rules governing this, so I'll need to do a bit of research on it (unless anybody else knows how it works).

#5 Updated by Adrian Gierakowski almost 8 years ago

I've fixed the GUID for the installer and added version automatic version recognition to the installer script. Now we just need to upload the installer (attached) to the website.

#6 Updated by Adrian Gierakowski almost 8 years ago

  • Status changed from Assigned to Resolved

#7 Updated by Trond Lossius over 6 years ago

  • Status changed from Resolved to Closed

Moved to GitHub

Also available in: Atom PDF