nyuuzyou/wikis huggingface dataset:
Open Grid Public Beta/Getting Rez Avatar Request Cap

The OGP protocol mentions getting the rez_avatar/request capability in Teleport § 1.3.2: This capability is normally attained from the Public Region Seed Capability, but does not go into detail.
To obtain the rez_avatar/request capability, you make a request to the public_region_seed_cap. In LLIDL, this would be:
 %% public_region_seed_cap -> undef <- &resp 
 
 ;;success 
 &resp = {
 capabilities: [ rez_avatar/request: uri ]
 }
 ;; error
 &resp = {
 message: string
 }
 
==In Practice==
You make a GET request to the public_region_seed_cap:
Note that you must send the Accept: application/llsd+xml header with the request. See OGP Serialization and Transport.
 curl -k -H "Accept: application/llsd+xml" http://75.101.131.107:9000
 * About to connect() to 75.101.131.107 port 9000 (#0)
 * Trying 75.101.131.107... connected
 * Connected to 75.101.131.107 (75.101.131.107) port 9000 (#0)
 > GET / HTTP/1.1
 > User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
 > Host: 75.101.131.107:9000
 > Accept: application/llsd+xml
 > 
 < HTTP/1.1 200 OK
 < Content-Type: application/llsd+xml; charset=utf-8
 < Server: Mono-HTTPAPI/1.0
 < Date: Wed, 24 Sep 2008 23:13:24 GMT
 < Content-Length: 230
 < Connection: close
 < 
 * Closing connection #0
 <llsd>
 <map>
 <key>connect</key>
 <boolean>1</boolean>
 <key>capabilities</key>
 <map>
 <key>rez_avatar/request</key>
 <string>http://75.101.131.107:9000/agent/de537165-804a-44f3-a6dc-bb27642be9af/rez_avatar/request</string>
 </map>
 </map>
 </llsd>
==Previous Implementation==
Previously, this was done by posting a request for the rez_avatar/request capability.
Category: Grid_Interoperability
Category: Open Grid Public Beta
Open Grid Public Beta/HTTPS Support

Over the weekend(and a portion of last week) I implemented SSL support in the region http server in OpenSimulator in response to some of the things we've been discussing. Most notably, the CAPS for OGP are meant to be sent/invoked over SSL.
I've also included a junk CA, a PEM file that corresponds with that junk CA, and directions in the /share/junkCA SVN folder.
Enabling SSL still isn't 'easy', but it's far easier then it was previously.
One thing to note, however is, since we don't know which certificate authorities the client trusts and therefore can't get a certificate signing request signed by one, you must append the CA2.pem file to the client's list of approved certification authorities to be able to test a region with SSL using the junk CA certificate authority. That file is located in the /app_settings/ folder and is called CA.pem.
Please *APPEND* the CA2.pem file to /app_settings/CA.pem (add it to the end) to test https OGP regions. If you do not, then the client will quietly refuse to connect to your SSL regions. Seed caps requests will fail and you'll see the following message on the debug console: routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
Do not erase what is already in there! It contains a list of Linden approved Certification authorities!(We don't know what ones are there.. but if you remove them you won't be able to connect with the Linden grid).
This is only a temporary measure to test SSL. Infinity is working on a complete solution. 
This will allow the client to verify the certificate. However, be aware that this is a junk CA, this CA should not be trusted for anything but testing. The private key for it is freely available so it can be spoofed easily. After the complete solution above is done, please be sure to remove the CA2.pem cert from your /app_settings/CA.pem since it isn't trusted. (it'll be the last -----BEGIN CERTIFICATE----- to -----END CERTIFICATE----- section)
Remember to read the [Network] section of the opensim.ini.example for information on how to set up the following values:
 http_listener_ssl = false ; Also create a SSL server
 http_listener_cn = "localhost" ; Use the cert with the common name
 http_listener_sslport = 9001 ; Use this port for SSL connections
 http_listener_ssl_cert = "" ; Currently unused, but will be used for OSHttpServer
As well as the directions in svn/share/junkCA/Certificate commands OpenSSL.txt. The directions in that file direct you on how to use OpenSSL to generate a certificate signing request, sign it with the junkCA, and install it for OpenSImulator to use.
Happy testing. You may direct specific setup questions to myself or the OpenSim-dev e-mail list: https://lists.berlios.de/mailman/listinfo/opensim-dev or the #opensim IRC channel on irc.freenode.net.
Best Regards
Teravus Ousley
Category:Open_Grid_Public_Beta
Open Grid Public Beta/Issue Tracking

== How To File Issues Against the Open Grid Public Beta ==
Note: This Document Presumes familiarity with the Public JIRA (PJIRA).
=== Check To See If The Issue Has Already Been Filed ===
There is an umbrella issue, SVC-2632, for all Open Grid Public Beta Issues. Please check in there to see if the issue has already been filed. Please, do not create duplicate issues.
* After creating the report, please create a link back to SVC-2632 by selecting the "Link this issue to another issue" operation along the left side of the window. Select "Related to" in the This issue: dropdown list. Then enter SVC-2632 in the Issues: entry. This will help make sure all OGP issues are seen under the SVC-2632 umbrella.
=== To File Issues Against the Viewer ===
# Open a new Issue under the VWR project.
# Select the Interop Component.
# Enter information on the issue.
# Use the words "OGP beta" in the summary.
If you are creating this issue to track a bug in a third party project:
* Under advanced, enter the URL of the issue in the other project's bug tracking system. Do not enter a Linden Lab internal JIRA.
=== To File Issues Against the Agent Domain ===
# Open a new Issue under the SVC project.
# Select the Interop - Agent Domain component
# Enter information on the issue.
# Use the words "OGP beta" in the summary.
If you are creating this issue to track a bug in a third party project:
* Under advanced, enter the URL of the issue in the other project's bug tracking system. Do not enter a Linden Lab internal JIRA.
=== To File Issues Against the Region Domain ===
# Open a new Issue under the SVC project.
# Select the Interop - Region Domain component
# Enter information on the issue.
# Use the words "OGP beta" in the summary.
If you are creating this issue to track a bug in a third party project:
* Under advanced, enter the URL of the issue in the other project's bug tracking system. Do not enter a Linden Lab internal JIRA.
=== To File Issues Against OpenSim ===
# You will need an account on the OpenSim Mantis site.
# File your issue with supporting log information in the [REGION] Specific OpenSim Module category.
# File a corresponding issue against the Region Domain in PJIRA (see above.)
category:Open Grid Public Beta
Open Grid Public Beta/Teleport How To

== Download and Install Open Grid Viewer ==
# Download the viewer from here.
# The viewer is named "Open Grid" so you can install it without conflict with your existing Second Life viewer.
# Launch the viewer.
== Log In ==
# If you have the grid dropdown selector visible (obtained with ++), then you must set the grid name to "Aditi" (not Agni nor Vaak), because the OGP grid's Agent Domain is running on Aditi.
# Note the new field, "Region URL" in the lower right hand pane of the splash/login screen.
# In this new field, enter "https://sim1.vaak.lindenlab.com:12043/cap/8656050e-a1b4-81ad-70d3-ba94971599c3", without quotes and without a trailing slash (see VWR-8382 ).
# Enter your user name and password, and press connect. (Your avatar must belong to the Gridnauts inworld group)
* When you login, you will be 'ruthed'.
* The system may also ask if you want your avatar to be male or female.
* Note that you will not have access to your inventory.
== Teleporting to an Open Sim Region ==
* From the "World" menu, select "Teleport Region".
** The teleport floater will only display if you originally logged in with a Region URL.
# Enter the URL of your patched OpenSim region.
# Press teleport.
* You will rez, once again, 'ruthed' on your OpenSim region.
* You can check "Help" > "About" from the menu to confirm that you are on your OpenSim region.
Congratulations! Gridnaut. You've Teleported Across The Grid!
A list of public regions to connect to is here: Public Regions
Send a screenshot of your avatar (with nametag) and the about screen to the gridnauts list for your special Gridnaut bear.
== Troubleshooting ==
* If you see the not in gridnauts message when logging into the Open Grid viewer, please check your account on the beta grid with a release viewer to confirm you are in the gridnauts group.
* If you show up as a 'puffball' ruth on an externally hosted sim, right click on yourself and select 'Edit Appearance,' but don't save. (See SVC-2763.)
* If you get an invalid region error when you attempt to teleport, check your OpenSim's bin/Regions/default.xml
** The attributes sim_location_x, and sim_location_y should not conflict with coordinates on the Second Life grid.
** Check the page Map_Locations and claim a non-conflicting set of coordinates.
** You might check and see if putting your region name in the "Start Location" helps
Category:Open_Grid_Public_Beta
Open Group Join

==User Touches Object to Join Group==
No bot needed for this script. 
User Touches object for a link in Local Chat that when clicked from History will open the Group Information Window. If Group is set to Open Enrollment the user may JOIN.
The object this script is in must be set to the group you want people to join.
findgroupkey()
{
 list TempList = llGetObjectDetails(llGetKey(), [OBJECT_GROUP]);
 key groupkey = llList2Key(TempList, 0);
 if (groupkey == NULL_KEY)
 {
 llWhisper(0, "Set the Group for this object in EDIT under the GENERAL tab and be sure your Group is Open Enrollment.");
 }
 else
 {
 llWhisper(0, "Click the link from Chat History (Ctrl+H) and then click on JOIN button! secondlife:///app/group/" + (string) groupkey + "/about");
 }
}
default
{
 state_entry()
 {
 llSetText("Touch to Join\nour Group", <1, 1, 1>, 1.0); // white and opaque floating text, optional
 findgroupkey();
 }
 touch_start(integer total_number)
 {
 findgroupkey();
 }
}
If the object Group must be different because of land settings use this object somewhere where you are allowed and Copy the message said from Chat History. Then create a simple script that whispers this message when Touched.
More scripts: http://www.aliciastella.com
Open Object

=== Feature Design Document ===
(none)
=== Functional Spec ===
(none)
=== Test scripts ===
Open Object Test
Single Click Test
=== Discussion for future improvements ===
(none)
=== Relationship to other features ===
 List of features that need to be tested when this feature changes, and why. 
Object Contents - Permissions for items in the "Open" window are displayed slightly different(?) than in the "Object Contents" window.
Buy Contents - Permissions for items in the "Open" window are displayed slightly different(?) than in the "Buy Contents" window.
=== User Guides ===
(none)
Open Object Test

Category:Test Scripts
[OpenObjectTest]
[VERSION] 0.1
[LENGTH] 00:15
[TESTERS] 2
[OVERVIEW] This test has been designed to exercise the "Open" pie menu option
[SETUP] This test requires 2 Testers
[*]
[NOTE] The menu option for Open only shows for objects owned by the avatar or which are 
modifiable by the avatar. The contents panel is still subject to the same bugs (whatever 
those may be) found in the Content's tab of the edit window. This is really just a light 
wrapper to move often used functionality out of the complex edit tool into a simple and 
easy to use window.
[*]
[0010] Tester 1: Right-click on the ground and select "Create" from the pie menu and rez a default cube
[0020] Tester 1: In edit, click "more >>" if necessary, click the contents tab
[0030] Tester 1: Add some clothing, objects, notecards, scripts, textures and landmarks of 
varying permissivness to the contents
[0040] Tester 1: Close the edit Window.
[0050] Tester 1: Right-click on the cube and Select "Open" from the pie menu
[0060] Tester 1: Verify the 'Open Object' window appears and has the correct contents.
[0070] Tester 2: Right-click on the cube and Select "Open" from the pie menu
[0080] Tester 2: Verify the 'Open' option is not available.
[0090] Tester 1: Drag a copyable item from the "Open" floater into your Inventory
[0100] Tester 1: Verify the item is copied into your inventory, is still in the open 
floater and is still shown in the contents panel of the edit window.
[0110] Tester 1: Drag a no-copy item from the "Open" floater into your Inventory
[0120] Tester 1: Verify the item is copied into your inventory, is no longer in the open 
floater and is no longer in the contents panel of the edit window
[0130] Tester 1: Close the "Open" window and Re-open it from the pie menu.
[0140] Tester 1: Verify the view is still correct
[0150] Tester 1: Delete some items from the Open floater
[0160] Tester 1: Verify they do delete from the Open floater and the contents panel of the 
edit window
[0170] Tester 1: Delete your prim
[END]
Category:QA Portal
Category:Quality Assurance
Open Prim Animator/Touch Ping Pong

//! @brief This is a utility script for OPA for cases when animation frames are meant to be viewed sequentially in both forward and "reverse".
/**
* @author SignpostMarv Martin
*/
//! The number of animation frames
integer count;
//! if TRUE then the "ping pong" is in effect and should not be interupted.
integer running=FALSE;
//! interval between animation frames
float interval = 1.0;
//! 
integer at=1;
integer mod=1;
default{
 state_entry() {
 llMessageLinked(LINK_ROOT, -1, "XDrecordedSnapshots", NULL_KEY); // get the number of animation frames from the core OPA script.
 }
 link_message(integer s, integer n, string m, key i){
 if(m == "XDrecordedSnapshots" && n >= 0){
 count = n; // update the number of animation frames
 }
 }
 touch_start(integer t){
 if(!running){ // if we're not doing the "ping-pong",
 running = TRUE; // set the flag to TRUE
 llSetTimerEvent(interval); // then set the timer event away.
 }
 }
 timer(){
 if(count <= 0){
 llSetTimerEvent(0); // stop the timer
 }else{
 at += mod; // add the modifier (which may be a negative integer)
 if(at >= count){ // if we're at the end of the "ping-pong", 
 mod = -1; // change the mod to negative 1 in preparation of reversing the animation
 llSetTimerEvent(0); // turn off the timer
 running = FALSE; // set the running flag to FALSE so a user can touch the script.
 }else if(at <= 1){ // if we're at the end of the "pong-ping",
 mod = 1; // change them od to positive one in preparation of running the animation
 llSetTimerEvent(0); // turn off the timer.
 running = FALSE; // set the running flag to FALSE so a user can touch the script.
 }
 llMessageLinked(LINK_ROOT, at, "XDshow", NULL_KEY); // instruct the core OPA script to change the displayed animation frame.
 }
 }
}
Ping Pong
Open Sim Public Beta/Map Locations

OpenSim regions cannot be placed directly adjacent to existing regions on aditi or vaak.
:Zha Ewry: "Setup as a very basic stand alone opensim. set the default location and the location of your region to be the same value, and run only one region on the server. (ie. in OpenSim.ini, make sure you set default_loc_x and default_loc_y, and make them match the ones in the default.xml in the Regions subdirectory of you r bin directory in your install. Make sure your X and Ys are multiples of 256."
Non-Linden Lab OpenSims should use default_loc_x and default_loc_y values greater than 4096.
Claim Map Locations Below
== Whump Linden ==
* 2048/2048
* 2304/2560
Open Source Meeting/2007-11-22

< Open Source Meeting
Open source meeting - Thursday, 2pm PT.
Teleport to the Linden Open Source Project headquarters.
== Agenda ==
* Open Discussion
== Minutes ==
[No transcript avail.]
Main Topics Discussed:
* Linux Builds with 1.18.5 (and 1.18.6) viewers: Various compiler errors have shown up. Some have already been mentioned on SLDev.
* OpenJPEG2000: Further speed improvements
* X11: SDL with hardware access requirements does not let X11 scale as it does without SDL, and it makes it hard to run SL across an X11 network or on multiple X11 screens
Open Source Portal

__NOTOC__
Documentation
A lot of the documentation below is geared toward developers. However, many aspects of the system don't require a deep technical background to learn. 
* Viewer Integration and Release Processes
* Viewer Source Code
** Viewer Doxygen - browse source and documentation
** Coding Standard
* Viewer Licensing
* Viewer architecture - Overview of the Viewer from a developer's perspective. 
* XUI Reference
* Third Party Libraries
* Features - An overview of the major components of the system as seen from an end user's perspective, including links to specifications, test plans and other documentation. 
* Protocol - in depth documentation of the protocol
* Server Architecture
* Glossary 
more...
Puppetry
* How Puppetry Works
* Puppetry Development
* Puppetry Network Control
* Puppetry Mocap	
Ways to Participate
* Communication tools (mailing list/IRC/etc)
* Get source and compile
* Read about the simpler CLA process
* Testing efforts
** Downloading test builds
** File and vet bugs
* Work on one of these outstanding open development suggestions
* Propose and refine feature contributions
* Submit code
* Inspect crash reports
* Implement new features
* Profile and Optimize
* Find memory leaks
Help make the Second Life Viewer better! You don't need to know C++ or even programming to help. Some of the toughest jobs in software development have nothing to do with writing code. Just grab a test build and try playing around with it. Let us know what you think on email, on the forum, or IRC. If it's not working for you, try to get help there. If it is working, try helping someone else. If you run into issues, see if a bug report has been filed; if not, file one. 
Of course, if you are a developer, we can use your help. Download the code - try your hand at fixing a bug, or extending the software through one of the APIs. There's a ton of ways you can help, and we welcome you regardless of your skill level.
Category:Portals
Open Source Portal/ja

__NOTOC__
資料
以下のドキュメントの多くが開発者向けとなっています。しかし、システムには、深い技術的知識がなくても理解できる面が多くあります。 
* Viewer Integration and Release Processes
* Viewer Source Code
** Viewer Doxygen - ソースとドキュメントの閲覧 
** Coding Standard
* Viewer Licensing
* Viewer architecture - 開発者視点で見たビューアの概要 
* XUI Reference
* Third Party Libraries
* Features - エンドユーザから見た、システムの主要なコンポーネントの概要。各仕様書へのリンクや、テスト計画、その他の文書があります。 
* Protocol - プロトコルの詳細な解説資料
* Server Architecture
* Glossary 
もっと見る...	
参加する方法
* コミュニケーションツール (メーリングリスト/IRC/その他)
* ソースコードを取得してコンパイルする
* Second Life Viewer Contributor Agreement を完成させる
* テストでがんばる 
** テストビルドをダウンロードする
** バグを報告したりバグに投票したりする
* 未着手の開発提案 のうちの1つを選んで実装してみる 
* 機能リクエストを出したり推敲したりする
* コードを投稿する
* クラッシュレポートを調査する
* 新しい機能を実装する
* プロファイリングや最適化を行う
* メモリリークを発見する
Second Life ビューワをよりよくするためにご協力をお願いします！C++ や、プログラミングさえ知らなくても手伝えます。ソフトウェア開発の中で最も過酷な仕事の中には、コードを書くことと全く関係のないものもあります。とにかく テストビルド を入手してそれで遊び回ってみてください。電子メールや、フォーラム、IRC で思ったことをお知らせください。うまくいかなかったら、そこで助けを呼んでください。うまくいっていたら、他の人を助けてください。問題にぶち当たったら、バグ報告が既に出されていないか確認して、なければ出してください。出されていたら、それに投票したり、できればさらに詳細を書いてください。
もちろん、あなた が 開発者であれば、私たちの助けになることができます。コードをダウンロードして、それでビルドできるか確認してください。バグを直してみたり、API でソフトウェアを拡張したりしてみてください。手伝う方法はごまんとあり、私たちはスキルレベルに歓迎なくあなたを歓迎します。
Category:Portals/ja
Open Source Portal/ko

__NOTOC__
배움
아래의 문서들은 많은 개발자들을 향해 준비되어있습니다. 하지만, 시스템의 여러 측면을 배우기 때문에 깊은 기술적 배경을 요구하지는 않습니다.
이 중 대부분의 문서들은 여전히 진행중이며, 이후 이 위키가 만들어져있다면, 비워져 있는 곳을 메꾸어 주실 때에 큰 도움이 있습니다!
* 기능 - 최종 사용자의 시점에서 보는 시스템의 주요 구성요소에 대한 개요. 링크 규격, 테스트 계획 및 기타 설명을 여기서 찾을 수 있습니다.
* 뷰어 아키텍쳐 - 이것은 개발자의 관점에서 보는 아키텍쳐에 관한 개요입니다.
* 프로토콜 - 프로토콜에 관한 문서
* Extended FAQ - 에 대하여 질문들이 들어있습니다.
더 알고자 한다면...	
Ways to Participate
* 테스트 빌드 다운받기
* 통신 도구들(메일링 리스트/IRC/그외)
* 소스 다운 방법과 컴파일
* 101가지 버그 리포팅
* 기능 요청
* 완성된 코드
* 검사 오류 리포트
* 새로운 기능 구현
* 프로필 및 최적화
* 메모리 누수 찾기
* 현재까지의 기여도 보기
* 아키텍쳐 그룹에 가입
우리는 당신의 도움으로 세컨드라이프를 보다 더 좋게 만들고 싶습니다. 당신은 C++이나 혹은 이하 프로그래밍에 대한 지식을 필요로 하지 않습니다.
일부 소프트웨어 개발에서 가장 어려운 부분과는 상관이 없습니다. 그냥 테스트 빌드와 여러가지 게임을 즐기시다가 버그를 잡아주시기만 하면 됩니다.우리에게 당신이 어떤 생각을 하고 있는지를 이메일, 포럼 혹은 IRC로 알려주시기 바랍니다. 만일 그것이 동작되지 않을 경우 그들이 도움을 줄 것입니다. 만일 당신을 위해 노력하는 사람만큼 당신은 행운을 바라지 않아도 사람들이 도와주려 할 것입니다. 만일 당신이 특정 문제로 실행을 하면 버그 리포트를 제출 할 수 있도록 하고 있으며, 파일일 수도 있으며, 투표일수도 있고 때로는 좀 더 자세하게 작성을 해주셔야 할 것입니다.
물론, 당신이 개발자라면 우리는 당신의 도움이 필요합니다. 소스 코드를 다운받고, 당신이 그것을 빌드할 수 있는지를 봐주시기 바랍니다.
당신의 손에 버그들이 고쳐질 것입니다. 혹은 API들에 대하여 소프트웨어를 만들어 주시기 바랍니다. 거기에 당신의 방법론, 우리의 기술 수준에 상관없이 당신을 환영할 것입니다.
더 알고자 한다면...
Category:Portals/ko
Open Zyngo Skin Installer

I am uploading this script here for everyone to use its a simple skin script to set skins on the popular zyngo machines all you have to do is change the keys and other varriables and drop it into your machine it does the rest.
//////////////////////////////////////////////////////////////////////////////
// Good Skin Instaler Script //
// //
// I got the basics of this script from Cold Spitteler over at Jaded //
// so its not entirely mine but i am giving credit where it is due //
// //
// Copyright (C) 2009 Tmzasz Luminos with help from Cold Spitteler //
// This program is free software: you can redistribute it and/or modify //
// it under the terms of the GNU General Public License version 3, as //
// published by the Free Software Foundation. //
// //
// This program is distributed in the hope that it will be useful, //
// but WITHOUT ANY WARRANTY; without even the implied warranty of //
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the //
// GNU General Public License for more details. //
// //
// You should have received a copy of the GNU General Public License //
// along with this program. If not, see <http://www.gnu.org/licenses/> //
//////////////////////////////////////////////////////////////////////////////
key texture = "00000000-0000-0000-0000-000000000000"; // replace 0 with your skins UUID
vector topColor = <1.0,1.0,1.0>; //Top of the machines color
vector potcolor = <1,1,1>; //Color of the Pot numbers
vector score2beatcolor = <1,1,1>; //Color of the Score2Beat numbers
vector scorecolor = <1,1,1>; //Color of the Score and Round numbers
vector pricecolor = <1,1,1>; //Color of the Price and %to Pot numbers
LoadTexture(key texture, vector topColor) // set the skin itself
{
 llSetTexture(texture,1);
 llSetTexture(texture,2);
 llSetTexture(texture,3);
 llSetTexture(texture,4);
 llSetColor(topColor,0); 
}
default
{
 state_entry()
 {
 LoadTexture(texture,topColor); // Calls the function to set skin
 
 llSetLinkColor(11, potcolor, ALL_SIDES); // sets pot color
 llSetLinkColor(10, score2beatcolor, ALL_SIDES); // sets score2beat color
 llSetLinkColor(9, scorecolor, ALL_SIDES); // sets score color
 llSetLinkColor(7, pricecolor, ALL_SIDES); // sets price color
 llSleep(2.5);
 llOwnerSay("Skin Installed removing this Script"); // tells you when its all done
 llRemoveInventory(llGetScriptName()); // gets the script name of this script! and removes THIS SCRIPT
 
 }
}
Opensecondlife.org

opensecondlife.org hosts a bleeding edge version of the open source Second Life client that contains many fixes that have not been accepted or released by Linden Lab. All of the submitted patches are released in to the public domain, and the main release attempts to stay as close as possible to the official release while also creating a simplified build environment for as many platforms as possible. It will currently compile straight from svn with no modifications in Visual Studio 2005, and the dependency requirements are greatly reduced from the official build instructions.