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

2015-09-01 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!
>
> 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

2015-09-01 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 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

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 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

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 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

[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 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