kacejot / xray-16 Goto Github PK

This project forked from openxray/xray-16

X-Ray Engine 1.6 expansion. Original version was used in S.T.A.L.K.E.R.: Call of Pripyat.

License: Other

CMake 0.68% C++ 77.50% C 18.72% Objective-C 0.39% Cuda 0.09% Makefile 0.35% TeX 0.01% Lua 0.33% Python 0.01% GLSL 0.61% HLSL 0.43% Pascal 0.05% C# 0.28% M4 0.04% Shell 0.44% Perl 0.05% Batchfile 0.02%

xray-16's Introduction

OpenXRay

OpenXRay is an improved version the X-Ray engine, used in world famous S.T.A.L.K.E.R. game series by GSC Game World.

Supported games

Call of Pripyat	Clear Sky	Shadow of Chernobyl
Yes	Beta (see #382)	Not yet (see #392)

Build status

Platform	Compiler	Configurations	Status
Windows	MSVC	Debug / Mixed / Release (x64/x86)
Linux	GCC	Debug / Release (x64/x86)

Documentation

How to
Build and setup	On Windows	On Linux
Install and play	On Windows	-

Changelist and more is available in wiki.

More details

This repository contains X-Ray Engine sources based on version 1.6.02. The original engine is used in S.T.A.L.K.E.R.: Call of Pripyat game released by GSC Game World.

It is a place to share ideas on what to implement, gather people that want to work on the engine, and work on the source code.

If you find a bug or have an enhancement request, file an Issue.

Pull requests appreciated! However, the following things should be taken into consideration:

We want to keep the game as close as possible to the vanilla game, so instead of introducing new gameplay features, consider adding non-gameplay features, fixing bugs, improving performance and code quality
Major changes should be discussed before implementation
Follow the procedures

Be advised that this project is not sanctioned by GSC Game World in any way – and they remain the copyright holders of all the original source code.

xray-16's People

Contributors

Watchers

xray-16's Issues

Fix build after removing "-fpermissive" compile flag

Refactor ProblemSolver

Remove problem_solver_inline.h
Move all header files to top
Remove inline qualifier
Decompose this class - it is overloaded

BugTrap include directories should be automatically delivered to the target similar to target_include_directories command (If some target is linked with BugTrap, inlude files are added to this target build process automatically)
BugTrap binaries should be exported as well: any target that links with BugTrap automatically links necessary libraries.
custom target is added only for windows builds

Suggestions:
The best way is to use add_custom_target command similar to this example:

add_custom_target(
    ${PROJECT_NAME} ALL
    COMMAND ${BUILD_SCRIPT}
    WORKING_DIRECTORY ${PROJECT_SOURCE_DIR})

set_property(TARGET  ${PROJECT_NAME} PROPERTY IMPORTED_LOCATION "${BINDIR}/${LIB_NAME}")
target_include_directories(${PROJECT_NAME} PUBLIC ${PROJECT_HEADERS})

Move to CMake

Now the project has two build systems:

CMake - works fine for Linux only
Visual Studio solutions and projects

As far as CMake can generate VS projects, the best way will be to use CMake only.

Now CMake on Windows can't even generate project files because of next errors:

CMake Error at CMakeLists.txt:46 (install):
  install called with unknown mode $<TARGET_FILE:luabind>
Call Stack (most recent call first):
  Externals/CMakeLists.txt:3 (xr_install_file)


CMake Error at CMakeLists.txt:52 (install):
  install called with unknown mode $<TARGET_FILE:luabind>
Call Stack (most recent call first):
  Externals/CMakeLists.txt:3 (xr_install_file)

Error occurs here:

install($<TARGET_FILE:${tgt}>
    CONFIGURATIONS Debug
    RUNTIME DESTINATION Debug/)

and here:

install($<TARGET_FILE:${tgt}>
    CONFIGURATIONS Release
    RUNTIME DESTINATION Release/)

I think the reason is that install command requires mode to be filled (source).
So, I need to research which mode is the best one. FILES works, but who knows what the impact is.

Update Readme

Rid of original repo readme.