Irrlicht Engine

I can't take this seriously. I taught myself how to program an Atari 800 in BASIC at age 11. Back then one got things done by PEEKing and POKEing OS memory addresses. I learned Linux 0.99-something after college on my own at age 23. Now there's an internet with search engines and 1 bazillion progra...

Ok thanks... now to perform the same exercise with ClanLib and Ogre, before working on any build systems. :-) Actually that's false. I already fixed some ClanLib Autoconf problems before even coming here, and I am resolved not to do any more such things until I understand the various 3d capabilities...

Sorry to stop in here, but for now hendu has a long register of very useful and almost always on-the-point additions to Irrlicht. In just over two years. While you made it to an astonishing 24 posts with about 80% discussions about personal opinions in six years. I have no present commitment to Irr...

I do question why that's a critical need for Irrlicht. Doing Windows builds from Linux has been supported for a long time now. It may be more common than you think. I very much doubt those builds are compiled and built against the very latest Visual Studio runtimes. I would expect them to be MinGW ...

It's perfectly possible that it's designed to do simple builds, no cross, no customization, with VS support. If so, then it clearly succeeds at its goal. However, that is not what I want or need, or for that matter, what Irrlicht needs. May not be a joy to do cross-compilation with, I will accept w...

Advanced users. The kind you want to use your project, because they tend to become developers later. The GUIs for those platforms allow even less control than the cmake cli tools. I can't take this seriously. I taught myself how to program an Atari 800 in BASIC at age 11. Back then one got things d...

Buying into proprietary tools like VS does not promote cross-platform growth either. It promotes lock-in. An open source outfit "with legs" has done the VS maintenance work for you. You don't have to and you're not locked in. CMake works, it's field proven, it's the most mature of build s...

Well, you know my stance on it: ignore people with IDEs. Practically no projects (as a % of all open source) include IDE project files with them, but only a standard build infra (make or autotools). Instantly only one place to update. In a CMake build, the "one place to update" is the CMa...

Coughing up a CMake or Premake build is a much more labor intensive way to deal with build issues in general, of which this shared vs. static lib stuff is a specific instance. I don't think it's illogical to suggest such a course of action, it's just a lot more work.

I was responding to CuteAlien's conjectures about doing CMake someday. Which is a component not presently in Irrlicht. Same as Premake would be. The Lua in Premake is embedded, it is not a separate component from Premake. For present realities, again, shared and static libs could be built with diffe...

Well, leaving the big build system planning horizon stuff aside, I think there are some more basic "best practices" for hand rolled Makefiles that could be done here. Like different suffixes for static and shared build rules. Or subdirectories for each, that's the other way to go typically...

Aw gee whiz. I haven't seen a "plain makefile" build in so long, I'm surprised that this level of build primitiveness exists. Why wouldn't the makefile rules have different suffixes for static vs. shared components? It is typical to want to build both static and shared versions of a librar...

This is shader-pipeline branch. On Lubuntu 12.10 Linux with GCC 4.7.2, some kind of compile incompatibility in CBSPMeshFileLoader.cpp involving -fPIC. bvanevery@nomad:~/devel/shader-pipeline/source/Irrlicht$ make -k sharedlib g++ -I../../include -Izlib -Ijpeglib -Ilibpng -I/usr/X11R6/include -DIRRLI...

As seen in the shader-pipeline branch, don't know if it affects trunk. "make install" behaves as though sharedlib should have been built already, but does not have sharedlib as a dependency. bvanevery@nomad:~/devel/shader-pipeline/source/Irrlicht$ sudo make -k install rm -f -r /usr/local/l...

Confirmed as fixed!