Re: [Mixxx-devel] port windows installer to Wix
-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 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 gain. It supports atomic access >to >>the >>> control objects and has core SSE instructions. >> >>ok, I modified the installer to allow 32 bits installation on a >64 >>bits >>machine but print a warning message to the user that he will have >>better >>performances using the 64bits version. >> >>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 in preferences->program uninstall >> >> >>I have 2 ways to deal with this : >> >>1) always append (64 bits) on 64bits shortcuts, directory and >>uninstall >>entry. I think this is a nonsense for 64 bits users that do not >>want to >>install 32bit version >> >>2) forbid 64 bits installation if 32bits version is already >>installed >>and vice-versa. This will lead to the impossibility to install >>woth 32 >>and 64 bits versions of Mixxx on the same computer. >> >>My preference goes to #2 because I don't see any use case to have >>both >>32 and 64 bits installed on the same computer, except for a >>developper >>that can tweak his registry to allow this to happen. >> >>Any thoughts ? >> > >I've had a lot of annoyance with multiple installs in Windows so >I'm chiming in: > >I'd much rather have #1, with Gavin's suggestion of the appending >term be "x64" or "(x64)". > >It would be pretty great if the appended name would only appear if >the other type (or even another version) was discovered at >install. >Otherwise left unappended. > >In other words, plain naming for when it will be the only version >on the machine, but if the installer discovers another version the >newer install gets its shortcuts appended. > >Further, the possibility to add a suffix to the preexisting >install >as well would be good, and make even more intuitive sense. > >~RAWRR > >> >>-- >- >>--- >>___ >>Get Mixxx, the #1 Free MP3 DJ Mixing software Today >>http://mixxx.org >> >> >>Mixxx-devel mailing list >>Mixxx-devel@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/mixxx-devel -BEGIN PGP SIGNATURE- Charset: UTF8 Version: Hush 3.0 Note: This signature can be verified at https://www.hushtools.com/verify wpwEAQMCAAYFAlXt8nYACgkQzo/Gj4mkNMwKKgQAhPVJfkoOy7zjRxUUqDNYpT8S231S c94mGuFcFq1v4vAHMa2ePx6v7TurC4+wBdlrjKB7nNse6BHYwVHdzUpm9UUfpEYwrnpf Poe8ILU43J0jplzXS3ni4siiCy4F1vcc9WX3fu1gCIDv/CgqJiw1eIGr4J2/w1aKP8H4 BjbCfws= =WsGL -END PGP SIGNATURE- -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
>> 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 in preferences->program uninstall >> >> >> I have 2 ways to deal with this : >> >> 1) always append (64 bits) on 64bits shortcuts, directory and uninstall >> entry. I think this is a nonsense for 64 bits users that do not want to >> install 32bit version >> >> 2) forbid 64 bits installation if 32bits version is already installed >> and vice-versa. This will lead to the impossibility to install woth 32 >> and 64 bits versions of Mixxx on the same computer. >> >> My preference goes to #2 because I don't see any use case to have both >> 32 and 64 bits installed on the same computer, except for a developper >> that can tweak his registry to allow this to happen. >> >> Any thoughts ? In my , limited, experience with the new change to 64bit packaging in windows it seems that the most recently installed version always wins with the things you noted as problematic. I think you could also have an option 3. Warn the user at installation that an old version of mixxx has been found and ask if he wants to delete that old version before continuing as this might cause problems later on. This might also be more useful for users upgrading from an 32bit installation to a 64bit one. Saves us the rather ugly 'x64' appendix. -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 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 gain. It supports atomic access to the > > control objects and has core SSE instructions. > > ok, I modified the installer to allow 32 bits installation on a 64 bits > machine but print a warning message to the user that he will have better > performances using the 64bits version. > > 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 in preferences->program uninstall > > > I have 2 ways to deal with this : > > 1) always append (64 bits) on 64bits shortcuts, directory and uninstall > entry. I think this is a nonsense for 64 bits users that do not want to > install 32bit version > > 2) forbid 64 bits installation if 32bits version is already installed > and vice-versa. This will lead to the impossibility to install woth 32 > and 64 bits versions of Mixxx on the same computer. > > My preference goes to #2 because I don't see any use case to have both > 32 and 64 bits installed on the same computer, except for a developper > that can tweak his registry to allow this to happen. > > Any thoughts ? > > > > -- > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 gain. It supports atomic access to the > control objects and has core SSE instructions. ok, I modified the installer to allow 32 bits installation on a 64 bits machine but print a warning message to the user that he will have better performances using the 64bits version. 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 in preferences->program uninstall I have 2 ways to deal with this : 1) always append (64 bits) on 64bits shortcuts, directory and uninstall entry. I think this is a nonsense for 64 bits users that do not want to install 32bit version 2) forbid 64 bits installation if 32bits version is already installed and vice-versa. This will lead to the impossibility to install woth 32 and 64 bits versions of Mixxx on the same computer. My preference goes to #2 because I don't see any use case to have both 32 and 64 bits installed on the same computer, except for a developper that can tweak his registry to allow this to happen. Any thoughts ? -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 increase complexity over time. regads, --- Sébastien Blaisot Le 03/09/2015 13:04, Daniel Schürmann a écrit : > 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 [4] > > IMHO we should not drop XP support for no reason. > > 2015-09-03 11:53 GMT+02:00 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. >> >> So for anything after 1.12 you should be free to ignore XP. >> >> -- >> Monitor Your Dynamic Infrastructure at Any Scale With Datadog! >> Get real-time metrics from all of your servers, apps and tools >> in one place. >> SourceForge users - Click here to start your Free Trial of Datadog now! >> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 [1] >> >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org [2] >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [3] > > -- > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 [1] > > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org [2] > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel [3] Links: -- [1] http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 [2] http://mixxx.org [3] https://lists.sourceforge.net/lists/listinfo/mixxx-devel [4] http://doc.qt.io/qt-5/windows-issues.html -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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. 2015-09-03 11:53 GMT+02:00 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. > > > So for anything after 1.12 you should be free to ignore XP. > > > -- > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
> > 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. So for anything after 1.12 you should be free to ignore XP. -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 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 present in Add/Remove programs, there's a registry key for it!
>> :) If nothing is mentioned on WiX documentation, look in the standard
>> places installed applications are registered. In the worst case, look
>> around your registry in HKLM/Software/Microsoft/Windows/Installer or
>> HKLM/Software/Microsoft/WiX.
> I found it under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2A076531-42D9-4231-8A60-323EBE603E2E}.
>
> but first, I'm not sure the Guid part is fixed, and second the
> installation path is not in this key :(
>
> But I found HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
> Installer XML\3.9
>
> unfortunately, the version number is in it, so I will have to include
> more logic :(
>
> sb
>
>
> --
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> ___
> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
> http://mixxx.org
>
>
> Mixxx-devel mailing list
> Mixxx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 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 present in Add/Remove programs, there's a registry key for it!
> :) If nothing is mentioned on WiX documentation, look in the standard
> places installed applications are registered. In the worst case, look
> around your registry in HKLM/Software/Microsoft/Windows/Installer or
> HKLM/Software/Microsoft/WiX.
I found it under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2A076531-42D9-4231-8A60-323EBE603E2E}.
but first, I'm not sure the Guid part is fixed, and second the
installation path is not in this key :(
But I found HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
Installer XML\3.9
unfortunately, the version number is in it, so I will have to include
more logic :(
sb
--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
___
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 microsoft part is the installer engine that let you install MSI's on target computers. Sadly, Desktop and Start Menu shortcuts are not separated, so I need to handle the case... Same apply to uninstall entries. so, we will need to append (64bits) to each shortcut or uninstall entry. -- Sébastien Blaisot 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 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 present in Add/Remove programs, there's a registry key for it! :) If > nothing is mentioned on WiX documentation, look in the standard places > installed applications are registered. In the worst case, look around your > registry in HKLM/Software/Microsoft/Windows/Installer or > HKLM/Software/Microsoft/WiX. > >> - installation of both 32 + 64 bit mixxx on a 64 bits OS. This should >> be the tricky part. > > Not really, since %PROGRAMFILES% will expand to "Program Files (x86)" in a > 32-bit process on a 64-bit system, and "Program Files" in other cases. This > happens automatically. The registries are also separated. (Wow6432Node) > > Sincerely, > Sean M. Pappalardo > "D.J. Pegasus" > Mixxx Developer - Controller Specialist -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 present in Add/Remove programs, there's a registry key for it! :) If nothing is mentioned on WiX documentation, look in the standard places installed applications are registered. In the worst case, look around your registry in HKLM/Software/Microsoft/Windows/Installer or HKLM/Software/Microsoft/WiX. - installation of both 32 + 64 bit mixxx on a 64 bits OS. This should be the tricky part. Not really, since %PROGRAMFILES% will expand to "Program Files (x86)" in a 32-bit process on a 64-bit system, and "Program Files" in other cases. This happens automatically. The registries are also separated. (Wow6432Node) Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist smime.p7s Description: S/MIME Cryptographic Signature -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 modules that you can embed in your installer. They are usually installed in C:\Program Files (x86)\Common Files\Merge Modules when you install visual studio. 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. so I don't see any solution appart asking the developper to manually set it somewhere, either as PATH or environment variable or as a compilation switch. The same way we do it for WINLIB_PATH path in http://www.mixxx.org/wiki/doku.php/build_windows_installer#make_the_package [7] 3. Ok, so I will need to handle : - warning message when installing 32 bits on 63bits system - installation of both 32 + 64 bit mixxx on a 64 bits OS. This should be the tricky part. 4. ok, I'll keep XP compatibility 5. ok, I'll drop sqldrivers but keep promo as pointed by Sean. regards, -- Sébastien Blaisot Le 02/09/2015 08:38, Daniel Schürmann a écrit : > 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 > [4] > > 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 gain. It supports atomic access to the > control objects and has core SSE instructions. > >> 4. Can we get rid of windows XP Support ? > > Is there a strong technical need to drop XP support? > Win XP is still the second often used desktop operating system after Win 7. > It is common to use recycled laptops for parties where a beer shower may > happen. > https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 > [5] > Lets keep it! > >> 5. actual installer creates empty directories "promo" and "sqldrivers". > Are they still required or just oldies that we can forget? > > They outdated and can be removed. > > Kind regards, > > Daniel > > Am 01.09.2015 um 23:05 schrieb 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 able to build 32 and 64 bits MSI for Mixxx manually and >> installing it to my computer leads to a working Mixxx \o/. >> >> My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer >> [1] >> All changes has been made under build/wix >> >> What's left on my TODO list : >> - include VCredist in the package (seems possible to use VCredist merge >> modules if we have visual studio installed on the build server) >> - Add QT's translations that I left appart from the installer now >> because it's not possible to include a subset of the files in a source >> directory >> - Integrate with SCons >> - test, test and test again >> >> I have a few questions to achieve this goal : >> >> 1. Can someone with an access to the build server show me what's in >> C:\Program Files (x86)\Common Files\Merge Modules ? >> >> 2. When we will have Wix installed on the build server, is it acceptable >> to add the Wix installation directory to the %PATH% of the build server >> and rely on it ? I didn't find a way to automatically determine where >> this folder is located like we actually do in scons for NSIS. >> >> 3. Installation of 64bits package on 32bits machines is of course >> forbidden. I'm not sure if we need to permit 32bits mixxx installation >> on 64bits computer. Is anyone aware of such a use-case ? >> >> I really appreciate all comments about this. >> >> regards, >> >> sb >> >> -- >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org [2] >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel [3] > > -- > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://p
Re: [Mixxx-devel] port windows installer to Wix
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 caveats: - Old 1.11 and new 1.12 skins present in the skins folder - 2 entries in settings pannel -> software uninstall (for 1.11 and 1.12), but both entries will uninstall mixxx and keep the other entry orpheline. - Files manually added to Mixxx installation folder being deleted on uninstall even if not installed by Mixxx's installer (except for controller mappings) The other benefit is to support autorepair functionnality of windows installer framework. regards, -- Sébastien Blaisot Le 02/09/2015 08:43, Tuukka Pasanen a écrit : > 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! > > 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 > [1] > > 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 gain. It supports atomic access to the > control objects and has core SSE instructions. > > 4. Can we get rid of windows XP Support ? Is there a strong technical need to > drop XP support? > Win XP is still the second often used desktop operating system after Win 7. > It is common to use recycled laptops for parties where a beer shower may > happen. > https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 > [2] > Lets keep it! > > 5. actual installer creates empty directories "promo" and "sqldrivers". Are > they still required or just oldies that we can forget? > > They outdated and can be removed. > > Kind regards, > > Daniel > > Am 01.09.2015 um 23:05 schrieb 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 able to build 32 and 64 bits MSI for Mixxx manually and > installing it to my computer leads to a working Mixxx \o/. > > My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer > [3] > All changes has been made under build/wix > > What's left on my TODO list : > - include VCredist in the package (seems possible to use VCredist merge > modules if we have visual studio installed on the build server) > - Add QT's translations that I left appart from the installer now > because it's not possible to include a subset of the files in a source > directory > - Integrate with SCons > - test, test and test again > > I have a few questions to achieve this goal : > > 1. Can someone with an access to the build server show me what's in > C:\Program Files (x86)\Common Files\Merge Modules ? > > 2. When we will have Wix installed on the build server, is it acceptable > to add the Wix installation directory to the %PATH% of the build server > and rely on it ? I didn't find a way to automatically determine where > this folder is located like we actually do in scons for NSIS. > > 3. Installation of 64bits package on 32bits machines is of course > forbidden. I'm not sure if we need to permit 32bits mixxx installation > on 64bits computer. Is anyone aware of such a use-case ? > > I really appreciate all comments about this. > > regards, > > sb > > -- > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org [4] > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel [5] > -- > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 [6] > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org [4] > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel [5] --
Re: [Mixxx-devel] port windows installer to Wix
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! > > 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 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 gain. It supports atomic access to the > control objects and has core SSE instructions. > >> 4. Can we get rid of windows XP Support ? > Is there a strong technical need to drop XP support? > Win XP is still the second often used desktop operating system after Win 7. > It is common to use recycled laptops for parties where a beer shower may > happen. > https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 > Lets keep it! > > >> 5. actual installer creates empty directories "promo" and "sqldrivers". > Are they still required or just oldies that we can forget? > > They outdated and can be removed. > > > Kind regards, > > Daniel > > > > > > > Am 01.09.2015 um 23:05 schrieb 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 able to build 32 and 64 bits MSI for Mixxx manually and >> installing it to my computer leads to a working Mixxx \o/. >> >> My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer >> All changes has been made under build/wix >> >> What's left on my TODO list : >> - include VCredist in the package (seems possible to use VCredist merge >> modules if we have visual studio installed on the build server) >> - Add QT's translations that I left appart from the installer now >> because it's not possible to include a subset of the files in a source >> directory >> - Integrate with SCons >> - test, test and test again >> >> I have a few questions to achieve this goal : >> >> 1. Can someone with an access to the build server show me what's in >> C:\Program Files (x86)\Common Files\Merge Modules ? >> >> 2. When we will have Wix installed on the build server, is it acceptable >> to add the Wix installation directory to the %PATH% of the build server >> and rely on it ? I didn't find a way to automatically determine where >> this folder is located like we actually do in scons for NSIS. >> >> 3. Installation of 64bits package on 32bits machines is of course >> forbidden. I'm not sure if we need to permit 32bits mixxx installation >> on 64bits computer. Is anyone aware of such a use-case ? >> >> I really appreciate all comments about this. >> >> regards, >> >> sb >> >> -- >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > -- > Monitor Your Dynamic Infrastructure at Any Scale With Datadog! > Get real-time metrics from all of your servers, apps and tools > in one place. > SourceForge users - Click here to start your Free Trial of Datadog now! > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 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 gain. It supports atomic access to the control objects and has core SSE instructions. > 4. Can we get rid of windows XP Support ? Is there a strong technical need to drop XP support? Win XP is still the second often used desktop operating system after Win 7. It is common to use recycled laptops for parties where a beer shower may happen. https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0 Lets keep it! > 5. actual installer creates empty directories "promo" and "sqldrivers". Are they still required or just oldies that we can forget? They outdated and can be removed. Kind regards, Daniel Am 01.09.2015 um 23:05 schrieb 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 able to build 32 and 64 bits MSI for Mixxx manually and > installing it to my computer leads to a working Mixxx \o/. > > My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer > All changes has been made under build/wix > > What's left on my TODO list : > - include VCredist in the package (seems possible to use VCredist merge > modules if we have visual studio installed on the build server) > - Add QT's translations that I left appart from the installer now > because it's not possible to include a subset of the files in a source > directory > - Integrate with SCons > - test, test and test again > > I have a few questions to achieve this goal : > > 1. Can someone with an access to the build server show me what's in > C:\Program Files (x86)\Common Files\Merge Modules ? > > 2. When we will have Wix installed on the build server, is it acceptable > to add the Wix installation directory to the %PATH% of the build server > and rely on it ? I didn't find a way to automatically determine where > this folder is located like we actually do in scons for NSIS. > > 3. Installation of 64bits package on 32bits machines is of course > forbidden. I'm not sure if we need to permit 32bits mixxx installation > on 64bits computer. Is anyone aware of such a use-case ? > > I really appreciate all comments about this. > > regards, > > sb > > -- > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 Wix installation directory to the %PATH% of the build server and rely on it ? I didn't find a way to automatically determine where this folder is located like we actually do in scons for NSIS. Can you not check the registry? Isn't that what we do for NSIS? I'd much prefer not to have to rely on any system environment setting to make it easier for others who want to set up a build environment. 3. Installation of 64bits package on 32bits machines is of course forbidden. I'm not sure if we need to permit 32bits mixxx installation on 64bits computer. Is anyone aware of such a use-case ? I can't think of a use case (other than mass deployment to a mix of 32 and 64-bit PCs,) but there is typically no restriction to install 32-bit software on a 64-bit OS. We could however pop up a message saying that a full 64-bit version is available and that they should go get that instead, but allow them to proceed if they choose. 4. Can we get rid of windows XP Support ? No. There are too many people still using Windows XP (on old hardware and in developing countries.) 5. actual installer creates empty directories "promo" and "sqldrivers". Are they still required or just oldies that we can forget ? Sqldrivers was needed when we didn't build SQLite support into the qtsql.dll. For the forseeable future it's not needed since we plan to continue doing that. Promo would contain promotional tracks that labels/artists have paid Mixxx to include with the installation, or tracks we otherwise want to include. We haven't done this in years but would like to keep the ability should we do so in the future. The folder should not be created if there's nothing to put in it though. Sincerely, Sean M. Pappalardo "D.J. Pegasus" Mixxx Developer - Controller Specialist smime.p7s Description: S/MIME Cryptographic Signature -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] port windows installer to Wix
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 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 able to build 32 and 64 bits MSI for Mixxx manually and > installing it to my computer leads to a working Mixxx \o/. > > My work is shown here : https://github.com/sblaisot/mixxx/tree/wix-installer > All changes has been made under build/wix > > What's left on my TODO list : > - include VCredist in the package (seems possible to use VCredist merge > modules if we have visual studio installed on the build server) > - Add QT's translations that I left appart from the installer now > because it's not possible to include a subset of the files in a source > directory > - Integrate with SCons > - test, test and test again > > I have a few questions to achieve this goal : > > 1. Can someone with an access to the build server show me what's in > C:\Program Files (x86)\Common Files\Merge Modules ? > > 2. When we will have Wix installed on the build server, is it acceptable > to add the Wix installation directory to the %PATH% of the build server > and rely on it ? I didn't find a way to automatically determine where > this folder is located like we actually do in scons for NSIS. > > 3. Installation of 64bits package on 32bits machines is of course > forbidden. I'm not sure if we need to permit 32bits mixxx installation > on 64bits computer. Is anyone aware of such a use-case ? > > I really appreciate all comments about this. > > regards, > > sb > > -- > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel -- Sébastien 圣巴斯弟盎 -- ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
