strange GLFW error with rev 423f4d9 from bitbucket

2»

Comments

  • jimjim
    edited June 2013
    Okay, I will get the mingw branch when I get home, is there any download button for that branch or I need to clone the whole repo to get that branch.
  • iarwainiarwain
    edited June 2013
    You can either clone the repository (which makes it much easier to stay up-to-date and switch from branches/versions to other ones), or go to the download page, and download any tag/branch version from there.

    You can actually download any specific version, at a given commit, by using a similar URL and simply replacing the name of the tag/branch by the hash of the changeset:
    https://bitbucket.org/orx/orx/get/<hash>.zip
  • jimjim
    edited June 2013
    Oh, I missed the download page. I would better clone the whole repo with source tree, last time they had no hg support. I hope its not much different from git, which I frequently use.
  • iarwainiarwain
    edited June 2013
    hg's very similar to git. Actually I think there are probably bridges that would let you use the hg repository seamlessly from git.
  • jimjim
    edited June 2013
    I tried the new branch today. Assert on the clock demo is gone, but still having the same assert for sound tutorial 
    [23:12:46] [ASSERT] [orxSoundSystem.c:orxSoundSystem_OpenAL_SetPitch():1768] [AS
SERT] : <eError == AL_NO_ERROR && "OpenAL error code: 0xA003">
AL lib: (EE) DSoundPlaybackProc: WaitForSingleObjectEx error: 0x102

    Also, while building rox for debug I got some warnings like this 
    ../../../include/../plugins/Display/GLFW/orxDisplay.c:4382:56: warning: invalid suffix on literal; C++11 requires a space between literal and identifier [-Wliteral-suffix]

    Its may be C++11 related
  • iarwainiarwain
    edited June 2013
    Mmh, the sound tutorial works fine for me with the 4.7.2 branch.
    Not sure what I can do about, sorry. Did it work fine with the previous version?

    For the C++11 warning, I haven't modified any code to be C++11 compliant yet (most compilers are still not implementing the full specs anyway), so I'd recommend simply turning off this specific warning for now.
  • jimjim
    edited June 2013
    The tutorial works fine with release and profile mode, assert is only there in debug. I tried 1.4 now, surprisingly the assert is also there. I don't know what is wrong here.

    edit: the assert is triggered when I pressed down the LEFT_KEY and pitch becomes 0
  • iarwainiarwain
    edited June 2013
    Ah thanks for the detail, I'll update the tutorial to make sure this situation never happens then, it'll be cleaner. :)
  • jimjim
    edited June 2013
    This assert only triggered for mingw + debug build.
Sign In or Register to comment.