Skip to content

Conversation

kankaristo
Copy link

Closes #488.

There were a few issues with different operator functions, which caused undefined reference errors:

  • some had duplicate declarations (removed)
  • others had missing definitions (added to glm/detail/type_vec4.inl; I also changed the parameter names to match similar functions in other vector classes)
  • one declaration didn't match the definition (fixed in glm/detail/type_mat4x2.hpp).

I guess you only get these errors if the template function is instantiated (i.e. you actually use the function). Weirdly enough, I don't get errors for all of the duplicate declarations I've fixed here (only some of them), but everything else produces an undefined reference error without these changes.

@Groovounet Groovounet added the bug label Mar 12, 2016
@Groovounet Groovounet added this to the GLM 0.9.8 milestone Mar 12, 2016
@Groovounet Groovounet self-assigned this Mar 12, 2016
Groovounet added a commit that referenced this pull request Mar 12, 2016
@Groovounet Groovounet merged commit e64e771 into g-truc:master Mar 12, 2016
@Groovounet
Copy link
Member

Thanks for contributing!

Groovounet added a commit that referenced this pull request Mar 12, 2016
@kankaristo kankaristo deleted the undefined-reference-errors branch March 13, 2016 04:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Undefined reference errors for operator functions
2 participants