I have asked someone from The Foundry about this at FMX 2012, and the answer was “we are not allowed to provide Visual Studio as a service because Shitcrosoft and licenses and bla, and it’s something we will have to maintain, and this and that” - so in other words “no and we won't”.
But the problem was on the table already and would be nice if there are some motions in that direction, since (my deep IMO) in the multiplatform-multiversion situation of today the ABI dependencies and library dependencies are becoming a drag. I.e. building and maintaining a Nuke plugin with all the older infrastructure to support it (without having a readymade Vagrant image available to do the builds within of, for all OSes) is way more hassle and butthurt than actually writing the said plugin and fixing it’s bugs. On 04 Jun 2014, at 09:57, Ben Dickson <[email protected]> wrote: > Incidentally, it has crossed my mind a few times that it might be > relatively simple to setup a "community Nuke plugin build server" > thingy. Something along the lines of Travis-CI, but a bit more focused > (e.g include various sets of Nuke headers, gcc4.1.2, the same Qt version > etc) -- Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX Amsterdam | The Netherlands | tel. +31 20 330 8250 cel. +31 61 145 06 36 | http://hecticelectric.nl
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
