From sldev at vlan1000.net Mon Aug 6 03:44:49 2018 From: sldev at vlan1000.net (Alex) Date: Mon, 06 Aug 2018 20:44:49 +1000 Subject: [opensource-dev] compiling viewer-release on linux Message-ID: <7552e86035bc725410285f685b2a590d@vlan1000.net> Hi All, I am being brave and giving this a go.. Can someone explain this: checking llappearance_utility downloading llappearance_utility: http://s3-proxy.lindenlab.com/private-builds-secondlife-com/hg/repo/p64_viewer-llappearance-utility/rev/317266/arch/Linux/installer/llappearance_utility-0.0.1-linux-317266.tar.bz2 to /var/tmp/alex/install.cache/llappearance_utility-0.0.1-linux-317266.tar.bz2 error: HTTP Error 401: Unauthorized Is this actually needed? If I grep through the sources, I find only linux references to llappearanceutility - nothing for windows, mac.. And for LLAppearanceUtility.cmake (which gets included by CMakeLists.txt) it seems relevant only for linux? Why? # -*- cmake -*- include(Prebuilt) include(Boost) # Linux proprietary build only if (INSTALL_PROPRIETARY) if(LINUX) use_prebuilt_binary(llappearance_utility) set(LLAPPEARANCEUTILITY_SRC_DIR ${LIBS_PREBUILT_DIR}/llappearanceutility/src) set(LLAPPEARANCEUTILITY_BIN_DIR ${CMAKE_BINARY_DIR}/llappearanceutility) endif (LINUX) endif (INSTALL_PROPRIETARY) Assuming its not needed, how can I drop the requirement for this during the configure phase of the build? -- Kind Regards, Alex. From cinder at alchemyviewer.org Wed Aug 8 13:25:52 2018 From: cinder at alchemyviewer.org (Cinder Roxley) Date: Wed, 8 Aug 2018 16:25:52 -0400 Subject: [opensource-dev] compiling viewer-release on linux In-Reply-To: <7552e86035bc725410285f685b2a590d@vlan1000.net> References: <7552e86035bc725410285f685b2a590d@vlan1000.net> Message-ID: On August 6, 2018 at 5:44:54 AM, Alex (sldev at vlan1000.net) wrote: Hi All, I am being brave and giving this a go.. Can someone explain this: (SNIP) Assuming its not needed, how can I drop the requirement for this during the configure phase of the build? You are building with the proprietary libs. You need to build an opensource autobuild target: autobuild configure -c ReleaseOS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20180808/6b210df9/attachment.htm From sldev at vlan1000.net Wed Aug 8 18:23:19 2018 From: sldev at vlan1000.net (Alex) Date: Thu, 09 Aug 2018 11:23:19 +1000 Subject: [opensource-dev] compiling viewer-release on linux In-Reply-To: References: <7552e86035bc725410285f685b2a590d@vlan1000.net> Message-ID: <137fcdc03115b6e35bfcc272a8d71f37@vlan1000.net> On 2018-08-09 06:25, Cinder Roxley wrote: > autobuild configure -c ReleaseOS You are building with the proprietary libs. You need to build an opensource autobuild target: > _______________________________________________ Ty :) Is there a way to have the viewer use FMOD by default instead of alsa? I have provisioned FMOD and it only gets used if I uncomment a line in the startup script: export LL_BAD_OPENAL_DRIVER=x That will make the viewer use FMOD and it works perfectly. Is editing the script the only way to make it default? Cheers, A. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20180809/1dec3a0e/attachment.htm From nickyperian at gmail.com Tue Aug 21 12:26:33 2018 From: nickyperian at gmail.com (Nicky Perian) Date: Tue, 21 Aug 2018 14:26:33 -0500 Subject: [opensource-dev] Linux Command Line run with out package Message-ID: <5477F211-DCA8-454D-A08F-0A198A2A032C@gmail.com> 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 refresh my memory? Thanks, Nicky