On Thu, Aug 10, 2017 at 11:48 AM, Nicky Perian
wrote:
Once the local LL libs are good to go, how can I prevent them from
> rebuilding every time a change is made to a newview source file?
>
Do you mean the various subprojects of the viewer source tree?
Once you have a build in hand, it would su
On Fri, Jun 30, 2017 at 12:21 PM, Nicky Perian
wrote:
Keep forgetting reply all. To complete the record;
> I tried to forcing Integrated Graphics (Intel) and Enhanced Graphics
> (Nvidia) and there is no difference.
>
I think you mean:
a. that you gave the name SL_Launcher.exe to both drivers. T
On Fri, Jun 30, 2017 at 11:52 AM, Nicky Perian
wrote:
On my alienware it is a Nvidia setting to use its driver as default and can
> also be set for a specific *.exe program name.
>
> On Fri, Jun 30, 2017 at 10:26 AM, Jonathan Welch
> wrote:
>
>> Some systems have two built in graphics chips such
On Fri, Jun 30, 2017 at 6:36 AM, Nicky Perian wrote:
I may be jumping ahead, but with an opensource build and built installer
> used :
>
> With shortcut to "C:\Program Files\SecondLifeProjectAlexIvy\SL_Launcher.exe"
> --set InstallLanguage en
> Program does not run log follows:
>
> 2017-06-30T09:
On Fri, Jun 30, 2017 at 6:41 AM, Nicky Perian wrote:
What is this a feature or hack?
>
Best guess is that somebody subscribed their support email to the
opensource-dev list? Seems like a poor idea.
___
Policies and (un)subscribe information available h
On Tue, Feb 21, 2017 at 9:36 AM, Nicky Perian wrote:
>>The autobuild feature that implicitly expands environment variables such
> as $AUTOBUILD_ADDRSIZE >>appearing in autobuild.xml is relatively recent,
> and we probably haven't yet covered all the cases where that >>should
> happen.
>
> As far
On Feb 18, 2017 1:33 PM, "Nicky Perian" wrote:
Any idea why autobuild the looks in the wrong location for
installed-packages.xml?
== Build: 5 succeeded, 0 failed, 29 up-to-date, 2 skipped ==
metadata file name: autobuild-package.xml
built Second Life Viewer version 5.1.0.41141
in
On Sat, Jan 28, 2017 at 10:00 PM, Nicky Perian
wrote:
macOS build ?
> Am I missing something? I have tried ReleaseOS command line build and
> cmake doesn't change to the correct source directory to complete the test
> compile.
>
> Are macOS command line builds possible at this time?
>
I think wh
On Fri, Jan 20, 2017 at 8:53 AM, Nicky Perian wrote:
Moving on to Linux and Linux64.
>
Now you're breaking trail. For the present, we're focusing on Windows and
Mac.
> I noticed there isn't an archive for 3p-mesa for linux64.
> The one I have used for building linux64 on Kokua is very old.
>
On Mon, Jan 16, 2017 at 6:47 AM, Nicky Perian wrote:
> https://bitbucket.org/lindenlab/p64_3p-openjpeg/pull-requests/2
>
> Please take this in and then provide for the updated archives in the viewer.
> I also received a report that the missing texture issue is in macOS when
> using openjpeg-1.5
On Fri, Jan 13, 2017 at 5:01 PM, Nicky Perian wrote:
Does "autobuild uninstall x" work for autobuild-1.1?
>
You might have to specify "autobuild uninstall --address-size 64 x" (or
-A 64) for the autobuild uninstall command to select the correct build
directory.
__
On Fri, Jan 6, 2017 at 9:23 PM, Nicky Perian wrote:
>>/SAFESEH:NO /NODEFAULTLIB:LIBCMT /DLL_RELEASE=1 /DLL_RLEASE_FOR_DOWNLOAD=1
>> /DNDEBUG
>
> DLL_RLEASE_FOR_DOWNLOAD=1 is the 'E' missing in RELEASE or was the variable
> name changed?
Thank you for pointing that out!
https://bitbucket.org/lind
On Thu, Jan 5, 2017 at 8:52 PM, Nicky Perian wrote:
I was expecting to build from the windows command prompt. I can go into
> Cygwin64 terminal and
> eval "$(autobuild source_environment)" appears to run, but doesn't
> feedback any information that it has.
>
Running that command performs a bunch
On Thu, Jan 5, 2017 at 4:41 PM, Nicky Perian wrote:
>>I do not have enough information to know where in your build environment
> the disconnect lies.
> autobuild source_environment 2>&1 |c:\cygwin64\bin\tee configRel.log
> autobuild --address-size=64 configure -c ReleaseOS --
> -DCMAKE_VERBOSE_M
On Wed, Jan 4, 2017 at 7:43 PM, Nicky Perian wrote:
>I'll make the CMake logic die with an error if it doesn't see the
> >LL_BUILD environment variable. That will at least be less obscure than
> >"unexpected type 'S'", and may help identify the problem you're
> >encountering.
>
> I'm back. Still
On Thu, Dec 22, 2016 at 2:24 PM, Nicky Perian wrote:
> AUTOBUILD_VARIABLES_FILE=C:\Users\Bill\P64\viewer-build-variables\variables
> has been set system wide.
> Within my configure script (a windows batch file) is autobuild
> source_environment and
> autobuild configure
>
> I configure then o
On Thu, Dec 22, 2016 at 12:21 PM, Nicky Perian
wrote:
This is from viewer64 repo w/o changes.
> 0>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
> C2226: syntax error : unexpected type 'S' (C:\Users\Bill\P64\
> viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\
On Thu, Dec 22, 2016 at 8:29 AM, Nicky Perian wrote:
I haven't confirmed, but there may be an issue with having build-vc120-32
> and build-vc120-64 side by side and pickup of library dependencies when
> switching from one build to the other.
>
Please let us know what you find out.
In general, w
On Wed, Dec 14, 2016 at 7:13 PM, Nicky Perian wrote:
While building my own 64 bit fmodex archive I had an issue with "autobuild
> --address-size=64 build".
> autobuild would not build a 64 bit variant. Once I added "export
> AUTOBUILD_PLATFORM_OVERRIDE='darwin64'" I was able to produce the 64 bit
On Dec 3, 2016 7:18 PM, "Nicky Perian" wrote:
With:
(autobuild-1.1) C:\Users\Bill\P64\viewer64>autobuild --address-size=64
configure -c ReleaseOS -- -DCMAKE_VERBOSE_MAKEFILE:BOOL=FALSE
-DLL_TESTS:BOOL=OFF -DPACKAGE:BOOL=FALSE -DOPENAL:BOOL=FALSE
-DFMODEX:BOOL=ON2>&1 | c:\cygwin64\bin\tee c
On Wed, Nov 30, 2016 at 4:04 PM, Callum Prentice (Callum) <
cal...@lindenlab.com> wrote:
Is it just a question of add /LTCG to the jpeglib link command? I see
> that's done via an nmake makefile and then build via a .sln but I think I
> see where to add that command.
>
I think we decided back wh
On Nov 29, 2016 11:11 PM, "Nicky Perian" wrote:
> I am unable to get a windows 64 bit build environment. A learning issue
for me.
> What commands do you use to switch to 64 bit?
I use:
autobuild build --address-size=64
:-)
But I don't yet have a clean 64-bit build on any platform.
___
On Sat, Nov 26, 2016 at 11:37 PM, Nicky Perian
wrote:
Was able to complete a win32 build, but had to revert to openjpeg 1.4. P64
> openjpeg needs work, The lib names in openjpeg.cmake don't match the new
> lib names and there is an archive include file issue. Once the include
> files are provided
gcc version is the
default on jessie, but for now it's moot.
P.S. I will have a better fix for the llceflib problem, along with a fix
for the openjpeg issues, next week. Happy Thanksgiving!
--
NAT LINDEN | Senior Software Engineer | Real Life: Nat Goodspeed LINDEN LAB
| Create Virtual Expe
On Wed, Nov 23, 2016 at 12:24 PM, Nicky Perian
wrote:
This is on a Release. The solution defaulted to Debug and I failed to
> notice.
> So, that raises the question; Why when autobuild source_environment is set
> to Release did it not follow through to the soultion?
>
There is a program called V
n every platform.
Thank you for your insights!
--
NAT LINDEN | Senior Software Engineer | Real Life: Nat Goodspeed LINDEN LAB
| Create Virtual Experiences <https://www.lindenlab.com>
___
Policies and (un)subscribe information available here:
http://wi
d Oct. 14, 2011, 9:32 a.m.)
>
>
> Review request for Viewer, Oz Linden, Jenn, and Nat Goodspeed.
>
>
> Summary
> ---
>
> These changes are to support packaging archives as zip files. This is useful
> when you are using autobuild to construct an archive that
-
>
> (Updated Oct. 13, 2011, 11:10 a.m.)
>
>
> Review request for Viewer, Oz Linden, Jenn, and Nat Goodspeed.
>
>
> Summary
> ---
>
> These changes are to support packaging archives as zip files. This is useful
> when you are using autobuild
> On Oct. 5, 2011, 10:42 a.m., Nat Goodspeed wrote:
> > indra/test/llsdmessagebuilder_tut.cpp, line 87
> > <http://codereview.secondlife.com/r/479/diff/1/?file=7165#file7165line87>
> >
> > Srsly?? I'd much rather see the definition of _PREHASH_Test0 et
visit:
> http://codereview.secondlife.com/r/479/
> ---
>
> (Updated Oct. 4, 2011, 10:23 a.m.)
>
>
> Review request for Viewer and Nat Goodspeed.
>
>
> Summary
> ---
>
> As part of the Linden Lab automation hackathon, I finally h
On Jul 24, 2011, at 6:49 AM, Boroondas Gupte wrote:
> Is that somehow related to the compile flag mismatch mentioned in changeset
> 740d8b8e509f?
>
> If the lib binary indeed deviates from the API, shouldn't we try to fix the
> binary rather than hacking around these problems in the calling vi
31 matches
Mail list logo
