-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-03-03 18:12, Mathieu Bouchard wrote:
Le 2012-02-27 à 10:34:00, IOhannes m zmoelnig a écrit :
On 2012-02-26 19:50, Mathieu Bouchard wrote:
Or else just discontinuing the MSVC edition...
no.
Why do you need to keep a MSVC edition, again ? You probably told me already, but I don't remember.
i think there are two things:
- writing code that compiles on _both_ MSVC and gcc gives me a better
feeling of "standard conformity". people using only gcc tend to use gcc-specific extensions (which is ok if you only ever intend your program to be compiled with gcc; similarily, it is ok to make heavy use of msvc-specifics if you don't care about gcc; i prefer code that makes few assumptions about the used compiler)
Are there libraries that people use with GEM that require MSVC and can't work with MinGW ?
unfortunately yes. some of the proprietary video backends (NaturalPoint,...) only come with c++-libraries compiled with msvc. it doesn't help to say "then don't support them", if your employer bought already bought their system.
also the current implementation of the DirectShow backend is tied to MSVC.
again, a solution would be to use a C-wrapper for anything that involves crossing dll-boundaries (all video acquisition in Gem is nowadays done in separate dlls)...
fgmasdr5 IOhannes