Skip to content

How to get rid of experimental GLM_GTX_component_wise #1385

@armagedescu

Description

@armagedescu

Hi,
Please provide a way to get rid of experimental components by default, silently. Provide way to enable them for ONLY the ones who really wants to use them.
While upgrading any other libraries (glew, glfw, stb, assimp....), the upgrading went seamlessly.

There is experimental GLM_GTX_component_wise which I don't want to use but it is inserted in lots of headers, for instance norm.hpp.
When I compile with glm fresh clone from GitHub (1.0.2?) there is a compile error.. Why the error suggesting that I fail to use some experimental extension? I don't intend and don't want to use it. I see the fix for "... if you really want to use it.", but what if I really want to NOT use it? My intention is to use glm without experimenting and without polluting the code with defines, which is lots of sources actually.

That is introduced in following file, and not only:
/glm/glm/gtx/component_wise.hpp
Compile error, explicitly caused by following lines

#ifndef GLM_ENABLE_EXPERIMENTAL
#	error "GLM: GLM_GTX_component_wise is an experimental extension and may change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really want to use it."
#elif GLM_MESSAGES == GLM_ENABLE && !defined(GLM_EXT_INCLUDED)
#	pragma message("GLM: GLM_GTX_component_wise extension included")
#endif

The problem started when I switched from glm-0.9.9.7 to glm-1.0.1, and the latest GitHub revision (v1.0.2?) has the same problem.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions