[GH-ISSUE #531] Any consequences building for x86 ? #293

Closed
opened 2026-02-27 15:49:44 +03:00 by kerem · 2 comments
Owner

Originally created by @ghost on GitHub (Sep 22, 2016).
Original GitHub issue: https://github.com/quasar/Quasar/issues/531

Are there any consequences in building & using the client for x86 architecture, rather than using "Any CPU" ?

Originally created by @ghost on GitHub (Sep 22, 2016). Original GitHub issue: https://github.com/quasar/Quasar/issues/531 Are there any consequences in building & using the client for x86 architecture, rather than using "Any CPU" ?
kerem 2026-02-27 15:49:44 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@yankejustin commented on GitHub (Sep 22, 2016):

I am pretty sure it should be fine! :)

<!-- gh-comment-id:248899056 --> @yankejustin commented on GitHub (Sep 22, 2016): I am pretty sure it should be fine! :)
Author
Owner

@MaxXor commented on GitHub (Sep 22, 2016):

I think you mixed something up. The client is always built for x86 architecture. lol

<!-- gh-comment-id:248961073 --> @MaxXor commented on GitHub (Sep 22, 2016): I think you mixed something up. The client is always built for x86 architecture. lol
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#293
No description provided.