Author Topic: Building openXCom in 64-bits with MinGW on Windows  (Read 24259 times)

Offline JDarthenay

  • Captain
  • ***
  • Posts: 55
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #45 on: May 01, 2016, 09:07:04 pm »
That will permit to pass the automatic check I failed, but it would be even better if I could also add it in MVS project as most Windows users use it... Is there anything else to update?

Online Yankes

  • Commander
  • *****
  • Posts: 3245
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #46 on: May 02, 2016, 12:59:02 pm »
`pch.h` if you add new headers. This is used by precompiled headers for VS but I don't know if anyone is using it right now.

Offline JDarthenay

  • Captain
  • ***
  • Posts: 55
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #47 on: May 02, 2016, 06:38:59 pm »
Are you sure there is only one file such as this one?
I see only header files from "Engine" and "Interface" folders.

Online Yankes

  • Commander
  • *****
  • Posts: 3245
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #48 on: May 02, 2016, 09:29:49 pm »
Are you sure there is only one file such as this one?
I see only header files from "Engine" and "Interface" folders.
AFAIK whole point of pch is having only one for whole project. Why only this folders? Maybe because this is most common part. Better ask person who create this file (probably SupSuper) for more accurate answer.

Offline JDarthenay

  • Captain
  • ***
  • Posts: 55
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #49 on: May 02, 2016, 09:50:54 pm »
Yes, let's wait for his answer.
By the way Supsuper, could you move this topic to the development forum? Actually, it would be more its place.

Offline SupSuper

  • Lazy Developer
  • Administrator
  • Commander
  • *****
  • Posts: 2161
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #50 on: May 05, 2016, 11:50:06 am »
My knowledge of make is basic, I did not even write it, I only modify to work for me. Because building system is not my focus, if it work I can leave it as is even if it not perfect. Bigger problem for me is cmake and VS project because each time I add some file I need update them manually. I don't have this problems with makefiles.
CMake supports wildcards, but apparently developers don't like it. :P It would make my job easier as well but I'd rather not touch what I'm not experienced with.

AFAIK whole point of pch is having only one for whole project. Why only this folders? Maybe because this is most common part. Better ask person who create this file (probably SupSuper) for more accurate answer.
The point of pch is to precompile headers that rarely change, this is the system/language headers and the Engine/Interface stuff in OpenXcom's case. Adding every header would just force a rebuild on every change.
I believe it's only used by MSVC and Makefile.pch though, and it's usually disabled because it tends to hide "include errors" on some compilers.

Offline R1dO

  • Colonel
  • ****
  • Posts: 438
    • View Profile
Re: Building openXCom in 64-bits with MinGW on Windows
« Reply #51 on: May 05, 2016, 12:53:15 pm »
CMake supports wildcards, but apparently developers don't like it. :P It would make my job easier as well but I'd rather not touch what I'm not experienced with.

If with wildcards you mean GLOB please take into account the cmake devs advice against it for generating a list of source files.

See cmake documentation and check the note halfway down, which reads:
Quote
We do not recommend using GLOB to collect a list of source files from your source tree. If no CMakeLists.txt file changes when a source is added or removed then the generated build system cannot know when to ask CMake to regenerate.