Re: [opensource-dev] Problem compiling llcommon on viewer 2.1 beta

2010-06-25 Thread Philippe (Merov) Bossut
Hi Marine,

I just built the tip of viewer-external on my Windows XP machine with no
problem. Could you tell us a bit more on how you get things together? Do you
use develop.py? Do you do a standalone build? Which Solution Configuration
are you building?

Cheers,
- Merov

On Thu, Jun 24, 2010 at 1:30 PM, Marine Kelley wrote:

> Hello,
>
> I am having the following link error when trying to compile the llcommon
> project on Viewer 2.1 beta extracted from viewer-external :
>
> 1>-- Build started: Project: llcommon, Configuration: Release Win32
> --
> 1>Linking...
> 1>   Creating library
> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.lib and object
> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.exp
> 1>exception_handler.lib(exception_handler.obj) : error LNK2019: unresolved
> external symbol "__declspec(dllimport) void __cdecl std::_Throw(class
> stdext::exception const &)" (__imp_?_th...@std@@yaxabvexcept...@stdext@@@Z)
> referenced in function "public: void __thiscall
> stdext::exception::_Raise(void)const " (?_ra...@exception@stdext@@QBEXXZ)
> 1>exception_handler.lib(exception_handler.obj) : error LNK2001: unresolved
> external symbol "__declspec(dllimport) void (__cdecl*
> std::_Raise_handler)(class stdext::exception const &)"
> (__imp_?_raise_hand...@std@@3p6axabvexcept...@stdext@@@ZA)
> 1>D:\SL\linden\indra\build-vc80\sharedlibs\Release\llcommon.dll : fatal
> error LNK1120: 2 unresolved externals
> 1>Build log was saved at
> "file://d:\SL\linden\indra\build-vc80\llcommon\llcommon.dir\Release\BuildLog.htm"
> 1>llcommon - 3 error(s), 0 warning(s)
> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==
>
>
> I have copied the libraries from libraries/i686-win32/lib/debug/ to
> libraries/i686-win32/lib/release/ but it didn't help. Does anyone know what
> to do please ? It seems to come from the new google_breakpad library but I
> don't know anything about it. I just know it was not there before.
>
> Thanks for any piece of help,
> Marine
>
> ___
> 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
>
___
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] Problem compiling llcommon on viewer 2.1 beta

2010-06-25 Thread Marine Kelley
Hi Merov, thank you for looking into this !

I'm on Windows 7, trying to compile viewer-external as I always do :

- I unzip the artwork from version 2.0.0 (knowing that I will have to
complete it with some of the icons from the official 2.1, like the icons for
the system folders)
- I unzip a very old library zip file of mine (it is more than 2 years old
and contains ares, fmod and all, but is still operational at least until
2.0.1)
- I run VC 2005, select the "Release" configuration, go to Configuration
Manager, uncheck all the "tests" and "integration" projects (plus "package")
- I open the Properties window on secondlife-bin and remove the /Zm1000
option from the command line
- I build the whole thing

But even just building llcommon will give me the error I mentioned, no need
to build the whole solution. This is the first time I get this error, and
since I noticed that google_breakpad was not part of the viewer before, and
surprisingly it uses an exception_handler.lib that does not provide the
correct functions...

That's all I can think of but I'm sure there is more.

Thanks again,
Marine



On 25 June 2010 22:39, Philippe (Merov) Bossut  wrote:

> Hi Marine,
>
> I just built the tip of viewer-external on my Windows XP machine with no
> problem. Could you tell us a bit more on how you get things together? Do you
> use develop.py? Do you do a standalone build? Which Solution Configuration
> are you building?
>
> Cheers,
> - Merov
>
> On Thu, Jun 24, 2010 at 1:30 PM, Marine Kelley wrote:
>
>> Hello,
>>
>> I am having the following link error when trying to compile the llcommon
>> project on Viewer 2.1 beta extracted from viewer-external :
>>
>> 1>-- Build started: Project: llcommon, Configuration: Release Win32
>> --
>> 1>Linking...
>> 1>   Creating library
>> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.lib and object
>> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.exp
>> 1>exception_handler.lib(exception_handler.obj) : error LNK2019: unresolved
>> external symbol "__declspec(dllimport) void __cdecl std::_Throw(class
>> stdext::exception const &)" (__imp_?_th...@std@@yaxabvexcept...@stdext@@@Z)
>> referenced in function "public: void __thiscall
>> stdext::exception::_Raise(void)const " (?_ra...@exception@stdext@@QBEXXZ)
>> 1>exception_handler.lib(exception_handler.obj) : error LNK2001: unresolved
>> external symbol "__declspec(dllimport) void (__cdecl*
>> std::_Raise_handler)(class stdext::exception const &)"
>> (__imp_?_raise_hand...@std@@3p6axabvexcept...@stdext@@@ZA)
>> 1>D:\SL\linden\indra\build-vc80\sharedlibs\Release\llcommon.dll : fatal
>> error LNK1120: 2 unresolved externals
>> 1>Build log was saved at
>> "file://d:\SL\linden\indra\build-vc80\llcommon\llcommon.dir\Release\BuildLog.htm"
>> 1>llcommon - 3 error(s), 0 warning(s)
>> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
>> ==
>>
>>
>> I have copied the libraries from libraries/i686-win32/lib/debug/ to
>> libraries/i686-win32/lib/release/ but it didn't help. Does anyone know what
>> to do please ? It seems to come from the new google_breakpad library but I
>> don't know anything about it. I just know it was not there before.
>>
>> Thanks for any piece of help,
>> Marine
>>
>> ___
>> 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
>>
>
>
> ___
> 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
>
___
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] Problem compiling llcommon on viewer 2.1 beta

2010-06-25 Thread Latif Khalifa
I just tried building viewer-external on my windows 7  - 64, had no
linking issues that you reported. (I also have pretty old library for
stuff like fmod, but those are not changed anyway).

Latif

On Fri, Jun 25, 2010 at 11:30 PM, Marine Kelley  wrote:
> Hi Merov, thank you for looking into this !
>
> I'm on Windows 7, trying to compile viewer-external as I always do :
>
> - I unzip the artwork from version 2.0.0 (knowing that I will have to
> complete it with some of the icons from the official 2.1, like the icons for
> the system folders)
> - I unzip a very old library zip file of mine (it is more than 2 years old
> and contains ares, fmod and all, but is still operational at least until
> 2.0.1)
> - I run VC 2005, select the "Release" configuration, go to Configuration
> Manager, uncheck all the "tests" and "integration" projects (plus "package")
> - I open the Properties window on secondlife-bin and remove the /Zm1000
> option from the command line
> - I build the whole thing
>
> But even just building llcommon will give me the error I mentioned, no need
> to build the whole solution. This is the first time I get this error, and
> since I noticed that google_breakpad was not part of the viewer before, and
> surprisingly it uses an exception_handler.lib that does not provide the
> correct functions...
>
> That's all I can think of but I'm sure there is more.
>
> Thanks again,
> Marine
>
>
>
> On 25 June 2010 22:39, Philippe (Merov) Bossut  wrote:
>>
>> Hi Marine,
>>
>> I just built the tip of viewer-external on my Windows XP machine with no
>> problem. Could you tell us a bit more on how you get things together? Do you
>> use develop.py? Do you do a standalone build? Which Solution Configuration
>> are you building?
>>
>> Cheers,
>> - Merov
>>
>> On Thu, Jun 24, 2010 at 1:30 PM, Marine Kelley 
>> wrote:
>>>
>>> Hello,
>>>
>>> I am having the following link error when trying to compile the llcommon
>>> project on Viewer 2.1 beta extracted from viewer-external :
>>>
>>> 1>-- Build started: Project: llcommon, Configuration: Release Win32
>>> --
>>> 1>Linking...
>>> 1>   Creating library
>>> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.lib and object
>>> D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.exp
>>> 1>exception_handler.lib(exception_handler.obj) : error LNK2019:
>>> unresolved external symbol "__declspec(dllimport) void __cdecl
>>> std::_Throw(class stdext::exception const &)"
>>> (__imp_?_th...@std@@yaxabvexcept...@stdext@@@Z) referenced in function
>>> "public: void __thiscall stdext::exception::_Raise(void)const "
>>> (?_ra...@exception@stdext@@QBEXXZ)
>>> 1>exception_handler.lib(exception_handler.obj) : error LNK2001:
>>> unresolved external symbol "__declspec(dllimport) void (__cdecl*
>>> std::_Raise_handler)(class stdext::exception const &)"
>>> (__imp_?_raise_hand...@std@@3p6axabvexcept...@stdext@@@ZA)
>>> 1>D:\SL\linden\indra\build-vc80\sharedlibs\Release\llcommon.dll : fatal
>>> error LNK1120: 2 unresolved externals
>>> 1>Build log was saved at
>>> "file://d:\SL\linden\indra\build-vc80\llcommon\llcommon.dir\Release\BuildLog.htm"
>>> 1>llcommon - 3 error(s), 0 warning(s)
>>> == Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
>>> ==
>>>
>>>
>>> I have copied the libraries from libraries/i686-win32/lib/debug/ to
>>> libraries/i686-win32/lib/release/ but it didn't help. Does anyone know what
>>> to do please ? It seems to come from the new google_breakpad library but I
>>> don't know anything about it. I just know it was not there before.
>>>
>>> Thanks for any piece of help,
>>> Marine
>>>
>>> ___
>>> 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
>>
>>
>> ___
>> 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
>
>
> ___
> 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
>
___
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] Problem compiling llcommon on viewer 2.1 beta

2010-06-25 Thread Nicky Perian
I built viewer-external on 6/19. Used Vista 32 and VC++Express 2005. Took 5 
builds. Logs and steps taken are here. 
This was all the way to a setup.exe.






From: Marine Kelley 
To: Philippe (Merov) Bossut 
Cc: opensource-dev@lists.secondlife.com
Sent: Fri, June 25, 2010 4:30:53 PM
Subject: Re: [opensource-dev] Problem compiling llcommon on viewer 2.1 beta

Hi Merov, thank you for looking into this !

I'm on Windows 7, trying to compile viewer-external as I always do :

- I unzip the artwork from version 2.0.0 (knowing that I will have to complete 
it with some of the icons from the official 2.1, like the icons for the system 
folders)
- I unzip a very old library zip file of mine (it is more than 2 years old and 
contains ares, fmod and all, but is still operational at least until 2.0.1)
- I run VC 2005, select the "Release" configuration, go to Configuration 
Manager, uncheck all the "tests" and "integration" projects (plus "package")
- I open the Properties window on secondlife-bin and remove the /Zm1000 option 
from the command line
- I build the whole thing

But even just building llcommon will give me the error I mentioned, no need to 
build the whole solution. This is the first time I get this error, and since I 
noticed that google_breakpad was not part of the viewer before, and 
surprisingly it uses an exception_handler.lib that does not provide the correct 
functions...

That's all I can think of but I'm sure there is more.

Thanks again,
Marine




On 25 June 2010 22:39, Philippe (Merov) Bossut  wrote:

Hi Marine,
>
>I just built the tip of viewer-external on my Windows XP machine with no 
>problem. Could you tell us a bit more on how you get things together? Do you 
>use develop.py? Do you do a standalone build? Which Solution Configuration are 
>you building?
>
>Cheers,
>- Merov
>
>
>On Thu, Jun 24, 2010 at 1:30 PM, Marine Kelley  wrote:
>
>>>
>>Hello,
>>
>>I am having the following link error when trying to compile the llcommon 
>>project on Viewer 2.1 beta extracted from viewer-external :
>>
>>1>-- Build started: Project: llcommon, Configuration: Release Win32 --

>>
>>
>>1>Linking...
>>1>   Creating library 
>>D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.lib and object 
>>D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.exp
>>1>exception_handler.lib(exception_handler.obj) : error LNK2019: unresolved 
>>external symbol "__declspec(dllimport) void __cdecl std::_Throw(class 
>>stdext::exception const &)" (__imp_?_th...@std@@yaxabvexcept...@stdext@@@Z) 
>>referenced in function "public: void __thiscall 
>>stdext::exception::_Raise(void)const " (?_ra...@exception@stdext@@QBEXXZ)

>>
>>
>>1>exception_handler.lib(exception_handler.obj) : error LNK2001: unresolved 
>>external symbol "__declspec(dllimport) void (__cdecl* 
>>std::_Raise_handler)(class stdext::exception const &)" 
>>(__imp_?_raise_hand...@std@@3p6axabvexcept...@stdext@@@ZA)

>>
>>
>>1>D:\SL\linden\indra\build-vc80\sharedlibs\Release\llcommon.dll : fatal error 
>>LNK1120: 2 unresolved externals
>>1>Build log was saved at 
>>"file://d:\SL\linden\indra\build-vc80\llcommon\llcommon.dir\Release\BuildLog.htm"

>>
>>
>>1>llcommon - 3 error(s), 0 warning(s)
>>== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==
>>
>>
>>I have copied the libraries from libraries/i686-win32/lib/debug/ to 
>>libraries/i686-win32/lib/release/ but it didn't help. Does anyone know what 
>>to do please ? It seems to come from the new google_breakpad library but I 
>>don't know anything about it. I just know it was not there before.
>>
>>Thanks for any piece of help,
>>Marine
>>
>>___
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
>>
>
>___
>>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
>



  ___
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] Explorations in develop.py

2010-06-25 Thread Philippe (Merov) Bossut
Hi Ricky,

On Tue, Jun 22, 2010 at 8:36 PM, Ricky  wrote:

> Looking through develop.py, I spied the following lines:
>
> 281-elif self.arch() == 'x86_64' and self.is_internal_tree():
> 282-# the viewer does not build in 64bit -- kdu5 issues
> 283-# we can either use openjpeg, or overhaul our viewer
> to handle kdu5 or higher
> 284:# doug knows about kdu issues
> 285-return ['server-' + platform_build]
>
> Using svn blame, I found that these lines arrived into
> /linden/projects/2010/snowglobe/trunk/indra/develop.py at the time of
> the creation of this project at r3145.  I didn't checkout and search
> up the parent branches (wish svn had a way to do this easily!)
> Because of this, I am unable to tell whether this is still valid or
> otherwise.  Any enlightenment? Maybe a JIRA so I can see what the
> current status is?  My initial searches have turned up nothing,
> however, I may not be using the correct keywords...
>

This is still valid script and, as one can see in the code, only triggered
for internal (that is, internal to Linden Lab) repositories. What that means
is that we (LL) always build with KDU internally and we haven't made the
effort to support the newest KDU lib that would handle 64bits architecture.

In Snowglobe (and other external tree), folks can (and do) build 64bits
viewers and use openjpeg for texture compression/decompression.


> My memory is bugging me with the thought that a switchover to OpenJPEG
> has already happened... If so, then section of code should likely be
> updated.  Of course, it seems from the conditional that is is only
> about 64 bit builds of the Linden internal branch.  However, the
> reasoning given here may not be valid any more, and could possibly be
> replaced with a reference to a JIRA issue, maybe even the Linux 64bit
> build meta http://jira.secondlife.com/browse/VWR-13793 .
>

I don't understand what you mean by "switchover to openjpeg". Support for
openjpeg is in the viewer since a long time, I think since the early days
of  open sourcing the viewer, pre Snowglobe for sure. Both KDU and openjpeg
are supported though. The choice is made at runtime by loading libraries:
the viewer tries to load llkdu first and, if it fails, uses the openjpeg
default implementation. See LLImageJ2C::openDSO() for llkdu loading and
switch to default (openjpeg). openjpeg is statically linked and implemented
in llimagej2coj.cpp.

Cheers,
- Merov
___
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] Problem compiling llcommon on viewer 2.1 beta

2010-06-25 Thread Lance Corrimal
I think someone of you guys who successfully build 2.1 should put 
detailed steps on the wiki...



Am Samstag 26 Juni 2010 schrieb Nicky Perian:
> I built viewer-external on 6/19. Used Vista 32 and VC++Express
> 2005. Took 5 builds. Logs and steps taken are here. This was all
> the way to a setup.exe.
> 
> 
> 
> 
> 
> 
> From: Marine Kelley 
> To: Philippe (Merov) Bossut 
> Cc: opensource-dev@lists.secondlife.com
> Sent: Fri, June 25, 2010 4:30:53 PM
> Subject: Re: [opensource-dev] Problem compiling llcommon on viewer
> 2.1 beta
> 
> Hi Merov, thank you for looking into this !
> 
> I'm on Windows 7, trying to compile viewer-external as I always do
> :
> 
> - I unzip the artwork from version 2.0.0 (knowing that I will have
> to complete it with some of the icons from the official 2.1, like
> the icons for the system folders) - I unzip a very old library zip
> file of mine (it is more than 2 years old and contains ares, fmod
> and all, but is still operational at least until 2.0.1) - I run VC
> 2005, select the "Release" configuration, go to Configuration
> Manager, uncheck all the "tests" and "integration" projects (plus
> "package") - I open the Properties window on secondlife-bin and
> remove the /Zm1000 option from the command line - I build the
> whole thing
> 
> But even just building llcommon will give me the error I mentioned,
> no need to build the whole solution. This is the first time I get
> this error, and since I noticed that google_breakpad was not part
> of the viewer before, and surprisingly it uses an
> exception_handler.lib that does not provide the correct
> functions...
> 
> That's all I can think of but I'm sure there is more.
> 
> Thanks again,
> Marine
> 
> 
> 
> 
> On 25 June 2010 22:39, Philippe (Merov) Bossut
>  wrote:
> 
> Hi Marine,
> 
> >I just built the tip of viewer-external on my Windows XP machine
> >with no problem. Could you tell us a bit more on how you get
> >things together? Do you use develop.py? Do you do a standalone
> >build? Which Solution Configuration are you building?
> >
> >Cheers,
> >- Merov
> >
> >On Thu, Jun 24, 2010 at 1:30 PM, Marine Kelley 
 wrote:
> >>Hello,
> >>
> >>I am having the following link error when trying to compile the
> >>llcommon project on Viewer 2.1 beta extracted from
> >>viewer-external :
> >>
> >>1>-- Build started: Project: llcommon, Configuration: Release
> >>Win32 --
> >>
> >>
> >>
> >>1>Linking...
> >>1>   Creating library
> >>D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.lib and
> >>object
> >>D:\SL\linden\indra\build-vc80\llcommon\Release\llcommon.exp
> >>1>exception_handler.lib(exception_handler.obj) : error LNK2019:
> >>unresolved external symbol "__declspec(dllimport) void __cdecl
> >>std::_Throw(class stdext::exception const &)"
> >>(__imp_?_th...@std@@yaxabvexcept...@stdext@@@Z) referenced in
> >>function "public: void __thiscall
> >>stdext::exception::_Raise(void)const "
> >>(?_ra...@exception@stdext@@QBEXXZ)
> >>
> >>
> >>
> >>1>exception_handler.lib(exception_handler.obj) : error LNK2001:
> >>unresolved external symbol "__declspec(dllimport) void (__cdecl*
> >>std::_Raise_handler)(class stdext::exception const &)"
> >>(__imp_?_raise_hand...@std@@3p6axabvexcept...@stdext@@@ZA)
> >>
> >>
> >>
> >>1>D:\SL\linden\indra\build-vc80\sharedlibs\Release\llcommon.dll :
> >>fatal error LNK1120: 2 unresolved externals 1>Build log was
> >>saved at
> >>"file://d:\SL\linden\indra\build-vc80\llcommon\llcommon.dir\Rele
> >>ase\BuildLog.htm"
> >>
> >>
> >>
> >>1>llcommon - 3 error(s), 0 warning(s)
> >>== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
> >>==
> >>
> >>
> >>I have copied the libraries from libraries/i686-win32/lib/debug/
> >>to libraries/i686-win32/lib/release/ but it didn't help. Does
> >>anyone know what to do please ? It seems to come from the new
> >>google_breakpad library but I don't know anything about it. I
> >>just know it was not there before.
> >>
> >>Thanks for any piece of help,
> >>Marine
> >>
> >>___
> >>
> 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
> >
> >___
> >
> >>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

___
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