[ProbableSpam] Re: [sldev] slviewer on PLAYSTATION3

[Gareth Nelson]

I believe that it can be set as an option to develop.py too, see below:

[gareth at lovely indra]$ python develop.py --help
Usage:   develop.py [options] command [command-options]

Options:
  -h | --help           print this help message
       --standalone     build standalone, without Linden prebuild libraries
       --unattended     build unattended, do not invoke any tools requiring
                        a human response
  -t | --type=NAME      build type ("Debug", "Release", or "RelWithDebInfo")
  -N | --no-distcc      disable use of distcc
  -G | --generator=NAME generator name
                        Windows: VC71 or VS2003 (default), VC80
(VS2005) or VC90 (VS2008)
                        Mac OS X: Xcode (default), Unix Makefiles
                        Linux: Unix Makefiles (default), KDevelop3
Commands:
  build       configure and build default target
  clean       delete all build directories (does not affect sources)
  configure   configure project by running cmake

If you do not specify a command, the default is "configure".


On Thu, Jan 22, 2009 at 2:40 PM, Mike Monkowski <monkowsk at watson.ibm.com> wrote:
> Takeshich Nakamura wrote:
>> (II) FBDEV(0): hardware: ps3fb (video memory: 18240kB)
>
> In indra/llwindow/llwindowsdl.cpp you will find:
>
> 362                     if (0 == rtn)
> 363                     {
> 364                             fp = fopen(fname.c_str(), "r");
> 365                             if (fp)
> 366                             {
> 367                                     rtn = x11_detect_VRAM_kb_fp(fp, ":
> Memory: ");
> 368                                     fclose(fp);
> 369                             }
> 370                     }
>
> Copy this code in the source and paste another copy right after it,
> changing the line inside the if statement to
> rtn = x11_detect_VRAM_kb_fp(fp, "video memory: ");
> This will allow it to get the correct setting for video memory.
>
>>>Is it possible to do a debug build so that the stack trace shows the
>>>line where it crashed?
>>
>>
>> To my regret I don't know how to do a debug.
>> Could you teach me the way of the debugging?
>
> It's a parameter to CMake, but I do not know the Linux parameters.  Are
> there any Linux builders reading this that could help?
>
> Mike
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting privileges
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html