I don't necessarily want to kick the dead horse here but the matter of fact
is that Henri is absolutely (and sadly) right.
I do understand that your role Oz could be very stressing (since you were
promoted i see you very rarely and only for a really small time frame) but
the thing here is that we
I am asking because when we went through the change for 2005->2010 (see
issue OPEN-1) LL used devenv in their systems and several of their dev's
had autobuild on personal dev boxes that pointed to devenv. The problem was
that many of the OS developers, would be contributors, were using VS2010
Expr
On Mon, 02 Feb 2015 13:05:20 -0500, Oz Linden (Scott Lawrence) wrote:
> On 2015-01-31 07:53 , Henri Beauchamp wrote:
> > Greetings,
> >
> > I know this should be posted in the JIRA, but apparently the comments in
> > the existing issue (SUN-38) are not read or not taken into account by
> > Lindens
On February 2, 2015 at 11:42:10 AM, Nicky Perian (nickyper...@gmail.com) wrote:
Does the underlying builder in LL's automated build system call MSBuild or
Devenv?
If it’s Team City or Bamboo, then it calls MSBuild like Microsoft recommends.
Not sure about others. Drake has fixed the issue wi
Does the underlying builder in LL's automated build system call MSBuild or
Devenv?
On Mon, Feb 2, 2015 at 12:30 PM, Oz Linden (Scott Lawrence) <
o...@lindenlab.com> wrote:
> On 2015-01-31 11:41 , Nicky Perian wrote:
>
> Two methods for command line building have been tested each starting
> wit
On 2015-02-02 13:05 , Oz Linden (Scott Lawrence) wrote:
I will say that your input would certainly have been considered had
you been a part of the conversation at the time rather than posting a
note on our private forum well after the fact.
s/our private forum/your private forum/
--
*Oz Linde
On 2015-01-31 11:41 , Nicky Perian wrote:
Two methods for command line building have been tested each starting
with a fresh build-vc120 directory, with tests and package on.
Machine spec is Intel i7 all 8 cores running with 6GB memory.
autobuild configure -c ReleaseOSCE and autobuild build -c
On 2015-01-31 17:38 , Nicky Perian wrote:
Anyone know what causes this on a release build?
Doesn't stop the build and the installer is still made.
3>-- Build started: Project: generate_viewer_version,
Configuration: Release Win32 --
3> processing
3> 'printf' is not recognized as an in
On 2015-01-31 07:53 , Henri Beauchamp wrote:
Greetings,
I know this should be posted in the JIRA, but apparently the comments in
the existing issue (SUN-38) are not read or not taken into account by
Lindens.
Please, to any and all Linden(s) involved in AHH, do read this post for
your own enligh
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 w
10 matches
Mail list logo
