76
Q-Gears / Re: Q-Gears v0.20
« on: 2011-11-22 04:59:09 »So you are using the last build suit? I don't know how Ogre's versioning system works, and I know that 1.8 is due in January. However 1.6.5 is consider stable, 1.7.XXX was not. I was going to ask that question but it seems to be self evident. You appear to like to use the latest and greatest. That can create some dependency issues (IE people have to go around grabbing newer version of software). My version of linux is a pain to use the latest and greatest with because it's considered unstable by the maintainers. I don't know if that is true however there are a huge number of bugs listed which relate to the 1.7.XXX and they don't specifically have to do with Ogre, mostly with the libraries it wants to use they have bugs that lead to security issues apparently.
It's a chronic problem with Linux one can end up having to update there entire library suite just to run one application only to find that those libraries make about 100 applications die horribly because the new versions are either incompatible or contain bugs that haven't been fixed that prevent them from playing nice. I could build OGRE 1.7.3 however as I just noted that can create a long list of other problems (like I experienced with GTK 3 for example). Java apps API do not play nicely with GTK 2/3 and throw up with lots of green relish and onions. (LOL) Although none of my other GTK based apps complain just anything using teabag. Sigh things just got a whole lot more complicated for me.
Hmmm you use code blocks right? Can that generate an automake or cmake config script?
Cyb
Now 1.7.x is stable. 1.6.x is previous stable. I use 1.7.2 because it is lastest SDK for mingw. Previously Ogre uses even versions to mark stable releases and odd to mark development version. Now they drop this practice and all versions are stable.
Codeblocks generate makefile.