Code blocks with mingw how to#
Code blocks with mingw .exe#

The second permitted me to compile CEGui for Ogre.īut I still have this 'entry point error' This is appropriate only if you have problem with the debug version not the relase version. Set in the file 'OgreConfig.h' the line :Īnd recompile completely Ogre ! This will remove the ogre debug version memory manager from ALL ogre code.

Second, more radical, this is the method I adopted. (This is the method used by Sinbad when he has problem with librares). You will need to try where to put them exactly. First, you can use #include 'OgreNoMemoryMacros.h' and #include 'OgreMemoryMacros.h'. There are two ways to deal with the OgreMemoryManager : Now the samples don't give me that entry point error, but now OGRE's memory manager causes the samples to crash. If someone is able to compile with mingw and run the samples, I would be really happy to know what is missing. Please: Don't tell me those for VisualC it's not useful I need those for mingw. I need to know which library version are needed. But there is something really strange with the cegui libraries included : opengl, directx and ogre. I am able to build and run Ogre in its opengl and directx version. The samples exe don't work! Now they work READ THE README : It explains which source files must be modified and optional build options. The OpenGl, DX9, DX8 and Ogre renderer are working ! These CB files contains debug and release projects. In the attachement are the CB files, which must be unziped in the root cegui directory.

Code blocks with mingw .exe#

exe (except DX8, Irrlicht which I don't need).

This topic is to help people compile CEGUI with Mingw + Codeblocks.

Code blocks with mingw how to#

But at least there are alternative option on how to deal with this.10 feb 06 - With the new forum the CB files are not attached anymore ! I asked crazyeddy to add the files to the cvs. It does not seem possible to prevent files from being added to these default Header and Sources folders in CB. Solution 1 and 3 are clean solutions, solution 2 is a workaround. The first solution is pretty quick, but has to be repeated for each class. The second solution is the least work, if you like these view settings and make sure the header file is also in the src folder (and not CB’s default include folder). Note: The last solution is probably the most work. Run the ProjectGenerator to create an OF-style project (read: with all the files in the src folder inside a virtual folder called src in the CB project). Remove the CB project files from the project’s root folder. Solution 3: Once the class files have been added, go through the following steps. Changing this view setting has to be done only once. Then the Sources and Headers folders in the CB project disappear and all files are shown under their physical folder (which is src if you followed the steps for the single physical folder solution as mentioned above). In the menu, go to “Project”, then “Project tree” and uncheck “Categorize by file types”. This has to be done each time you add a class. Solution 1: Manually drag both files (in CB’s project structure) from respectively the Sources and the Headers folder (and perhaps a subfolder inside that) to the src virtual folder. So they are not in the src virtual folder as the rest of the OF-added files. When adding a new class the source file is added to a Sources folder and the header file is added to a Headers folder. In the CB project (as generated by the ProjectGenerator) of all OF examples the files are placed in a virtual folder in CB called src. I haven’t found a way yet to change the default header file folder. Note: Unfortunately this has to be done manually, each time you add a class. Then the header file is placed in the src folder and thus both class files are in the same location. You can find it in the bottom left under “Header file” and then “Folder”. Solution: To ensure the header file of a class is also added to the src folder, you can manually set the folder location in the “create new class” dialog box. So the location on the hard drive differs. When you add a new class in CB, the source file is placed in the src folder, but the header file is placed in the include folder. In all OF examples the source and header files are in the same folder (namely the src folder).

In both cases the default behavior of codeblocks differs from the OpenFrameworks ProjectGenerator solution. There are two things relevant here, the location in a physical folder (read: where is the file on the hard drive) and the location in a virtual folder (read: where is the file in the codeblocks project).