Re: [Mixxx-devel] port windows installer to Wix

2015-09-07 Thread re-cycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (forgot to Cc) On Mon, 07 Sep 2015 21:03:41 +0200 re-cy...@hushmail.com wrote: >On Sat, 05 Sep 2015 23:48:06 +0200 "Sébastien Blaisot" > wrote: >>Le 02/09/2015 08:38, Daniel Schürmann a écrit : >>> 3. IMHO it is nothing wrong to

Re: [Mixxx-devel] port windows installer to Wix

2015-09-06 Thread Max Linke
>> I now have a conflict when installing both 32 and 64bits packages on the >> same machine because they install : >> - same Mixxx startup menu shortcut >> - same Mixxx desktop shortcut >> - same Mixxx manual startup menu shortcut >> - same Mixxx startup menu subfolder >> - same uninstall entry

Re: [Mixxx-devel] port windows installer to Wix

2015-09-05 Thread Sébastien Blaisot
Le 02/09/2015 08:38, Daniel Schürmann a écrit : > 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit Windows. > So It should be possible to keep a degree of freedom in case of issues. > However, we should encourage the user to use 64 bit binaries, since > there should be a performance

Re: [Mixxx-devel] port windows installer to Wix

2015-09-05 Thread Gavin Swanson
Definitely number one. Appending "x64" or something similar is the standard method of handling this. On Sat, Sep 5, 2015, 2:49 PM Sébastien Blaisot wrote: > Le 02/09/2015 08:38, Daniel Schürmann a écrit : > > 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit

Re: [Mixxx-devel] port windows installer to Wix

2015-09-03 Thread Max Linke
> > 4. Can we get rid of windows XP Support ? 1.12 will be the last release supporting Windows XP. It is also the last release were it is possible to have a Windows XP build. This is because Qt5 has dropped support for XP and the new Virtual Studios that support C++11 don't support XP either.

Re: [Mixxx-devel] port windows installer to Wix

2015-09-03 Thread Daniel Schürmann
We are free to decide when it is the right moment to drop XP since Microsoft has reintroduced XP support into Visual Studio. It also looks like that there is no issue to compile QT 5.5 for Windows XP: http://doc.qt.io/qt-5/windows-issues.html IMHO we should not drop XP support for no reason.

Re: [Mixxx-devel] port windows installer to Wix

2015-09-03 Thread Sébastien BLAISOT
No matter if we will continue to build Mixxx for XP or not, the installer will not enforce XP support drop, so you will be free to support XP or not. That said, I personnally don't think it's a good think to passively encourage people to keep XP. Keeping XP support will exponentionnaly

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Tuukka Pasanen
Hello, What are main benfits of porting to WIX and yes XP in oboslette but many people still use it. Biggest problem will be with QT5 or the future when it's dropped.from QT. Tuukka 02.09.2015, 09:38, Daniel Schürmann kirjoitti: > Hi Sébastien, > > Thank you for all your work on Windows! > >

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Daniel Schürmann
Hi Sébastien, Thank you for all your work on Windows! I'll try to answer some of you questions: 1. ? 2. it should be $(WIX) according to http://stackoverflow.com/questions/2375322/variable-for-wix-bin-directory-path 3. IMHO it is nothing wrong to install a 32 binary to a 64 bit Windows. So

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT
The main benefit in switching to wix is to support clean upgrade pathes between versions the same way they are handled by deb packages or macOS packages. Actually, If you install 1.12 on windows and have 1.11 already installed, this leads to 1.12 installed on top of 1.11 with the following

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sean M. Pappalardo - D.J. Pegasus
On 09/02/2015 08:11 AM, Sébastien BLAISOT wrote: 2. I'm afraid $(WIX) is a locally defined variable from the blog author. in fact $(WIX) is not a windows variable format, it should be %WIX%. I didn't find any environment variable nor registry key telling me where WIX it installed. If it's

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT
I'll try to answer to all points. 1. Mixxx needs VCredist libraries. The actual NSIS installer embed vcredist.exe and launch it in the background based on a registry key. The clean way to do this in Wix is to embed mergeable modules of vcredist in your installer. mergeable modules are

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien BLAISOT
I already did a search on Wix in my registry with nothing standard found to tell me where wix is actually installed. I will take another look tonight. (Wix is not a microsoft product, it's an open source project that compiles an xml description of your installer into an MSI package). The

Re: [Mixxx-devel] port windows installer to Wix

2015-09-02 Thread Sébastien Blaisot
oops, found it, there indeed IS a %WIX% environment variable set by installer. sb Le 02/09/2015 19:28, Sébastien Blaisot a écrit : > Le 02/09/2015 17:27, Sean M. Pappalardo - D.J. Pegasus a écrit : >> >> On 09/02/2015 08:11 AM, Sébastien BLAISOT wrote: >>> 2. I'm afraid $(WIX) is a locally

Re: [Mixxx-devel] port windows installer to Wix

2015-09-01 Thread Sean M. Pappalardo - D.J. Pegasus
Hello. Thanks for working on this! It's something I've wanted to see for awhile myself. Owen has access to the build server so can answer your question #1. On 09/01/2015 02:05 PM, Sébastien Blaisot wrote: 2. When we will have Wix installed on the build server, is it acceptable to add the

Re: [Mixxx-devel] port windows installer to Wix

2015-09-01 Thread Sébastien Blaisot
I have two more questions : 4. Can we get rid of windows XP Support ? 5. actual installer creates empty directories "promo" and "sqldrivers". Are they still required or just oldies that we can forget ? regards, sb Le 01/09/2015 23:05, Sébastien Blaisot a écrit : > Hi All, > > I'm in an

[Mixxx-devel] port windows installer to Wix

2015-09-01 Thread Sébastien Blaisot
Hi All, I'm in an effort to port Mixxx's windows installer to Wix. I really have hard times because windows installer framework is... well... you know. I primarily focused on the reproduction of the existing operation, with some gain in this migration (working upgrades primarily). I am now