Development environment

[felipezacani]

Hey, I tried to search for this, but it is complicated to locate.

I'm thinking about contributing to openxcom and I was wondering what it the dev. environment most contributors use. I'm talking about OS, IDE (if using one), code editor, compiler. I work with different environments in my job and hobby programming and I would like to hear comments or advice about the most productive way to start.

Thanks!

[Meridian]

I am not really contributing (only had one PR so far), but my setup is:
- OS: Windows 7
- IDE/compiler: Visual Studio 2010
- Git bash
- Git Extensions GUI

Info how to set it up: https://www.ufopaedia.org/index.php?title=Compiling_with_Microsoft_Visual_C%2B%2B_%28OpenXcom%29

[myk002]

I use:
- OS: Gentoo Linux (or OSX -- it's the same workflow)
- IDE: Netbeans
- Compiler: gcc on Linux, clang on OSX
- git
- ah, and cmake

[DoxaLogos (JG)]

I use..

- OS: Linux (Ubuntu 14.04 LTS 64-bit)
- IDE: VIM  (sudo apt-get install vim-gtk   ... be ready for a steep learning curve that pays off long term)
- Compiler: gcc  (sudo apt-get install build-essential)
- git  (sudo apt-get install git)
- CMake ( sudo apt-get install cmake) or Make

[SupSuper]

We support a wide variety: https://www.ufopaedia.org/index.php?title=Compiling_(OpenXcom)
The leads use Windows / Visual Studio.

[felipezacani]

Thank you all for the friendly replies. I think I'll go with the leads. It is what I have most of the time during travels. git cloning my fork now!

[DoxaLogos (JG)]

No problem! Do what works for you and enjoy! 

[Xtendo-com]

I would recommend to use a dark style of desktop environment like in screenshot if you feel a pain in eyes even with rest breaks. For me that makes more easy to read text from monitor and no eye pain after some time of reading.

[Xtendo-com]

- OS: Host Windows 7 SP1 64bit, Guest XUbuntu 14.04 32bit using virtualbox
- IDE: None.
- Code editor: notepad++ in Windows and notepadqq in XUbuntu
- Compile: under XUbuntu 14.04. I use make from src/makefile.simple (Linux binary) or src/makefile.mxe (Windows binary). You can found makefile.mxe form Yankes or Meridian repository.
- Watch variables through log: I add Log(LOG_VERBOSE) << " Text of variable: " << variable and run linux binary through terminal with enabled verbose output in openxcom config.
- Step-by-step execution and breakpoints: GDB. In order to compile with symbols (you get "no debugging symbols error" in GDB) just modify src/makefile.simple and add -g option into CXXFLAGS. Recompile.
- Git: command-line version

[JDarthenay]

- OS: Windows 7 64-bits
- No IDE, only Notepad++.
- Building with MinGW toolchains provided by MSys2. But also did it with TDM-GCC-64.
- Building most often 64-bits release binary but can also build 32-bits and/or debug binary.
- I build statically with yaml-cpp.0.5.3 and c++11 standard even though this is discouraged by SupSuper, but I have also successfully built with yaml-cpp.0.5.1 with c++98.
- I build dynamically with SDL 1.2, SDL_mixer 1.2, SDL_image 1.2 and SDL_gfx.
- I provide instructions and makefiles to build OpenXcom the same way as me in my GibHub repository in branch MinGW-w64.