Skip to content

Conversation

@Ingrater
Copy link
Contributor

@Ingrater Ingrater commented May 13, 2020

  • Seperate the concepts of generator, target architecture and compiler. This allows to compile for a single target platform with multiple compilers. For example its now possbile to compile with clang on windows.
  • Add better detection of target architecture by actually invoking the compiler instead of relying on cmake quirks.
  • Cleanup handling of warnings for msvc. Do not ignore them through header files, instead ignore them through compiler options. This doesn't leak the ezEngine warning settings to customers.
  • Adds propper support for VS 2019. Fixes Buildsystem cannot distinguish VS 2017 and VS 2019 #223

Ingrater added 3 commits May 11, 2020 17:41
…der files, instead ignore them through compiler options. This doesn't leak the warning ignores to customers.
@Ingrater Ingrater requested a review from jankrassnigg May 13, 2020 20:15
@jankrassnigg
Copy link
Member

Do not ignore them through header files, instead ignore them through compiler options.

😄


// Make sure all components are set to the same value
#if EZ_SIMD_IMPLEMENTATION == EZ_SIMD_IMPLEMENTATION_SSE
#if (EZ_SIMD_IMPLEMENTATION == EZ_SIMD_IMPLEMENTATION_SSE) && EZ_ENABLED(EZ_COMPILER_MSVC)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this stuff MSVC specific?
@C-Core

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only MSVC defines __m128 as a union. On clang and gcc __m128 is a opaque data type with no members. Thats why all these tests only work on msvc.

@jankrassnigg
Copy link
Member

Why do you need to check in a binary file (.o) ?

Copy link
Member

@jankrassnigg jankrassnigg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! This is a really great improvement!

@Ingrater
Copy link
Contributor Author

Why do you need to check in a binary file (.o) ?

Adding this file was unintentional. Will remove.

@Ingrater Ingrater merged commit d94d3bf into dev May 14, 2020
@Ingrater Ingrater deleted the user/bt/buildSystemCleanup branch May 14, 2020 09:31
@jankrassnigg jankrassnigg added this to the Next Release milestone Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Buildsystem cannot distinguish VS 2017 and VS 2019

3 participants