Label dlls

tgraupmann · Post by **tgraupmann** » Mon Jun 11, 2007 5:56 am

When I compile Ogre 1.4.2 from source on Windows, the DLL assembly info isn't filled out. (version???) I'd like to make a feature request to start doing this.

Compiling in VC8 Express.

Quall · Post by **Quall** » Mon Jun 11, 2007 6:09 pm

Is the info filled out in the pre-compiled binaries?

I am not an ogre dev, but I know many projects do not do this for a specific reason. If version info was defined, then people who modify the source before compiling will end up with a dll that states it is ogre version X.X.X, but in reality would be a modified version. Most people don't change that information when they compile projects from source. It may screw a bit with windows if you have 2 different dll's that give the same version and generally may cause applications to crash if windows points to the wrong one (if they are both registered).

tgraupmann · Post by **tgraupmann** » Mon Jun 11, 2007 7:37 pm

I'd be satisfied with "Ogre 1.4.2.Unofficial". Any version info is better than none.

Post by **jacmoe** » Mon Jun 11, 2007 8:05 pm

Anything you can't do using the OGRE_VERSION macro?

Like

#if OGRE_VERSION < ((1 << 16) | (3 << 8 ) | 0)

.. ?

Post by **sinbad** » Tue Jun 12, 2007 12:52 pm

Patch the ogrenew/bumpversion.sh script and I'll consider it

Post by **:wumpus:** » Fri Jun 15, 2007 2:01 pm

IMO you should package your own Ogre dlls with your application, and not install them to a central place. This way, versioning/registry info doesn't really matter and it's always safe from the problem mentioned by Qual.

tgraupmann · Post by **tgraupmann** » Sun Jun 17, 2007 3:25 pm

:wumpus: wrote:IMO you should package your own Ogre dlls with your application, and not install them to a central place. This way, versioning/registry info doesn't really matter and it's always safe from the problem mentioned by Qual.

In my case, I'm more thinking about working on an application using Ogre 1.2.3. Everything is great. Multiple developers checking in code, keeping the latest exe checked in for non-developers to see our work. They also have a habit of checking in the Ogre dlls that they compiled, but that's ok because we are on the same version. And then party time Ogre 1.2.4 comes out. I upgrade the project, check in the new dependencies and dlls, life is good. The other devs are finishing up their code, and then merge. And in the dll merge process we get a little confused, because you always get that 1 or 2 developers that have merge phobia and do something weird. And then all the sudden which version of Ogre are we using again? I check in my dlls, they check in theirs, and nobody knows what version we are on now.