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

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

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

>>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 as i can tell this happens only on 32 bit builds. On Sat, Feb

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

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

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

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 installed files in installed-packages.xml no instal

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

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

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

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? On Fri, Jan 20, 2017 at 9:55 AM, Nat Goodspeed wrote: > On Fri, Jan 20, 201

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

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

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

Moving on to Linux and Linux64. 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. http://s3.amazonaws.com/viewer-source-downloads/install_pkgs/mesa-6.2.1-linux64-20081016.tar.bz2 Will this be updated for P64_3p-mesa? On Fr

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

I had openjpeg 1.5 long ago for some time, the 32bit version wasn't all that better... it was... unreliable. 2017-01-17 18:09 GMT+01:00 Nicky Perian : > >>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 loa

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

We’ve had OpenJPEG 1.5.1 running solidly on Alchemy for years now. I can put together some patches to get it working. --  Cinder Roxley Sent with Airmail On January 17, 2017 at 9:03:11 AM, Nat Goodspeed (n...@lindenlab.com ) wrote: Nat Goodspeed erian wrote

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

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

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

@Nat 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.1. Or, if the problem with 1.5.1 is easily corrected

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

On Fri, 13 Jan 2017 21:53:51 -0600, Nicky Perian wrote: > Texture quality when openjpeg-1.5 is used ranges from poor to piss poor 64 > bit is worse. > Screenshots attached, openjpeg-1.5.1 and openjpeg-1.4.0. These are on the > same viewer with only openjpeg.dll changed. There are "fixes" that wen

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

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. (autobuild-1.1) C:\Users\Bill\P64\Kokua-SL-64>autobuild --address-size 32 uninstall openjpeg usage: autobuild [-V] [-h [HELP

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

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. __

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

more... (autobuild-1.1) C:\Users\Bill\P64\Kokua-SL-64>autobuild --address-size=32 uninstall openjpeg Traceback (most recent call last): File "C:\Users\Bill\Envs\autobuild-1.1\Scripts\autobuild-script.py", line 11, in load_entry_point('autobuild==1.1.3', 'console_scripts', 'autobuild')() Fi

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

>>Documentation that it doesn't is of course welcome (autobuild-1.1) C:\Users\Bill\P64\Kokua-SL-64>autobuild uninstall openjpeg Traceback (most recent call last): File "C:\Users\Bill\Envs\autobuild-1.1\Scripts\autobuild-script.py", line 11, in load_entry_point('autobuild==1.1.3', 'console_s

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

On 2017-01-13 17:01 , Nicky Perian wrote: Does "autobuild uninstall x" work for autobuild-1.1? as far as we know, yes Documentation that it doesn't is of course welcome -- OZ LINDEN | Engineering Director, Second Life email or hangouts: o...@lindenlab.com | Re

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

Does "autobuild uninstall x" work for autobuild-1.1? On Thu, Jan 12, 2017 at 12:59 PM, Callum Prentice (Callum) < cal...@lindenlab.com> wrote: > KDU build here was indistinguishable from the 32bit viewer-release on > first inspection. > > Tried both with full cache and cleaned one. > > On Thu

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

KDU build here was indistinguishable from the 32bit viewer-release on first inspection. Tried both with full cache 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 textu

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 390776087c1d7c83f04af

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 an attempt to directl

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

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

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

> > set (ENV{LL_BUILD} $ENV{LL_BUILD_WINDOWS_RELEASE}) > #message(STATUS "LL_BUILD = '$ENV{LL_BUILD}'") > if ("$ENV{LL_BUILD}" STREQUAL "") > message(FATAL_ERROR "Environment variable LL_BUILD must be set") > endif () > > Above allows configure to complete, but I would like a better place or > be

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 > # Sat Jan 07

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

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 an attempt to directly use those switches. #message(STATUS "AUTOBUILD_VARIABLES_FILE = '$ENV{AUTOBUILD_VARIABLES_FILE}'")

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

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

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

test script #!/bin/bash varsfile="$(mktemp -t vars.)" autobuild source_environment > "$varsfile" source "$varsfile" echo "LL_BUILD = '$LL_BUILD'" Output Bill@BILLAW /cygdrive/c/Users/Bill/P64/viewer64 $ bash buildit.sh LL_BUILD = '' $varsfile contents export AUTOBUILD='C:\Users\Bill\

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

>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. I'm thinking the problem is not being able to execute bash internal commands such as "eval" and "source" from a windows CMD shell. Programs such as "tee"

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

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. Then in the windows command prompt terminal a virtualenv is set to autobuild-1.1 and trying to execu

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

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

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

>>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_MAKEFILE:BOOL=FALSE -DLL_TESTS:BOOL=OFF -DPACKAGE:BOOL=FALSE -

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

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

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 environment variable. That will at

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

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

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

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

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

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\

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

On 2016-12-22 09:58 , Nat Goodspeed wrote: In general, we have tried to isolate build artifacts under the build-whatever directory, in this case build-vc120-32 or build-vc120-64. That includes the libraries installed by autobuild: there should be separate build-vc120-32/packages and build-vc

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

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

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, Nicky Perian > wro

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

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

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

macOS with autobuild-1.1 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 archive. I have not repro'ed beca

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

On Thu, 8 Dec 2016 18:07:42 -0600, Nicky Perian wrote: > Possible Correction, Parts of this were in declined Pull Request #4 > This is windows only Darwin and Linux will need a similar code. Not needed for Darwin (the FMOD Ex Darwin library is a fat binary with both 32 and 64 bits code in it). F

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

Fault: LINK : fatal error LNK1181: cannot open input file 'fmodex_vc.lib' [C:\Users\Bill\P64\viewer64\build-vc120-64\newview\secondlife-bin.vcxproj] Possible Correction, Parts of this were in declined Pull Request #4 This is windows only Darwin and Linux will need a similar code. # HG changeset pa

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

On Sat, 3 Dec 2016 19:12:31 -0600, Nicky Perian wrote: > *only issue is that some script is trying to copy fmodex.dll Speaking of FMOD Ex, you might want to update it. The current version is v4.44.64 and got crash fixes over the one you are using... Henri. ___

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

woohoo - thanks nicky. On Sat, Dec 3, 2016 at 5:12 PM, Nicky Perian wrote: > *only issue is that some script is trying to copy fmodex.dll to the right > place and not (the correct) fmodex64.dll (I fixed the third party package).* > > It's fixed at: > https://bitbucket.org/kokua/viewer64/commits/

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

*only issue is that some script is trying to copy fmodex.dll to the right place and not (the correct) fmodex64.dll (I fixed the third party package).* It's fixed at: https://bitbucket.org/kokua/viewer64/commits/ca4ffedff48cf4ae29622434567a59f6b010708b On Sat, Dec 3, 2016 at 7:07 PM, Callum Prenti

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

Yep - we;re all following along similar tracks by the sound of it Nicky :) With my latest changes, if I unload the VLC plugin (as you say, that needs a little work) the build completes - only issue is that some script is trying to copy fmodex.dll to the right place and not (the correct) fmodex64.

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

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

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

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 configRel.log I get many: No windows64 configur

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

On 11/30/2016 4:11 PM, Nat Goodspeed wrote: > > I think we decided back when switching to VS 2013 that /GL and /LTCG > didn't add enough value for us to bother with them. I think the > expedient fix would be to remove /GL from jpeglib. I'll be the grumpy engineer and ask that 00-COMPILE-LINK-RUN.t

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

Disregard, It was a viewer cmake for llimagej2coj that did not work. ${OPENJPEG_LIBRARIES} ) +if (WINDOWS) + set_target_properties( +llimagej2coj +PROPERTIES +LINK_FLAGS "/MANIFEST:NO /SAFESEH:NO /LTCG /NODEFAULTLIB:LIBCMT" +LINK_FLAGS_DEBUG "/MANIFEST:NO /SAFESEH:NO /NOD

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

>> Is it just a question of add /LTCG to the jpeglib link command? I tired that and it didn't change anything. On Wed, Nov 30, 2016 at 3:04 PM, Callum Prentice (Callum) < cal...@lindenlab.com> wrote: > I'd like to fix that too. > > Is it just a question of add /LTCG to the jpeglib link command?

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

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

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

I'd like to fix that too. 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. On Wed, Nov 30, 2016 at 5:53 AM, Nicky Perian wrote: > Would this be a good time to fix this

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

Would this be a good time to fix this warning? jpeglib.lib(jerror.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance Thanks On Tue, Nov 29, 2016 at 10:30 PM, Nat Goodspeed wrote: > On Nov 29,

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

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. ___

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: > > Was able to c

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

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

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

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 then that just opens the box for un-defines at link. cef fli

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

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 meal, that is, if you can call possum pie traditional. On Thu, Nov 24, 2016 at 4:51 PM, Nat Goodspeed wrote: >

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

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 Visual Studio 12.0\Common7\Tools\VsDevCmd.bat"" > The C:\Us

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

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 Visual Studio 12.0\Common7\Tools\VsDevCmd.bat"" The C:\Users\Bill\P64\viewer-build-variables\convenience script, at defa

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

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

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

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? Error 7 error LNK1181: cannot open input file '..\llimagej2coj\Release\llimagej2coj.lib' C: