Issue #11 resolved

Update Ogre depencies

Beauty
created an issue

The current download link points to a very old depency package (zip file). \ Useful would be to use an updated depency package instead.

Details I wrote here: http://www.ogre3d.org/addonforums/viewtopic.php?p=98741#p98741 http://www.ogre3d.org/addonforums/viewtopic.php?p=98770#p98770

\ For special case OIS / MOIS read here: http://www.ogre3d.org/addonforums/viewtopic.php?p=98943#p98943 and the post below

\ We could (or should?) add a switch for depency download files related the Ogre version. \ Maybe Ogre 1.8 needs different depencies than Ogre 1.7. \ For differentiation it's useful to check the content of the config file option "OgreBranch".

Comments (8)

  1. Beauty reporter
    • changed status to new

    Thanks for your improvements. I reported about them in the official MogreBuilder forum topic.

    Questions:

    1) Does your modified MogreBuilder build the depencies from the sources?

    2) In file "AssembleBinaryFiles.cs" you removed the "warning message" (for debug builds) and its description.
    Did you build Mogre with "debug" setting?
    If yes - are you shure that all generated files are created in the correct build directory and copied to the output directory?

  2. Beauty reporter

    3) You added OIS to the "BuildOgreTask.cs".
    Does the MogreBuilder also build the MOIS wrapper?

    Notes:
    There is as well the file "BuildMoisTask", but currently it's not processed by the MogreBuilder.

    The source code of MOIS is located in the MogreAddons repository. The MogreBuilder can still clone this repository.

    I don't remember the option yet to clone the Add-ons repository. You could look how I applied the "-mogrenewt" option. It set the flag "inputManager.Option_MogreNewt". And in "TaskManager.cs" is check if an option was used, which needs to clone the Add-ons repository. In file "TaskManager.cs" search for the string "--- optional add-on tasks ---". There you see more.
    Sorry that I can't support you by extending the code. I need to concentrate to my diploma thesis.

    Beauty

  3. Andreas Schuster

    Sorry, didn't see those posts before answering on the topic. For the sake of completeness some short answers:

    1) Yes, dependencies are built from source

    2) Dependency building is included in Ogre's build process itself, so the binaries are created and copied together with Ogre in the correct directories. No need to check for binaries in dependencies folder. And yes, I tested it with both Debug and Release builds.

    3) MOIS is not built by MogreBuilder (not yet, give me a few days more ;-) ). But OIS was included in the old dependency archive, so I added it too.

  4. Log in to comment