Skip to main content
InfiniteMort
Up and Coming
May 16, 2015

0.6.0.0 Changes to build configurations?

The 0.6.0.0 SDK no longer contains the pre-built LibOVR.lib, LibOVR64, LibOVRd.lib and LibOVR64d.lib files, that previous versions of the SDK did. It's still possible to compile these library files manually, but looking at the build configurations I see that there are now two new build configurations: DebugSingleProcess and ReleaseSingleProcess.

Anyone care to explaint he difference between the Debug/Release and the DebugSingleProcess/ReleaseSingleProcess build configurations and what purpose the new configurations serve?

PS) The 0.6.0.0 readme.txt still refers to version 0.5. I guess someone forgot to update the file.

    7 replies

    jherico
    Inspiring
    May 19, 2015
    Make sure you're downloading the platform specific SDK (i.e. ovr_sdk_win_0.6.0.0.zip). The lib files are located in OculusSDK/LibOVR/Lib/Windows/*
    Brad Davis - Developer for High Fidelity Co-author of Oculus Rift in Action
    mattnewport
    Up and Coming
    May 19, 2015
    The lib files are located in OculusSDK/LibOVR/Lib/Windows/*


    Not in the .zip I downloaded. I had to build the libraries myself.

    *Edit*. Looks like they added the .libs to the .zip, I re-downloaded and the new .zip does have the libs in the above folder. The OP might want to try downloading the SDK again.
    cybereality
    Inspiring
    May 19, 2015
    Looks fine to me. Please download the SDK for Windows again and see if it looks OK.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    mattnewport
    Up and Coming
    May 19, 2015
    This thread confirms that the SDK was originally uploaded without the .libs included. I downloaded again this morning and the .zip now had the precompiled .libs.

    In general I think it's bad practice to release downloads with the same version number but different contents as it leads to a lot of confusion when trying to track down a problem if it is present in some downloads of SDK 0.6.0.0 and not in others. I think if a mistake is made in packaging an SDK release the fixed version should carry a different version number (SDK 0.6.0.1 might have been appropriate in this case).
    cybereality
    Inspiring
    May 19, 2015
    Yes, I just saw that post as well. Sorry for the confusion.

    Not sure it deserves it's own version number as it was originally supposed to be in the release.

    I do understand what you are saying, though.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    Constellation
    Up and Coming
    May 25, 2015
    I re-downloaded and now I have release libs but not debug. Are these also missing from the install or are these now something you need to build for yourself? Previous SDK's had them and personally I'd still like to have them for convenience and for peace of mind that I'm using the official libs.
    kondrak
    Inspiring
    May 25, 2015
    Yes, they are indeed missing. I built them debug along with the Samples project - Release libs are more important but I agree it would be convenient if debug came along with the SDK as in previous versions.

    If you're developing a bigger application be wary that the default settings for debug libs in VC++ is to create a multithreaded non-dll (/MtD instead of /MDd), so you might want to change that beforehand to be "compatible" with the multithreaded dll release lib.
    Terms & ConditionsAccessibility statement