Re: [opensource-dev] Cygwin64

updated: Malwarebytes Cygwin64 All good now. On Tue, Jan 28, 2020 at 2:39 PM Nicky Perian wrote: > I use Malwarebytes and just had to add a pass exception / exemption for > c:\Cygwin64 in order to get a good config and build. > > Just passing along in case others have the same issue

[opensource-dev] Cygwin64

I use Malwarebytes and just had to add a pass exception / exemption for c:\Cygwin64 in order to get a good config and build. Just passing along in case others have the same issue. All worked fine yesterday. ___ Policies and (un)subscribe information avai

Re: [opensource-dev] INTEL driver windows exit graphics corruption

torm-lgpl/rev/ab2ec5c5423b> > > I can't see SL-11341, but it's listed in the Rainbow Viewer release notes as > a crash fix: SL-11341 <https://jira.secondlife.com/browse/SL-11341> BugSplat > Crash: ig7icd32+0x2b07d > https://releasenotes.secondlife.com/viewer/6.

[opensource-dev] INTEL driver windows exit graphics corruption

I saw this documented somewhere. I can't recall where. Does anyone know where? ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting pr

[opensource-dev] LL_TESTS:BOOL=ON

This is a Kokua viewer question but, should apply to other third party viewers and to LL's viewer-release once Linux is re-implemented. Note: all tests pass on MacOs and VS2013. Kokua's branch with no rlv is used as it is closest to viewer-release code. My approach is to use skip(..) to bypass

[opensource-dev] Last linux 3p-vlc-bin

https://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/3p-vlc-bin/rev/315283/arch/Linux/vlc_bin-2.2.3-linux-201606011750-r10.tar.bz2 Can this LL build id 315283 be identified to node from which it was built? ___ Policies and (un)subscribe infor

[opensource-dev] Linux Command Line run with out package

On windows the viewer can be built with _DPACKAGE:BOOL=OFF then with the short-cut properties Start in set to C:\Program Files\viewer-release\indra\newview; you can then start the viewer. I don’t recall how that is done with linux build. I think it is done with parameter passing. Can someone

Re: [opensource-dev] Mac Build - Where do I start?

Step 1. hg clone ssh://h...@bitbucket.org/lindenlab/viewer-build-variables Or hg clone ssh://h...@bitbucket.org/kokua/viewer-build-variables //setup for multiple Xcode installed in /Xcode currently Xcode-9.3 Set an environment variable AUTOBUILD_VARIABLES_FILE=/Users/bill/viewer-build-var

[opensource-dev] Linux 64 build

Has anyone seen this before and know how to resolve it? [ 5%] Building CXX object llcommon/CMakeFiles/llcommon.dir/llallocator.cpp.o In file included from /usr/include/x86_64-linux-gnu/c++/6/bits/c++config.h:507:0, from /usr/include/c++/6/cstring:41, from /home

[opensource-dev] llbase

package llbase has no installation information configured for platform linux64 What is the correction for this? ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before post

Re: [opensource-dev] building a viewer: fails with some undefined variables

Repo is not pretty, but is up to date for linux 64 build > On Mar 31, 2018, at 5:07 PM, Nicky Perian wrote: > > openjpeg-1.5.0.201701152240-windows64-201701152240.tar.bz2 > <https://bitbucket.org/kokua/p64_3p-openjpeg/downloads/openjpeg-1.5.0.201701152240-windows64-20170

Re: [opensource-dev] building a viewer: fails with some undefined variables

ew> I’ll have it current in a day or so. Just put a watch on the repo. > On Mar 31, 2018, at 4:58 PM, Lance Corrimal wrote: > > Am Samstag, 31. März 2018, 20:35:06 CEST schrieb Lance Corrimal: >> Am Samstag, 31. März 2018, 19:57:50 CEST schrieb Nicky Perian: >>> Yes ope

Re: [opensource-dev] building a viewer: fails with some undefined variables

Yes openjpeg-1.5.1 is faulty. openjpeg-1.5.0.180801725-linux64-180801725.tar.bz2 . untested but win and mac versions work. Please publish what you have done. > On Mar 31, 2018, at 12:46

Re: [opensource-dev] building a viewer: fails with some undefined variables

I am limbing along building Kokua on linux with autobuild. If you want you may use my viewer-build-variables repo that has some linux adds. This is a WIP. viewer-build-variables > On Mar 31, 2018, at 8:43 AM, Henri Beauchamp wrote: > > On S

[opensource-dev] Linux viewer manage

http://s3-proxy.lindenlab.com/private-builds-secondlife-com/ct2/3428/8686/viewer_manager-1.0-linux-503417.tar.bz2 Please public this. Just need to get past configure. I know it w

Re: [opensource-dev] CDN

t doing to resolve them? On Fri, Mar 23, 2018 at 5:04 PM, Nicky Perian wrote: > If you have an asset in inventory delivered via cdn how is it not in > inventory? Is that just a distinction as to the different back-end > services? > > On Fri, Mar 23, 2018 at 4:56 PM, Nicky

[opensource-dev] CDN

What is the procedure for determining which CDN node is use for viewer instance. Then, how do you determine which assets are present on that CDN and not present in the viewer? ___ Policies and (un)subscribe information available here: http://wiki.secon

[opensource-dev] Libraries -- Linux

I am in process of rebuilding all linux libraries. I had in 2015 broken apart gtk-atk-pango-glib into individual autobuild 3p type repositories. All of those have performed well in Kokua linux and linux64. I have updated and rebuilt for lack of better terminology, feeder libraries: I have an

Re: [opensource-dev] Linux

ade with the wheezy lines active. > Building non Alex Ivy code went fine with this setup. Should be Jessie!!! > On Feb 2, 2018, at 1:33 PM, Nicky Perian wrote: > > Having read the comments on viewer-release repo and your comment concerning > ABI mismatch I want to submit the

Re: [opensource-dev] Linux

Having read the comments on viewer-release repo and your comment concerning ABI mismatch I want to submit the following: I have put together in a VM Debian / stretch. My past linux builds have been on Ubuntu 14.04 and 16.04 using gcc-4.8 and 4.9. Stretch has neither gcc-4.9 nor libpngl2. Both o

[opensource-dev] Linux

Which version of Debian does LL plan to use? Stretch is at stable. ___ 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

Re: [opensource-dev] macOS build

Fixed. Related to bypass of SL_Launcher. > On Jan 19, 2018, at 1:16 PM, Nicky Perian wrote: > > I have a bit of an issue carrying through with a kokua build. When building > on command line the packaged Kokua.app says it is incomplete and has a stop > sign overlay icon. When

[opensource-dev] macOS build

I have a bit of an issue carrying through with a kokua build. When building on command line the packaged Kokua.app says it is incomplete and has a stop sign overlay icon. When I open and look inside I can run both the SL_Launcher and the Kokua Viewer.app with no problems. When built using Xcode ID

[opensource-dev] autobuild-1.1 on a new macOS xcode8.3.3

Williams-iMac:viewer64 bill$ hg tip changeset: 38165:7c191babc4f6 tag: tip user:Nat Goodspeed date:Fri Dec 15 17:07:37 2017 -0500 summary: MAINT-8087: Update to viewer-manager build 511462 Williams-iMac:viewer64 bill$ autobuild --version autobuild 1.1.7 auto

Re: [opensource-dev] Viewer Manager (Launcher) and AntiVirus

Sounds similar to what I reported here: https://jira.secondlife.com/browse/BUG-134328 I haven't been able to make it fail since. On Thu, Sep 28, 2017 at 8:47 AM, Niran wrote: > Avira (and presumably all others) goes nuts on vmp_util.exe whenever it > appears anywhere, worse, when i configure t

Re: [opensource-dev] macOS -DVIEWER-CHANNEL

The same escape sequence on autobuild-1.0 and code from 5.0.7 works on win, macOS, and Linux. Also, the sequence works correctly on windows for both 5.1.0 and 5.0.7 On Fri, Aug 11, 2017 at 3:10 PM, Cinder Roxley wrote: > GIGO > > > On August 11, 2017 at 2:47:04 PM, Nicky Peri

[opensource-dev] macOS -DVIEWER-CHANNEL

When -DVIEWER_CHANNEL="\"SecondLife Test Channel Assignment\"" is passed on configure a malformed filename is constructed for dmg. This produces Second_Life_SecondLife\\_Test\\_Channel\\_Assignment_5.1.0_x86_64.dmg and the dmg is not useable. ___ Pol

[opensource-dev] Building macOS

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? ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the p

Re: [opensource-dev] viewer64 macOS and cmake-3.5

Resolved with help from Nat and reference to previous fix on windows platform suggested by Nicky D. On Tue, Aug 8, 2017 at 5:53 PM, Nat Goodspeed wrote: > On Tue, Aug 8, 2017 at 6:50 PM, Nicky Perian > wrote: > > I resolved by >> https://bitbucket.org/kokua/viewer-build-v

Re: [opensource-dev] viewer64 macOS and cmake-3.5

..//indra On Tue, Aug 8, 2017 at 9:27 AM, Nicky Perian wrote: > When executing autobuild configure the default source tree looks one > directory level up for the source tree. I have tried to pass > -DCMAKE_SOURCE_DIR= and ../ is always appended to > the configure command. &g

[opensource-dev] viewer64 macOS and cmake-3.5

When executing autobuild configure the default source tree looks one directory level up for the source tree. I have tried to pass -DCMAKE_SOURCE_DIR= and ../ is always appended to the configure command. Is there a command I don't know about? ___ Policies

[opensource-dev] build viewer64 dependencies

https://bitbucket.org/lindenlab/autobuild-1.1 https://bitbucket.org/lindenlab/viewer-build-variables Are these up to date with LL's build system? ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Pl

Re: [opensource-dev] Python errors after update of viewer64

My fault. While working the problem with the "mq" extension I overwrote python with the 64 bit version. Reinstalled 32 bit and it works. On Sat, Jul 22, 2017 at 10:56 PM, Nicky Perian wrote: > Note: there is no problem with autobuild 1.0.3 with default viewer code. > >

[opensource-dev] Python errors after update of viewer64

Note: there is no problem with autobuild 1.0.3 with default viewer code. autobuild --version errors out with -- (autobuild-1.1) C:\Users\Bill\P64\Kokua-SL-64>autobuild --version Traceback (most recent call last): File "C:\Users\Bill\Envs\autobuild-1.1\Scripts\autobuild-script.py", line 6, in

[opensource-dev] Update to mercurial and conflict with "hg policy" local extension.

I recently updated mercurial 4.2.2 and encountered a crash at any hg invocation. hg policy caused the crash when the system extension "mq" was also used. Does hg policy need a rewrite? ___ Policies and (un)subscribe information available here: http://wi

Re: [opensource-dev] viewer64 SL_Launcher

web components on the login page are missing. (jira pending) On Fri, Jun 30, 2017 at 12:11 PM, Nat Goodspeed wrote: > On Fri, Jun 30, 2017 at 12:10 PM, Nicky Perian > wrote: > > I just forced in Nvidia settings for SL_Launcher.exe to use the Nvidia >> driver and the problem

Re: [opensource-dev] viewer64 SL_Launcher

Keep forgetting reply all. To complete the record; I tried to forcing Integrated Graphics (Intel) and Enhanced Graphics (Nvidia) and there is no difference. On Fri, Jun 30, 2017 at 11:02 AM, Nat Goodspeed wrote: > On Fri, Jun 30, 2017 at 11:52 AM, Nicky Perian > wrote: > > On my

Re: [opensource-dev] viewer64 SL_Launcher

" wrote: > >> 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_Lau

Re: [opensource-dev] viewer64 SL_Launcher

iewer update in order to test. Will post to jira once a new SL installer is up. On Fri, Jun 30, 2017 at 8:23 AM, Nat Goodspeed wrote: > 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 : &g

Re: [opensource-dev] viewer64 SL_Launcher

racter (which you can see in the game, but if you > cannot find it that will be fine ) > We are really hope that we could help! > > If you want to report a BUG, please try to tell us more details, such as > related character names and servers. The most important is the exact time >

[opensource-dev] viewer64 SL_Launcher

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:56:56Z INFO: vmp_util.py(58) : getLogger: Running

[opensource-dev] Viewer Channel

Has the escape sequence for viewer channel changed? -DVIEWER_CHANNEL="\"Second Life Project Alex Ivy\"" This picks Test Icon set. The blue top menu bar is present. I would not be using this channel. It is used to prove the point. ___ Policies and (un)su

[opensource-dev] Windows installer slower

Has anyone noticed it is taking longer to install the viewer since the Windows Creator update? Extract of xml files is taking longer on my machine. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev

Re: [opensource-dev] How to deal with FMODEX?

Which platform are you using? You may want to use a non-commercial license of FmodEx. Then, send an email to FMOD support explaining your use of non-commercial provisions of their license and that you need access of FmodEx archives. It may take time for them to respond as there isn't any money in

Re: [opensource-dev] 64 bit viewers build instructions

t builds. On Sat, Feb 18, 2017 at 3:11 PM, Nat Goodspeed wrote: > 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 s

Re: [opensource-dev] 64 bit viewers build instructions

installed files found (C:\Users\Bill\P64\Kokua-SL-64\build-vc120-$AUTOBUILD_ADDRSIZE\packages\installed-packages.xml) On Fri, Jan 13, 2017 at 4:53 PM, Nicky Perian wrote: > > and more... > >>You might have to specify "autobuild uninstall --address-size 64 x" >

Re: [opensource-dev] Linux

edo it from a blank box. On Sun, Jan 29, 2017 at 7:54 PM, Monty Brandenberg wrote: > On 1/29/2017 8:39 PM, Nicky Perian wrote: > > > Will LL use a build system that can be updated as opposed to the current > > out of date system? Hopefully, the build system will be a sta

[opensource-dev] Linux

Questions: Will LL use a build system that can be updated as opposed to the current out of date system? Hopefully, the build system will be a standard off the shelf that everyone can install and without any mix and match specials. Will there be LL developed QA procedures for the linux builds? Gr

Re: [opensource-dev] 64 bit viewers build instructions

, 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. >&

Re: [opensource-dev] 64 bit viewers build instructions

On Fri, Jan 13, 2017 at 4:53 PM, Nicky Perian wrote: > > and more... > >>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. > > (autobu

Re: [opensource-dev] 64 bit viewers build instructions

>>Please forgive me if this should already be on my plate, but I don't >>recall a Jira about the openjpeg 1.5.1 issues? Does 1.5.1 fail to load >>texture files that are correctly handled by 1.5.0? Yes. openjpeg-1.5.1 has so many textures marked as over-sized and unavailable that the viewer is unus

Re: [opensource-dev] 64 bit viewers build instructions

On Fri, Jan 13, 2017 at 4:53 PM, Nicky Perian wrote: > > and more... > >>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. > > (a

Re: [opensource-dev] 64 bit viewers build instructions

ld-vc120-$AUTOBUILD_ADDRSIZE\\packages\\installed-packages.xml' On Fri, Jan 13, 2017 at 4:25 PM, Nat Goodspeed wrote: > On Fri, Jan 13, 2017 at 5:01 PM, Nicky Perian > wrote: > > Does "autobuild uninstall x" work for autobuild-1.

Re: [opensource-dev] 64 bit viewers build instructions

epresentation)) IOError: [Errno 2] No such file or directory: 'C:\\Users\\Bill\\P64\\Kokua-SL-64\\build-vc120-$AUTOBUILD_ADDRSIZE\\packages\\installed-packages.xml' On Fri, Jan 13, 2017 at 4:08 PM, Nicky Perian wrote: > >>Documentation that it doesn't is of course welcome

Re: [opensource-dev] 64 bit viewers build instructions

#x27;).write(llsd.format_pretty_xml(dict_representation)) IOError: [Errno 2] No such file or directory: 'C:\\Users\\Bill\\P64\\Kokua-SL-64\\build-vc120-$AUTOBUILD_ADDRSIZE\\packages\\installed-packages.xml' On Fri, Jan 13, 2017 at 4:04 PM, Oz Linden (Scott Lawrence) < o...@lindenlab.com>

Re: [opensource-dev] 64 bit viewers build instructions

ache and cleaned one. > > On Thu, Jan 12, 2017 at 10:55 AM, Nicky Perian > wrote: > >> [Windows] When I log on with viewer64 w/openjpeg I have a mostly grey >> world. Terrain and most prim textures are grey. Full bright textures and >> my avatar appear normal. Is thi

Re: [opensource-dev] 64 bit viewers build instructions

[Windows] When I log on with viewer64 w/openjpeg I have a mostly grey world. Terrain and most prim textures are grey. Full bright textures and my avatar appear normal. Is this the same with KDU? I haven't a KDU license or I would check myself. On Tue, Jan 10, 2017 at 12:30 PM, Nicky D. wrote: >

Re: [opensource-dev] 64 bit viewers build instructions

brute force setting of LL_BUILD environment variable. There may be a better/smarter way, but it appears to work. # HG changeset patch # User Nicky Perian # Date 1483848353 21600 # Sat Jan 07 22:05:53 2017 -0600 # Node ID 7b4fb3c48718213d1cd8c1e6c6dca0d50c95d78e # Parent

Re: [opensource-dev] 64 bit viewers build instructions

LL list server problem so resending. On Sat, Jan 7, 2017 at 6:32 PM, Nicky Perian wrote: > Snip Variables.cmake > # Switches set here and in 00-Common.cmake must agree with > # https://bitbucket.org/lindenlab/viewer-build-variables/src/tip/variables > # Reading $LL_BUILD is a

Re: [opensource-dev] 64 bit viewers build instructions

LL list server issue so resending On Sat, Jan 7, 2017 at 10:13 PM, Nicky Perian wrote: > brute force setting of LL_BUILD environment variable. > There may be a better/smarter way, but it appears to work. > # HG changeset patch > # User Nicky Perian > # Date 1483848353 21600 >

Re: [opensource-dev] 64 bit viewers build instructions

also, but grep was of no help finding where they are set. Good news is the build completed without the crazy errors encountered earlier. On Sat, Jan 7, 2017 at 2:17 PM, Nat Goodspeed wrote: > On Fri, Jan 6, 2017 at 9:23 PM, Nicky Perian > wrote: > > >>/SAFESEH:NO /NODE

Re: [opensource-dev] 64 bit viewers build instructions

Tools/Binn/:/cygdrive/c/Program Files (x86)/CMake/bin:/cygdrive/c/Python27/Scripts:/usr/bin:/usr/sbin:/cygdrive/c/Program Files (x86)/QuickTime/QTSystem/:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/cygdrive/c/Program Files/TortoiseGit/bin:/cygdrive/c/Pr

Re: [opensource-dev] 64 bit viewers build instructions

AM, Argent wrote: > Try creating the env file and reading it. Think about how the UNIX > environment works. The CMD shell and probably even PowerShell won't see it. > > On Jan 5, 2017 19:52, "Nicky Perian" wrote: > > I was expecting to build from the windows command

Re: [opensource-dev] 64 bit viewers build instructions

rom the windows command prompt. On Thu, Jan 5, 2017 at 4:29 PM, Nat Goodspeed wrote: > 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

Re: [opensource-dev] 64 bit viewers build instructions

s\doxygen\bin;C:\Program Files (x86)\Midnight Commander;C:\Users\Bill\AppData\Local\Microsoft\WindowsApps; _OLD_VIRTUAL_PROMPT=$P$G TERM=cygwin HOME=/home/Bill (autobuild-1.1) C:\Users\Bill\P64\viewer64> On Thu, Jan 5, 2017 at 1:16 PM, Nat Goodspeed wrote: > On Wed, Jan 4, 2017 at 7:43 PM, N

Re: [opensource-dev] windows build issues

obuild and follow FS build instructions. Just now tried FS -m64 configure and it is complaining about boost being overwriting something that is already present even though configuring from scratch. On Thu, Jan 5, 2017 at 5:59 AM, Nicky Perian wrote: > Nope. > O

Re: [opensource-dev] windows build issues

hat autobuild in https://bitbucket.org/lindenlab/autobuild-1.0 > support -m64? > > Am 04.01.2017 um 16:06 schrieb Nicky Perian: > > I have never used ssh://h...@bitbucket.org/NickyP/fs-autobuild-1.0. It was > put there for reference only. > This is what you should be using https

Re: [opensource-dev] 64 bit viewers build instructions

Backed out changeset: 54c80e27a54f restore build switches Building now. Did notice other avatars are grey. Mine looks fine. On Wed, Jan 4, 2017 at 6:43 PM, Nicky Perian wrote: > >I'll make the CMake logic die with an error if it doesn't see the > >LL_BUILD environme

Re: [opensource-dev] 64 bit viewers build instructions

hiccup. Nicky On Thu, Dec 22, 2016 at 2:51 PM, Nat Goodspeed wrote: > 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 s

Re: [opensource-dev] windows build issues

ork, at least it starts to work. it > dies at the point where it tries to download the prebuild packages. > here is the complete output of my problem: > > http://susepaste.org/33664691 > > > > > > Am 04.01.2017 um 19:58 schrieb Nicky Perian: > > cd into local repo

Re: [opensource-dev] windows build issues

cd into local repo firestorm, viewer-release are any other. >From there enter autobuild --version an absolute path should not be needed to reach autobuild. It should give the version, If not, your path is not set or you may need to set AUTOBUILD='pathtoautobuild/bin/autobuild' environment variabl

Re: [opensource-dev] windows build issues

unden > > > Am 04.01.2017 um 13:46 schrieb Lance Corrimal: > > Am Mittwoch, 4. Januar 2017, 06:23:32 CET schrieb Nicky Perian: > >> autobuild --version > >> > >> s/b 1.0 unless your on the viewer64 repo. > >> > > 64bit here.. using your autobuil

Re: [opensource-dev] windows build issues

autobuild --version s/b 1.0 unless your on the viewer64 repo. On Wed, Jan 4, 2017 at 2:25 AM, Lance Corrimal wrote: > Hi, > > I am in the process of rebuilding my windows build environment... > > [obvious steps removed] > > ... and what I get from autobuild configure is: > > > CMake Error at c

Re: [opensource-dev] 64 bit viewers build instructions

I have a local repo of https://bitbucket.org/lindenlab/viewer-build-variables as a sibling of viewer64. Just now pulled and updated it. 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 autobuil

Re: [opensource-dev] 64 bit viewers build instructions

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\LLPhysicsExtensionsStubImpl.cpp) 10> c:\users\bill\p64\

Re: [opensource-dev] 64 bit viewers build instructions

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. On Wed, Dec 14, 2016 at 7:56 PM, Nat Goodspeed wrote: > On Wed, Dec 14, 2016 at 7:13 PM, Nick

Re: [opensource-dev] 64 bit viewers build instructions

archive. I have not repro'ed because once I had the archive I didn't care to go back through it. Just an fyi. Nicky On Fri, Dec 9, 2016 at 4:11 AM, Henri Beauchamp wrote: > On Thu, 8 Dec 2016 18:07:42 -0600, Nicky Perian wrote: > > > Possible Correction, Parts of this

Re: [opensource-dev] 64 bit viewers build instructions

changeset patch # User Nicky Perian # Date 1480710394 21600 # Fri Dec 02 14:26:34 2016 -0600 # Node ID f70e1917b449af35d719e3a572694c6768d87254 # Parent 290ae1d71523ee22a079421d4fdeee4225a9f7cc Provide for x64 FMOD ex libraries diff -r 290ae1d71523 -r f70e1917b449 indra/cmake/Copy3rdParty

Re: [opensource-dev] 64 bit viewers build instructions

on Monday. > > > > On Sat, Dec 3, 2016 at 4:35 PM, Nat Goodspeed wrote: > >> 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 Releas

Re: [opensource-dev] 64 bit viewers build instructions

merged in. Attached is the configure log. On Fri, Dec 2, 2016 at 9:25 AM, Nicky Perian wrote: > RE: Windows 64 bit cmake identifier. > What cmake variable is going to be used within cmake for branching 32 vs > 64 bit builds? > > Example FMODEX.cmake. > > Friestorm u

Re: [opensource-dev] 64 bit viewers build instructions

RE: Windows 64 bit cmake identifier. What cmake variable is going to be used within cmake for branching 32 vs 64 bit builds? Example FMODEX.cmake. Friestorm uses if( NOT ND_BUILD64BIT_ARCH ) which is very specific to their build system. So, will it be ARCH or ADDRESS_SIZE or a new variable comb

Re: [opensource-dev] 64 bit viewers build instructions

:NO /SAFESEH:NO /NODEFAULTLIB:LIBCMTD" +) +endif (WINDOWS) \ No newline at end of file On Wed, Nov 30, 2016 at 3:48 PM, Nicky Perian wrote: > >> Is it just a question of add /LTCG to the jpeglib link command? > > I tired that and it didn't change anything. >

Re: [opensource-dev] 64 bit viewers build instructions

TCG 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. > > On Wed, Nov 30, 2016 at 5:53 AM, Nicky Perian > wrote: > >> Would this be a good time to fix this warning? >>

Re: [opensource-dev] 64 bit viewers build instructions

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 > > :-) > > Bu

Re: [opensource-dev] 64 bit viewers build instructions

Thanks, I'll return to poking at it. 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? On Tue, Nov 29, 2016 at 8:37 PM, Nat Goodspeed wrote: > On Sat, Nov 26, 2016 at 11:37 PM, Nicky Perian > wrote: >

Re: [opensource-dev] 64 bit viewers build instructions

cef flip issues have returned. On Thu, Nov 24, 2016 at 5:49 PM, Nicky Perian wrote: > Happy Thanksgiving. @Nat, I really didn't expect an answer until next > week, hoping it was minimal interruption to your Thanksgiving . > > My family just finished a wonderful traditional mea

Re: [opensource-dev] 64 bit viewers build instructions

wrote: > On Thu, Nov 24, 2016 at 2:19 PM, Nicky Perian > wrote: > > Which windows command prompt should be used? I have used Developer Command >> Prompt for VS2013 >> which defaults to 32 bit tool set via %comspec% /k ""C:\Program Files >> (x86)\Microsoft

Re: [opensource-dev] 64 bit viewers build instructions

convenience script set the system build variables and pick the proper tool set regardless of which terminal is used? Next question, what distro and gcc version is being used for linux builds? On Wed, Nov 23, 2016 at 12:11 PM, Nat Goodspeed wrote: > On Wed, Nov 23, 2016 at 12:24 PM, Nicky Perian >

Re: [opensource-dev] 64 bit viewers build instructions

1083: Cannot open include file: 'opj_stdint.h': No such file or directory C:\Users\Bill\P64\viewer64\build-vc120-32\packages\include\openjpeg\openjpeg.h 94 1 llimagej2coj On Wed, Nov 23, 2016 at 10:06 AM, Nicky Perian wrote: > Complete the record on opensource-dev. > >

[opensource-dev] Fwd: 64 bit viewers build instructions

Complete the record on opensource-dev. -- Forwarded message -- From: Nicky Perian Date: Wed, Nov 23, 2016 at 9:13 AM Subject: Re: 64 bit viewers build instructions To: Nat Goodspeed Cc: "Oz Linden (Scott Lawrence)" Thanks, I'm trying to build 32 bit windo

Re: [opensource-dev] Darwin build failure

years ago and it was a not having llbase.py installed. I can't recall the solution, but it was simple. On Wed, Nov 16, 2016 at 10:10 PM, Nicky Perian wrote: > Failure: > Mini:viewer-release nicky$ python --version > Python 2.7.12 > Mini:viewer-release nicky$ /opt/lo

[opensource-dev] Darwin build failure

Failure: Mini:viewer-release nicky$ python --version Python 2.7.12 Mini:viewer-release nicky$ /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/autobuild configure -v -c RelWithDebInfoOS -- -DLL_TESTS:BOOL=OFF -DFMODEX:BOOL=ON -DOPENAL:BOOL=OFF -DPACKAGE:BOOL=ON -DQUICKTIME:BOOL=ON -D

Re: [opensource-dev] 64 bit lib archives

Needed to update autobuild to 1.1 pip install hg+http://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild --upgrade Worked ok. autobuild build --address-size 64 autobuild package --address-size 64 Not a friendly transition between 32 and 64 bit though. On Wed, Oct 26, 2016 at 5:17 PM, Nicky

[opensource-dev] 64 bit lib archives

Starting to dabble a bit with p64_3p-zlib. At autobuild build --address-size 32 getting: ../build-cmd.sh: line 44: AUTOBUILD_WIN_CMAKE_GEN: unbound variable Any idea what I am doing wrong? ___ Policies and (un)subscribe information available here: http:

Re: [opensource-dev] Stuck on stupid

e add_dependencies to fail. *Then:* configure with -DRELEASE_CRASH_REPORTING:BOOL=ON and generate_breakpad_symbols project is included in the build. On Fri, Jul 22, 2016 at 3:51 PM, Nicky Perian wrote: > I have done before and was surprised how simple it was. But... > > How do

[opensource-dev] Stuck on stupid

I have done before and was surprised how simple it was. But... How do you tell the viewer build to provide the breakpad symbol generation in the build project? It should produce an archive of the symbols. ___ Policies and (un)subscribe information avail

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

Should avi abd wmv files be moved from cef to vlc plugin. Made a change locally and it worked. Movie (Windows Media WMV) movie media_plugin_libvlc Movie (AVI) movie media_plugin_libvlc On Sat, Jun 4, 2016 at 9:20 AM, Henri Beauchamp wrote: > On Sat, 4 Jun 2016 06:52:58 -0500, A

[opensource-dev] glib-networking and gstreamer stream processing.

This was not the SL viewer, I attempted to play an mp4 file that at one time played without issue. Messages logged: pid:27246: (media plugin) receiveMessage:1159: >Got size change instruction from application with shm name: /LL27034_5 - size is 1 x 1 pid:27246: (media plugin) receiveMessage

Re: [opensource-dev] Firewall block of media files

After more thinking about it this must have been using gstreamer that allowed direct play of mp4 mov etc. I'm busy with merging kokua up to v-r tip for now, but will investigate over the weekend and post results afterward. On Thu, May 19, 2016 at 1:48 PM, Dax Dupont wrote: > Which is expected be

Re: [opensource-dev] Firewall block of media files

It may have been parcel media, but I remember them playing. On Thu, May 19, 2016 at 1:34 PM, Whirly Fizzle wrote: > That will not play in a web browser though, the file needs to be > downloaded to play it. > Being able to play dropbox links like that via MOAP never worked in any SL > viewer as f

  1   2   3   4   5   >