Hello Eric,
Maslowski, Eric wrote:
> - which branch/version of 2.0 should I grab?
trunk (or very recent snapshot of trunk), Gerrit has put a lot of work
into the windows build and worked out a bunch of problems recently.
(is trunk known to work 64-bit and stable)
we use fairly recent snapshots of trunk and update once in a while (if I
do it too often everybody complains about having to rebuild their apps
again ;) ). We only use 64 bit builds, although on linux.
> - has there been any change to which version of the
> dependencies should be used?
>
> o boost 1.37
> o collada 1.4 (tried 1.5 too)
there are two version involved when referring to collada: one is the
schema version (which must be 1.4 at this point) and the version of the
colladadom libraries which should be 2.1 or 2.2
> o jpeg 7.1
> o png 1.2.40
> o tiff 3.9.1
> o openEXR 1.4
> o zlib 1.2.3
> o GLEW 1.5.1
> o freeglut 2.6.0
>
> - I know I have to compile the above for 64-bit but are there
> any known binaries for these around?
I know of no prebuilt binaries, but there are cmake scripts that can
build these with the correct settings from the sources, take a look in
Support/ReadMe.txt
> They each seem have their own
> issues and won't compile 100% without some work. I think I have these
> compiled successfully, but with all of the unresolved externals and
> other issues I'm seeing, I have my doubts.
hm, I only have a little experience with 32 bit windows, but there they
usually build without too much trouble. Some of the above do depend on
others in the list though, e.g. jpeg, png depend on zlib and I think
tiff depends on jpeg.
What sorts of unresolved symbols do you get?
> - If library binaries are available, should I be compiling
> these libraries for DLL or static lib?
the scripts in Support/ give you either option (and you need to tell the
main OpenSG build which ones to use). I've usually build DLLs, copy them
to a central location by build type (e.g. to a directory
C:\devel\libpool_debug) which I put into PATH so that the DLLs are found
at runtime.
> I've been trying this for the past couple of days and have slowly begun
> making progress in resolving the many unresolved externals and other
> compiler errors I've been receiving. However, there is so much left to
> do that I figured I would ask the OpenSG 2.0 experts for some advice
> before beating my head on this anymore.
I can't really speak for 64bit windows as I don't have one here (only
32bit), but apart from being tedious I've not encountered too much
trouble building the dependencies on windows.
I'd suggest trying the build scripts from Support/, if that does not
help we'd need some more details about the errors you are seeing to see
if it is something we can improve on our end.
Cheers,
Carsten
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
