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
