alternative way to setup MG in eclipse

[titi]

As I wasn't very happy with setting up an eclipse project using cmake, here is an alternative description (for linux):

step1:
Checkout MG.
run build-mg.sh and make everything work so you can compile MegaGlest

step2:
Import MG in eclipse ( via right click ):

Choose the source directory in your svn checkout.


step3:
Setup compile options in eclipse:
-  change make call to "make -j4" where 4 is the number of CPU-Cores you have.
-  set build directory to "build" in your checked out directory.


step4
Setup run configuration so you can launch MG directly form eclipse:


update:
We had some trouble to setup this for my son. All external things( from libs ) were marked as error.

To fix it we disbabled "build automatically" and made a "Project->clean" after this.

[Omega]

I'm curious, could this work in Windows too if we used the MinGW toolchain?

[softcoder]

No since we don't have a ming dependencies archive (at least not up to date).

[Omega]

Pity. I'm not a fan of visual studio, which often bugs up on me, but Eclipse is a fantastic IDE. Do these dependencies exist around the web, though? Would it be possible to manually download each one needed?

[softcoder]

The big question is whether all the deps compile (or are available) under mingw compiler. A while back i did this using mingw on Linux, but haven't updated it for a long while.  Nothing stops you from trying, the cmake script has the support for proably 90% of mg building in mingw, I think the script i built for that (in Linux) is in the same folder as the Linux build script but the ming script is called build-mg-win32.sh (which shows how to call cmake for using mingw)

[titi]

We had some trouble to setup this for my son. All external things( from libs ) were marked as error.

To fix it we disbabled "build automatically" and made a "Project->clean" after this.


!! PLease report if you have any Problems with this!!

[titi]

touch

[Omega]

I actually started typing up how I eventually "figured out" how to get rid of the various errors Eclipse thought I had. It was caused by the SDL_types include in shared_lib/include/platform/sdl/data_types.h. The file has a line:

Code: [Select]

#include <SDL_types.h>
which had to be changed to

Code: [Select]

#include <SDL/SDL_types.h>
But now I've got yet more errors (I'm leaving what I already typed in case it's useful for anyone else).

Honestly, getting MG to work in Eclipse has been nothing but a complete disaster for me. I've spent more than 5 hours trying to get the errors to go away. I've tried every Stackoverflow answer I could find, advice from the IRC, and more. So now I've just disabled all code analysis in Eclipse. I hope those CMake files are well configured in regard to warnings.

If anyone else needs to do this, for Eclipse 4.4 Luna, go to Project > Properties > C/C++ General > Code Analysis and switch to "Use project settings", then uncheck every box. Then go to the "Launching" subcategory and make sure both boxes are unchecked.

This keeps the index intact, so you can still use the call hierarchy (etc), but completely removes all warnings and errors in Eclipse. You'll have to compile to find warnings and errors.