Re: [opensource-dev] Setup a Release configuration for VS2010 build -- Need testers.

2011-03-06 Thread Ima Mechanique
 Applied change to autobuild.xml for -VC10msbuildRelease.
 Applied change to CMakeLists.txt to remove the Colon from  /MAP
 the colon was being passed through cmake and causing a bad path.
 
 Failed in an attempt to place the CMakeList.txt change to Review Board.
 Oz's repository is out of sync with mine. And, mine isn't a review board 
 repository.
 
 https://bitbucket.org/NickyP/viewer-autobuild2010-wip
 
 @ WolfPup Know you intended to work on this. I was trying to work 32 bit 
 memory 
 issues and was trying to see if release was better and it fell in place. 
 Sorry, 
 if I stepped on your toes.
 Memory is slightly better. On XP 32bit 1:20 minutes before crash.
 
 Nicky

Don't know exactly what needed testing, but it compiled  for me on Win
XP Pro 64-bit, using VCE 2010.
commands used
autobuild configure -c VC10msbuildRelWithDebInfo -- -DLL_TESTS:BOOL=OFF
autobuild build --no-configure -c VC10msbuildRelWithDebInfo

Managed to log into SL today with it (last night I couldn't stay
connected for more than 30 seconds). All appears to work except for
audio (I assumed FMOD was disabled).

--
Ima Mechanique
ima.mechanique(at)blueyonder.co.uk


___
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


[opensource-dev] Review Request: Incorrect library names in the windows section of XmlRpcEpi.cmake

2011-03-06 Thread Nicky Perian

---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/178/
---

Review request for Viewer.


Summary
---

Incorrect library names in the windows section of XmlRpcEpi.cmake


This addresses bug OPEN-42.


Diffs
-

  doc/contributions.txt 8a50c1a8428d 
  indra/cmake/XmlRpcEpi.cmake 8a50c1a8428d 

Diff: http://codereview.secondlife.com/r/178/diff


Testing
---

patched and correct libraries were found.


Thanks,

Nicky

___
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] Review Request: Incorrect library names in the windows section of XmlRpcEpi.cmake

2011-03-06 Thread Nicky Perian

---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/178/#review424
---


Not needed LL changed the autobuild.xml libraries and cmake and I was using an 
older autobuild.xml.

- Nicky


On March 6, 2011, 1:39 p.m., Nicky Perian wrote:
 
 ---
 This is an automatically generated e-mail. To reply, visit:
 http://codereview.secondlife.com/r/178/
 ---
 
 (Updated March 6, 2011, 1:39 p.m.)
 
 
 Review request for Viewer.
 
 
 Summary
 ---
 
 Incorrect library names in the windows section of XmlRpcEpi.cmake
 
 
 This addresses bug OPEN-42.
 
 
 Diffs
 -
 
   doc/contributions.txt 8a50c1a8428d 
   indra/cmake/XmlRpcEpi.cmake 8a50c1a8428d 
 
 Diff: http://codereview.secondlife.com/r/178/diff
 
 
 Testing
 ---
 
 patched and correct libraries were found.
 
 
 Thanks,
 
 Nicky
 


___
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

[opensource-dev] Added repository. Windows Autobuild

2011-03-06 Thread Nicky Perian
Last week I merged in viewer-development 
into https://bitbucket.org/NickyP/viewer-autobuild2010-wip. Yesterday, I found 
some pre-autobuild behavior. While not broken it does lead to maintenance 
problems when trying to submit changes that are intended to correct autobuild 
issues. Change set 14899 is an example of one such issue. This was chasing a 
problem present in viewer-development but not in viewer-autobuild2010. That 
section of code isn't in viewer-autobuild2010 at all. The code from that change 
set will most likely be in viewer-development someday and was likely a make 
work 
removal in viewer-autobuild 2010. It concerns making a secondlife-bin.map when 
in Release. Since the code to make a map isn't present there is no map in 
viewer-autobuild2010.

Repository http://bitbucket.org/NickyP/viewer-autobuild2010-msbuild, added 
today, has only those viewer-development changes that were present in the 
source 
repository from which it was forked.  I have added changes and tested builds 
for 
 VC10msbuildRelease and VC10msbuildRelWithDebInfo which included configure, 
build, and log to aditi. This repository will be maintained to track its fork 
and only have commits of those changes and necessary changes to use with 
msbuild.

I am sorry for any confusion this may have caused.

Nicky


  ___
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] Is 'STANDALONE' confusing?

2011-03-06 Thread Ima Mechanique
 On 2011-03-03 1:45, Philippe (Merov) Bossut wrote:
 
  Dropping privately built 3rd party libs though was always a bit of a 
  black art. Now that most 3rd party libs have a public repo available 
  at lindenlab/3p-package though, you have another possibility which 
  is to build the package yourself and point autobuild.xml to it using a 
  file:///path url (don't forget to also change the md5 hash...). 
  That will extract libs and includes and drop them in 
  build-plat/packages. I experimented with that in OPEN-6 and it works 
  fine.
 
 I'd really like to some experiences from open devs trying to use this 
 method.  Essentially, it means maintaining your own version of the 
 autobuild configuration file (either in autobuild.xml, being careful not 
 to include those changes in any changeset meant to be merged to 
 viewer-development, or by using a copy and pointing to the copy either 
 with a --config-file option to autobuild or with the 
 AUTOBUILD_CONFIG_FILE environment variable).
 
 Even if you build your own prebuilds, you probably won't need to do it 
 very often - check them all out once, build each one, construct the 
 packages portion of the autobuild.xml file and then copy it into any 
 working copy you've got for doing viewer work.  The only time you should 
 need to rebuild any of them is when a package is modified either by you 
 or from upstream.

I spent 3-4 hours playing with this today. I started by updating local
copies of the 3p repoes,and was encouraged to see several commits for
VS2010 compatibility. That didn't last long though, as when I checked
the autobuild.xml files there was nothing in them for Windows users :-(
There are entries under platform claiming to be windows, but in reality
all but one appear to be for cygwin only, and I'm not sure about the
last. Cygwin really needs to be treated as a platform in its own right
here. Otherwise when the OS community creates *real* windows
configurations you will not be able to accept them because of a naming
conflict.
Not to mention it annoys Windows users to see a window entry and it
doesn't work. ;-)

I tried using the cygwin configs, but was unable to get any of them
working because of errors calling python scripts. Pretty sure the path
isn't being translated back into MSDOS style. I tried the note on the
https://wiki.secondlife.com/wiki/Autobuild page, installing the module
and including the Script directory in path, but that didn't work either.


--
Ima Mechanique
ima.mechanique(at)blueyonder.co.uk


___
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