Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #765  -  Cannot build Arx since recent commits
Posted Aug 20, 2015 - updated Aug 21, 2015   Shortlink: http://arx.vg/765
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "NOT AN ISSUE".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    NOT AN ISSUE
  • Priority
    Not determined
  • Reproducability
    Always
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Hi there! I'm getting: Error MSB6006 "cmd.exe" exited with code 1. arx C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets 170

when I try to rebuild the latest source. When I try custom target commands the CMake error logs show that visual studio is trying to find a pthread file. So maybe some library is not ptoperly linekd now?

Thanks
Steps to reproduce this issue
Nothing entered.

#1
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Aug 21, 06:26
That's odd, and I don't recall any recent changes that could have cause this.

Could you start with a clean build directory and the post the full cmake output form that?
#2
icon_reply.pngReply
Comment posted by
Guest user
icon_reply.pngAug 21, 09:42, in reply to comment #1
My bad. I have not noticed that the GLM version was bumped up. Updated GLM and now everything is fine! Sorry for the false report!
#3
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Aug 21, 09:43
Awesome. Thanks for testing :D

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to NOT AN ISSUE.