On Mon, Oct 5, 2009 at 9:12 AM, Toni Alatalo <ant...@kyperjokki.fi> wrote:
>
> On Sun, Oct 4, 2009 at 10:04 PM, Jonne Nauha <jonne.na...@evocativi.com>
> wrote:
>>> For Ryans ps: Well I'd much rather see <deps_svn>/external_libs and
>>> <deps_svn>/runtime_libs. Windows, linux and mac under them both. Now we have
>>>
>
> The downside of that is that someone wanting e.g. just the Mac
> dependencies couldn't check out a mac dir, but would have to either
> check out whole deps_svn and get the libs for all platforms in vain, or
> do two separate checkouts to get the two mac dirs.
Good point.
Not sure what problems are caused on windows by the current situation,
but there is no point in causing other users problems.
Here is what I'd like to see, but I'm not volunteering for it, as it
mostly doesn't affect me:
bin/{win32|win64|mac}/<whatever makes sense on your platform> (ex:
bin/win32/{build|dist})
Cheers,
> Neither may be a problem really, but just wanted to point out that this
> is perhaps not an optimal solution. I do agree that the most important
> thing is that it's easy to setup, the simplest copying possible.
> Probably checking out the whole deps and having to download all is ok,
> and if someone is on a slow connection / with tight disk space, they can
> do the two checkouts in that exceptional case.
>
> This may become more annoying if we end up with like >10 platform dirs
> in there (iphone, solaris, android, ps3, xbox, symbian, plan9 and hal)
> but I guess win, lin and mac cover it for long now (at least if the
> different variants of those can be handled with a single case, and there
> wont be winxp, vista, win7, minwin, 32bit, 64bit, leopards with and
> without snow etc).
>
> The blender deps lib/ dir in svn seems to have these dirs .. seems
> ppc/intel was one distinction i didn't consider, and that with linux you
> may wanna have different glibc versions supported etc?
>
> https://projects.blender.org/plugins/scmsvn/viewcvs.php/trunk/lib/?root=bf-blender
> darwin-6.1-powerpc/ 22397 7 weeks ton 2.5 Homebrewn own
> python 3.1 .a compiled on PPC 10.3
> darwin-8.0.0-powerpc/ 11714 2 years lukep libopen al
> for os x
> darwin-8.x.i386/ 22784 5 weeks nexyon For some reason
> svn skipped the libsndfile.a in last commit.
> irix-6.5-mips/ 19942 5 months campbellbarton remove
> ~45mb of unneeded pyo and pyc files
> linux-glibc2.2.5-i386/ 2768 5 years larstiq - Update
> FTGL to version 2.0.9
> linux-glibc2.3.1-i386/ 317 6 years larstiq Enough is
> quite enough, ode lib and header for linux powerpc and i386
> linux-glibc2.3.1-powerpc/ 317 6 years larstiq Enough
> is quite enough, ode lib and header for linux powerpc and i386
> solaris-2.10-x86_64/ 14817 16 months campbellbarton
> Adding freetype to solaris x86_64
> solaris-2.8-sparc/ 13107 21 months campbellbarton
> removing pyc and pyo files
> tests/ 9855 2 years letterrip = game engine logic test
> suite = this is a gameengine test suite for game engin...
> win64/ 22868 5 weeks campbellbarton Fix for 2.49b
> release. Windows python26 would fail importing
> windows/ 23464 10 days jesterking * scons/mingw: ensure
> all necessary symbols are visible for debug build
>
> So there it's clearly nice you can just get the dir of your platform.
>
> ~Toni
>
>>> totally (in my opinion, other you do copying from, other you just refer to
>>> with a path variable) two different things inside each other. And as we see
>>> here this is confusing people where to copy what, what dist means and why
>>> there is 1-2 "bin" folders inside a "bin" folder etc. :)
>>>
>>> Would be easier to write wikis/readmes for this setup if we had the two
>>> functionally different things separeted. The other thing you just put there
>>> and setup the NAALI_DEP_PATH to it, the other you would just copy the whole
>>> content into your naali/bin. But hey thats just my opinion and its only
>>> based on how my brain works and not that much on the techicalities of the
>>> subject :)
>>>
>>> - Jonne
>>>
>>> On Sun, Oct 4, 2009 at 8:55 PM, Ryan McDougall <sempu...@gmail.com> wrote:
>>>
>>>> On Sun, Oct 4, 2009 at 8:38 PM, Paul Fishwick <fishw...@cise.ufl.edu>
>>>> wrote:
>>>>
>>>>> 1. In C:\viewerdeps\bin\windows\dist\bin, there are dlls in
>>>>> subdirectories
>>>>> as well as in this main directory. Are *all" DLLs to be copied
>>>>> (including
>>>>> those in the subdirectoriees (farsight2-0.0, gabble..) or only the DLLs
>>>>> directly in dist\bin ?
>>>>>
>>>> Copy the whole lot, as that includes all runtime dependencies which
>>>> we've precomputed, and you just slam in there.
>>>>
>>>>
>>>>> 2. In your instructions, the next step is to copy the DLLs to a new
>>>>> folder
>>>>> yet to be created: C:\viewerTrunk\viewer\bin, and then to continue to
>>>>> section
>>>>> #4 (Building the Viewer). Then there is a reference in section #4 to
>>>>> a file "viewerTrunk\viewer\CmakeLists.txt. Where is this file? I do not
>>>>> recall
>>>>> seeing instructions in:
>>>>>
>>>> That file is in SVN:
>>>>
>>>> http://dev.realxtend.org/gf/project/viewer/scmsvn/?action=browse&path=%2Ftrunk%2FCMakeLists.txt&view=markup
>>>>
>>>> But to just build the viewer, you don't even need to know that, just
>>>> run cmake_vs2008.bat
>>>>
>>>>
>>>>> http://wiki.realxtend.org/index.php/Building_Naali_in_Windows
>>>>>
>>>>> for downloading additional files into "viewertrunk". Have I missed a
>>>>> step?
>>>>>
>>>>> -p
>>>>>
>>>>>
>>>> If you're downloading SVN trunk, you need to use the instructions
>>>> here:
>>>> http://dev.realxtend.org/gf/project/viewer/scmsvn/?action=browse&path=%2Ftrunk%2Fdoc%2Fbuild-windows.txt&view=markup
>>>>
>>>> If you're downloading from SVN tag, you can use the wiki instructions.
>>>> I guess this wasn't made very clear: wiki tracks releases, svn tracks
>>>> svn HEAD.
>>>>
>>>> #1 solve the build dependencies, that's in viewerdeps/bin/windows/*
>>>> #2 build the viewer using cmake_vs3008.bat
>>>> #3 solve the runtime dependencies, that's in
>>>> viewerdeps/bin/windows/dist/bin -> trunk/viewer/bin
>>>> #4 run trunk/viewer/bin
>>>>
>>>> In linux it's all quite a bit easier, you do
>>>>
>>>> #1 sudo yum/apt-get <ALL DEPS>
>>>> #2 cmake . && make
>>>> #3 ./bin/viewer
>>>>
>>>> but the linux build so far has less testing.
>>>>
>>>> Cheers,
>>>>
>>>>
>>>>> Jonne Nauha wrote:
>>>>>
>>>>>> Small correction runtime dll:s that you copy to <naali_trunk>/bin are
>>>>>> in "/bin/windows/dist/bin". Small renaming of folders recently :) Its
>>>>>> still a little confusing, but thats how it is for now.
>>>>>>
>>>> ps. The fix would be to put the build dependencies into
>>>> "bin/windows/build/*. I take it you've signed up to do that? :P
>>>>
>>>>
>>>>>> - Jonne
>>>>>>
>>>>>> On Sun, Oct 4, 2009 at 6:58 PM, Toni Alatalo <ant...@kyperjokki.fi
>>>>>> <mailto:ant...@kyperjokki.fi>> wrote:
>>>>>>
>>>>>>
>>>>>> Paul Fishwick kirjoitti:
>>>>>> > Well, if possible, I'd like to use your precompiled dependency
>>>>>> package
>>>>>> > without having to build it. Does this precompiled package (w/
>>>>>> the DLLs that I need to copy)
>>>>>> > exist somewhere? It is not under:
>>>>>> >
>>>>>>
>>>>>> We just moved that precompiled zip to be a binary dir in the
>>>>>> dependencies svn, lib/windows/lib has deps for bulding and
>>>>>> lib/windows/bin the runtime dlls iirc.
>>>>>>
>>>>>> > http://dev.realxtend.org/gf/project/viewerdeps/frs/
>>>>>> >
>>>>>>
>>>>>> So they've been updated in the svn of that project, also the
>>>>>> binaries
>>>>>> for windows, to match what current trunk head needs. On linux the
>>>>>> distributions have almost all of the deps, and most of the deps
>>>>>> sources
>>>>>> are in that svn in trunk/
>>>>>>
>>>>>> > -p
>>>>>> >
>>>>>>
>>>>>> ~Toni
>>>>>>
>>>>>> > Ryan McDougall wrote:
>>>>>> >
>>>>>> >> There is a bit of a mis-match in documentation there. The wiki
>>>>>> >> documents the 0.0.1 release IIRC. There should be a version in
>>>>>> the
>>>>>> >> doc/ folder in SVN that documents HEAD.
>>>>>> >>
>>>>>> >> We've basically removed the viewer deps tarball/zip in favour
>>>>>> of the
>>>>>> >> viewerdeps SVN, which appears to be what you've got, so don't
>>>>>> worry
>>>>>> >> about it.
>>>>>> >>
>>>>>> >> If you're using VC++ express, often you'll need the MS Windows
>>>>>> >> platform SDK to compile most anything with express; however
>>>>>> since I
>>>>>> >> don't think we call any windows APIs directly (instead we go
>>>>>> through
>>>>>> >> Qt), you may not need that. Also, there are some licensing
>>>>>> >> restrictions what you can do with a binary compiled by express.
>>>>>> >>
>>>>>> >> I'm not sure one "configures" the modules per se, only that if
>>>>>> you
>>>>>> >> don't need a module, commenting it out from the build will make
>>>>>> sure
>>>>>> >> it's not linked. At this point I think you can just use the
>>>>>> cmake file
>>>>>> >> you get from a clean checkout.
>>>>>> >>
>>>>>> >> Please let us know if you have any other problems.
>>>>>> >>
>>>>>> >> Cheers,
>>>>>> >>
>>>>>> >> On Sun, Oct 4, 2009 at 6:12 PM, Paul Fishwick
>>>>>> <fishw...@cise.ufl.edu <mailto:fishw...@cise.ufl.edu>> wrote:
>>>>>> >>
>>>>>> >>
>>>>>> >>> Jonne
>>>>>> >>> I thought I'd try to build Naali from source to see where it
>>>>>> is in
>>>>>> >>> development. The
>>>>>> >>> plan would be to use Naali to access an existing Opensim
>>>>>> server. Using
>>>>>> >>> this guideline:
>>>>>> >>>
>>>>>> >>> http://wiki.realxtend.org/index.php/Building_Naali_in_Windows
>>>>>> >>>
>>>>>> >>> Installing CMake was not an issue, but I do not follow these
>>>>>> >>> instructions.
>>>>>> >>> From Gforge, I used the access info: svn co
>>>>>> >>> http://dev.realxtend.org/svn/viewerdeps
>>>>>> >>> to C:\viewerdeps. Where is "viewer-dependencies-VS2008" ?
>>>>>> Also, can
>>>>>> >>> Visual C++ Express edition be used (in the same spirit as one
>>>>>> can use
>>>>>> >>> Visual C# Express edition to compile opensim)? Thanks
>>>>>> >>>
>>>>>> >>> I also have some questions on "Building the Viewer" but have
>>>>>> yet to get
>>>>>> >>> to that
>>>>>> >>> stage, such as:
>>>>>> >>>
>>>>>> >>> What does "Open up .... and configure the set of modules by
>>>>>> commenting
>>>>>> >>> out the
>>>>>> >>> unnecessary ones.." mean ? Anyway, I suppose I'll cross that
>>>>>> bridge
>>>>>> >>> when I come
>>>>>> >>> to it.
>>>>>> >>>
>>>>>> >>> -p
>>>>>> >>>
>>>>>> >>> ..............................
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> Jonne Nauha wrote:
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>> Here is a wiki page where I tried to cover the most server
>>>>>> and auth
>>>>>> >>>> types and how to login to/with them.
>>>>>> >>>>
>>>>>>
>>>>>> http://wiki.realxtend.org/index.php/Getting_Started_with_Naali#Login_to_worlds
>>>>>> >>>>
>>>>>> >>>> - Jonne
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>> --
>>>>>> >>> Paul Fishwick, PhD
>>>>>> >>> Professor and Director, Digital Arts and Sciences Programs
>>>>>> >>> University of Florida
>>>>>> >>> Computer & Information Science and Eng. Dept.
>>>>>> >>> Bldg. CSE, Room 301
>>>>>> >>> P.O. Box 116120
>>>>>> >>> Gainesville, FL 32611
>>>>>> >>> Email: fishw...@cise.ufl.edu <mailto:fishw...@cise.ufl.edu>
>>>>>> >>> Phone: (352) 392-1414
>>>>>> >>> Fax: (352) 392-1220
>>>>>> >>> Web: http://www.cise.ufl.edu/~fishwick
>>>>>> <http://www.cise.ufl.edu/%7Efishwick>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>
>>>>>> >>
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Best regards,
>>>>>> Jonne Nauha
>>>>>> realXtend developer
>>>>>>
>>>>>> http://www.realxtend.org/
>>>>>> http://www.evocativi.com/
>>>>>>
>>>>>>
>>>>> --
>>>>> Paul Fishwick, PhD
>>>>> Professor and Director, Digital Arts and Sciences Programs
>>>>> University of Florida
>>>>> Computer & Information Science and Eng. Dept.
>>>>> Bldg. CSE, Room 301
>>>>> P.O. Box 116120
>>>>> Gainesville, FL 32611
>>>>> Email: fishw...@cise.ufl.edu
>>>>> Phone: (352) 392-1414
>>>>> Fax: (352) 392-1220
>>>>> Web: http://www.cise.ufl.edu/~fishwick
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Jonne Nauha
>>> realXtend developer
>>>
>>> http://www.realxtend.org/
>>> http://www.evocativi.com/
>>>
>>>
>>
>> >
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/realxtend
http://www.realxtend.org
-~----------~----~----~----~------~----~------~--~---
