Re: [Mixxx-devel] thoughts about our windows build env

[Sean M. Pappalardo - D.J. Pegasus]

Hi again, another thought:

RJ was at one time working on Windows cross-compiling from Linux. Where
did that leave off, RJ?

IMHO, spending the time getting that working would be more fruitful
since it would be MUCH easier for us to maintain. The only downside is
that Windows users would need access to a Linux box or VM to build Mixxx
themselves. But we could provide a packaged Linux VM with the build env
ready to go.

(The idea of providing a packaged Windows VM ready to go is a
non-starter for legal reasons.)

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine___
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] thoughts about our windows build env

[Sean M. Pappalardo - D.J. Pegasus]

On 06/19/2016 11:04 PM, Sébastien Blaisot wrote:
> This is absolutely incompatible with using a CI platform because the
> cost of env setup is way too much before being able to compile the code.

That's true of course.

> Why not using this as a base to maintain a ready-to-download build env ?

If you know of any way to do that, sure, rock on. :) If we can do
anything like RJ's Fabric script for Ubuntu, that would be great.

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine___
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] thoughts about our windows build env

[Sébastien Blaisot]

Le 20/06/2016 à 01:59, Sean M. Pappalardo - D.J. Pegasus a écrit :
> Hello.
>
> On 06/18/2016 08:01 AM, Sébastien Blaisot wrote:
>> I see another solution: why not seeing our windows build env as code,
>> just like the Mixxx base code. we can entirely script the build env
>> building and have it in git (we're not too far from that currently).
> RJ has already made very good progress on this:
> https://github.com/mixxxdj/buildserver/tree/windows_environment
>
> He and I are working on updating it for VS 2015 and newer dependencies.
>
> When complete, setting up a new env will be a matter of:
> 1) Installing the many prerequisite tools (Git, Scons, Python, MS Build
> Tools/VS Express, CMake, etc.)
> 2) Cloning that branch
> 3) Downloading the Qt source into the build/folder of that branch
> 4) Running build_environment.bat [x86|x64] [release|debug]
This is absolutely incompatible with using a CI platform because the 
cost of env setup is way too much before being able to compile the code.

Why not using this as a base to maintain a ready-to-download build env ?

> Then building Mixxx is a matter of:
> 1) Cloning the Mixxx repo
> 2) Running scons winlib=C:\path\to\above\folder
Currently, building Mixxx on a new windows machine (like a CI platform 
VM) is a matter of:
1) monthes of build env configuration
2) Cloning repo
3) Running scons
4) it's not working
5) do it again
6) ...
...

SB


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
___
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] thoughts about our windows build env

[Sean M. Pappalardo - D.J. Pegasus]

Hello.

On 06/18/2016 08:01 AM, Sébastien Blaisot wrote:
> I see another solution: why not seeing our windows build env as code, 
> just like the Mixxx base code. we can entirely script the build env 
> building and have it in git (we're not too far from that currently).

RJ has already made very good progress on this:
https://github.com/mixxxdj/buildserver/tree/windows_environment

He and I are working on updating it for VS 2015 and newer dependencies.

When complete, setting up a new env will be a matter of:
1) Installing the many prerequisite tools (Git, Scons, Python, MS Build
Tools/VS Express, CMake, etc.)
2) Cloning that branch
3) Downloading the Qt source into the build/folder of that branch
4) Running build_environment.bat [x86|x64] [release|debug]

Then building Mixxx is a matter of:
1) Cloning the Mixxx repo
2) Running scons winlib=C:\path\to\above\folder

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine___
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] thoughts about our windows build env

[Uwe Klotz]

Great idea, that's what I'm waiting for :) The Windows code is barely tested 
due to lack of contributors and a missing CI environment. On the other hand 
the Windows user base seems to be big.

In the past I've used a VM, no cross compiling. A VM is still a native 
Windows installation where you need to set up your build environment. Manual 
installation of the build tools is ok, because you only need to do this 
once. But the installation, patching, and building of 3rd party components 
needs to be scripted.

I've tried to follow the instructions in the Wiki, but that didn't work. 
After copying and editing various files manually I gave up half way, because 
it was too much work. With a working Windows build environment I would start 
to spend some time on fixing some of the outstanding (and really critical) 
bugs. Mixxx is unusable on Windows when playing M4A files.

Uwe


On 18.06.2016 17:01, Sébastien Blaisot wrote:
> Hi all,
>
> Our Linux build env is easy to setup: just install a few -devel and
> build tools packages included in the distribution and you're done.
>
> On the other hand, our windows build env is really hard to set up. You
> need to install the build tools (Microsoft visual studio, nsis, wix,
> ...), but also download the library sources and build them as shared
> libraries and headers.
>
> This has two consequences:
>
> - first, this is a long, manual process so it is hard for a beginner to
> have a working windows build env for Mixxx. It is also hard for us to
> make a new windows build server for our package delivery and we have no
> windows build server for ages.
>
> - Secondly, the way it is working now prevent us to use continuous
> integration platforms for windows env (like appveyor) because the
> cost/time to setup our build env before effectively building and testing
> the code is prohibitive.
>
>
> I see another solution: why not seeing our windows build env as code,
> just like the Mixxx base code. we can entirely script the build env
> building and have it in git (we're not too far from that currently).
>
> With this in mind, our windows build server can regularly build our
> build env, make an artifact (a zip file containing the build env) and
> put it somewhere for download.
>
> With this packaged build env, our build server as well as any other
> windows CI service like appVeyor will be able to download and setup the
> build env in a few seconds, and then compile Mixxx.
>
> This would make creating a new windows build env or a new windows
> jenkins slave an easy task, as easy as installing the few build tools
> packages and downloading the build env package.
>
>
> What do you think of this ?
>
> I can start working on this if you find it a nice way to deal with our
> buil env complexity.
>
>
> S.B.
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports. http://sdm.link/zohomanageengine
> ___
> 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
>


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
___
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] thoughts about our windows build env

[Sébastien Blaisot]

Yes, setting up a build env on windows will stay harder than on other 
systems.


Virtual machine and cross compilation are attractive ideas, but will 
remain harder for our users that want to try compiling Mixxx and 
involves more system knowledge (needing setting up a virtualization 
system or installing Linux).


My preference goes to either a batch file (we have one already thanks to 
RJ but it needs a little fix and a lot of manual download/install/modify 
by hand some files), or even easier a ready-to-use build env that we can 
build and provide to our users and even use ourselves for building Mixxx.


The other way is to have a working building env and delivering nightly 
builds, making fixing the build env a #1 priority when it breaks. This 
way, nobody needs a windows build env.


sb

Le 18/06/2016 à 17:48, Daniel Schürmann a écrit :


Hi Sébastien,

any work, that simplifies the Windows building would be great.

However. I am afraid that Windows will remain the hardest build 
environment. This is a bad situation facing that a mayority of users 
are on Windows.


An instant build environment for windows would help a lot.

What are our legal oportuities to provide a working Win10 virtual 
machine Image?


If that isn't allowed, can we provide a batch file, that can be run on 
a virgin Win10?


An other Idea (l think Uwe has done some research) is to setup a cross 
compile environment on Linux.


Am 18.06.2016 5:21 nachm. schrieb "Sébastien Blaisot" 
>:


Hi all,

Our Linux build env is easy to setup: just install a few -devel and
build tools packages included in the distribution and you're done.

On the other hand, our windows build env is really hard to set up. You
need to install the build tools (Microsoft visual studio, nsis, wix,
...), but also download the library sources and build them as shared
libraries and headers.

This has two consequences:

- first, this is a long, manual process so it is hard for a
beginner to
have a working windows build env for Mixxx. It is also hard for us to
make a new windows build server for our package delivery and we
have no
windows build server for ages.

- Secondly, the way it is working now prevent us to use continuous
integration platforms for windows env (like appveyor) because the
cost/time to setup our build env before effectively building and
testing
the code is prohibitive.


I see another solution: why not seeing our windows build env as code,
just like the Mixxx base code. we can entirely script the build env
building and have it in git (we're not too far from that currently).

With this in mind, our windows build server can regularly build our
build env, make an artifact (a zip file containing the build env) and
put it somewhere for download.

With this packaged build env, our build server as well as any other
windows CI service like appVeyor will be able to download and
setup the
build env in a few seconds, and then compile Mixxx.

This would make creating a new windows build env or a new windows
jenkins slave an easy task, as easy as installing the few build tools
packages and downloading the build env package.


What do you think of this ?

I can start working on this if you find it a nice way to deal with our
buil env complexity.


S.B.



--
What NetFlow Analyzer can do for you? Monitors network bandwidth
and traffic
patterns at an interface-level. Reveals which users, apps, and
protocols are
consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using
capacity planning
reports. http://sdm.link/zohomanageengine
___
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



--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine___
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] thoughts about our windows build env

[Daniel Schürmann]

Hi Sébastien,

any work, that simplifies the Windows building would be great.

However. I am afraid that Windows will remain the hardest build
environment. This is a bad situation facing that a mayority of users are on
Windows.

An instant build environment for windows would help a lot.

What are our legal oportuities to provide a working Win10 virtual machine
Image?

If that isn't allowed, can we provide a batch file, that can be run on a
virgin Win10?

An other Idea (l think Uwe has done some research) is to setup a cross
compile environment on Linux.
Am 18.06.2016 5:21 nachm. schrieb "Sébastien Blaisot" :

> Hi all,
>
> Our Linux build env is easy to setup: just install a few -devel and
> build tools packages included in the distribution and you're done.
>
> On the other hand, our windows build env is really hard to set up. You
> need to install the build tools (Microsoft visual studio, nsis, wix,
> ...), but also download the library sources and build them as shared
> libraries and headers.
>
> This has two consequences:
>
> - first, this is a long, manual process so it is hard for a beginner to
> have a working windows build env for Mixxx. It is also hard for us to
> make a new windows build server for our package delivery and we have no
> windows build server for ages.
>
> - Secondly, the way it is working now prevent us to use continuous
> integration platforms for windows env (like appveyor) because the
> cost/time to setup our build env before effectively building and testing
> the code is prohibitive.
>
>
> I see another solution: why not seeing our windows build env as code,
> just like the Mixxx base code. we can entirely script the build env
> building and have it in git (we're not too far from that currently).
>
> With this in mind, our windows build server can regularly build our
> build env, make an artifact (a zip file containing the build env) and
> put it somewhere for download.
>
> With this packaged build env, our build server as well as any other
> windows CI service like appVeyor will be able to download and setup the
> build env in a few seconds, and then compile Mixxx.
>
> This would make creating a new windows build env or a new windows
> jenkins slave an easy task, as easy as installing the few build tools
> packages and downloading the build env package.
>
>
> What do you think of this ?
>
> I can start working on this if you find it a nice way to deal with our
> buil env complexity.
>
>
> S.B.
>
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports. http://sdm.link/zohomanageengine
> ___
> 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
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine___
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] thoughts about our windows build env

[Sébastien Blaisot]

Hi all,

Our Linux build env is easy to setup: just install a few -devel and 
build tools packages included in the distribution and you're done.

On the other hand, our windows build env is really hard to set up. You 
need to install the build tools (Microsoft visual studio, nsis, wix, 
...), but also download the library sources and build them as shared 
libraries and headers.

This has two consequences:

- first, this is a long, manual process so it is hard for a beginner to 
have a working windows build env for Mixxx. It is also hard for us to 
make a new windows build server for our package delivery and we have no 
windows build server for ages.

- Secondly, the way it is working now prevent us to use continuous 
integration platforms for windows env (like appveyor) because the 
cost/time to setup our build env before effectively building and testing 
the code is prohibitive.


I see another solution: why not seeing our windows build env as code, 
just like the Mixxx base code. we can entirely script the build env 
building and have it in git (we're not too far from that currently).

With this in mind, our windows build server can regularly build our 
build env, make an artifact (a zip file containing the build env) and 
put it somewhere for download.

With this packaged build env, our build server as well as any other 
windows CI service like appVeyor will be able to download and setup the 
build env in a few seconds, and then compile Mixxx.

This would make creating a new windows build env or a new windows 
jenkins slave an easy task, as easy as installing the few build tools 
packages and downloading the build env package.


What do you think of this ?

I can start working on this if you find it a nice way to deal with our 
buil env complexity.


S.B.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
___
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