[Freeswitch-users] Windows build system

[Michael Jerris]

I'm a bit out of date on what these tools provide and need someone to get me up to speed on what is available.  Can you help me understand what the options are for maintaining c libraries in a way that is cleaner than needing to stuff them all into our build.


> On Dec 8, 2014, at 5:29 AM, Markus von Arx <mkvonarx at gmail.com> wrote:
> 
> We are fine with your Visual Studio plans. We only use VS2012 at the moment and actually would like to migrate to VS2013.
> 
> Not so sure about the use of chocolatey though. Are you planning to use it to download libraries required by the build or for installing software/tools required for the build? Both look a bit problematic to me, because chocolatey (as far as I understand it) always acts globally on the target machine, meaning that it installs the libs/tools/software not locally inside the build directory but globally on the machine. I wouldn't like that at all. I don't want a build tool/process to install anything outside the build directory. If you manage to use chocolatey to only work in the build directory that's fine for me. But I'd strongly vote against any use of chocolatey to install libraries, tools or any software globally or outside the build directory. I wouldn't like a build tool/process/system installing anything on my machine for me automatically. Kind of like calling apt-get on a Linux machine from a build script. I think that is a no-go. Also, chocolatey is not so good detecting installed software that was not installed by chocolatey itself and would often try to re-install software that is already there. I'd vote against using chocolatey in the FreeSWITCH build if you ask me. Wouldn't nuget be the more natural choice anyway to install modules/libraries in Visual Studio? Just my opinion.
> 
> Markus
> 
> 
> 2014-12-03 21:31 GMT+01:00 Michael Jerris <mike at jerris.com <mailto:mike at jerris.com>>:
> Given the recent announcements by Microsoft about the community edition 2013 being available, we are working to migrate the build system towards using that as our primary build.  As part of this process we will be very soon dropping support for any version of Visual Studio prior to 2012.  If you feel strongly about needing support for these older versions, please speak up now with an offer to maintain these legacy build systems.  We are also investigating moving to using chocolatey as a new system to manage dependencies on windows instead of maintaining the build for all our deps ourselves.   It is also possible we will drop support for the 2012 build system in the not so distant future.  Could the community chime in here as to what their needs are, and what they are willing to do to help support the windows builds so we can determine what we plan to support going forward.
> 
> Thanks
> Mike
> 
> https://chocolatey.org/ <https://chocolatey.org/>
> http://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx <http://www.visualstudio.com/en-us/news/vs2013-community-vs.aspx>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20141208/c859a51e/attachment.html