how to run it in linux?

[xinsuinizhuan]

Is your feature request related to a problem? Please describe

A clear and concise description of what the problem is, e.g. "I'm always frustrated when [...]"

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here. Any relevant information for platform specific features could be useful.

[AnantTiwari-Naman]

Could you please like fill in the template / strip parts which you can't answer

[DaVikingMan]

The Hazel Engine(currently)only supports Windows.

[astralchan]

See Hazel/src/Hazel/Core/PlatoformDetection.h, specifically this section:

.
.
.
#elif defined(__linux__)
	#define HZ_PLATFORM_LINUX
	#error "Linux is not supported!"
#else
	/* Unknown compiler/platform */
	#error "Unknown platform!"
#endif // End of platform detection

This header will see if __linux__ is defined (which is defined on linux systems) and error "Linux is not supported!" Though, it does define HZ_PLATFORM_LINUX, which currently only seems to be used in Hazel/src/Hazel/Core/Base.h:

.
.
.
#ifdef HZ_DEBUG
	#if defined(HZ_PLATFORM_WINDOWS)
		#define HZ_DEBUGBREAK() __debugbreak()
	#elif defined(HZ_PLATFORM_LINUX)
		#include <signal.h>
		#define HZ_DEBUGBREAK() raise(SIGTRAP)
	#else
		#error "Platform doesn't support debugbreak yet!"
	#endif
.
.
.

Beyond that, I don't really see any other spots where HZ_PLATFORM_LINUX is used - and this is the only thing that gets defined before the build system errors out at the moment. Given the way they bother defining a platform for linux, it might be supported in the future. Here is what would happen if you were to try and built it now

premake5 gmake2
make -j4

In the mean time, check out PR#82, which is attempting to add Linux support.

[DaveAxiom]

Can we close this issue? Just see PR #82.

[astralchan]

Can we close this issue? Just see PR #82.

Maybe instead of closing it, add it to the tracker such that the issue will be closed once 82 is merged. As it stands, it is still an issue.