What did not work in production is compression and encryption with, said, "foreign agendas," inefficiencies, power consumption. In game mechanics, those tests are ignored and seem irrelevant because it is working. Under applied STEM research, even openjpeg failed production factors. If it doesn't work nicely (on bare metal) then it is subject for *external* video card mechanics and those agendas, warranties.
We have not received any digitally signed TOS tokens that specifically enable *Auto*build or register certain build features. The challenge is there, as the lawyers said, "it doesn't benefit me." In California, ibid. On Fri, Jan 30, 2015 at 1:41 PM, Oz Linden (Scott Lawrence) < o...@lindenlab.com> wrote: > On 2015-01-30 11:51 , Tank Master wrote: > > You are getting an error because that isn't a valid command. Use > "autobuild configure -c RelWithDebInfoOS" OR "autobuild configure -c > ReleaseOS" Also, This will still fail do to tests. I used: "autobuild > configure -c ReleaseOS -- -DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn > off both packaging and tests. > > > The tests should work - they do for us, though I suppose some may depend > on libs not in open source. > > -- > *Oz Linden (Scott Lawrence)* | *Engineering Director, Second Life* > Email or Hangouts o...@lindenlab.com | Second Life Oz Linden > <https://my.secondlife.com/oz.linden> > Linden Lab | Makers of Shared Creative Spaces <http://lindenlab.com/> > Check out what we're working on! <http://lindenlab.com/products> > > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
