Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x86 built in x64 #1165

Closed
OriginLive opened this issue Dec 15, 2016 · 7 comments
Closed

x86 built in x64 #1165

OriginLive opened this issue Dec 15, 2016 · 7 comments
Labels

Comments

@OriginLive
Copy link

OriginLive commented Dec 15, 2016

Using winbuild on windows 10 and trying to compile for x64 ver. I get
..\builds\libcurl-vc14-x64-debug-static-ipv6-sspi-winssl-obj-lib/file.obj : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

apparently it works if i use the correct vs console

@OriginLive
Copy link
Author

OriginLive commented Dec 15, 2016

using VC files gives me an issue with language in .rc file

@bagder
Copy link
Member

bagder commented Dec 15, 2016

So the first issue is solved and now you changed it to something else?

@bagder bagder added the build label Dec 15, 2016
@OriginLive
Copy link
Author

OriginLive commented Dec 15, 2016

No, it's a bit unrelated. I managed to get it to compile (The x64 ver still has problems with debug and static lib). I should rather say the second issue is that i cannot open the included visual studio files, because they give me an error about .rc file having wrong language defined

@bagder
Copy link
Member

bagder commented Dec 15, 2016

and you feel that is our problem?

@OriginLive
Copy link
Author

OriginLive commented Dec 15, 2016

Yes, i would say a faulty libcurl.rc file is your problem

@bagder
Copy link
Member

bagder commented Dec 15, 2016

okay so how exactly is it faulty? What does "wrong language defined" mean?

@OriginLive
Copy link
Author

OriginLive commented Dec 15, 2016

I got an err: a resource in this file uses an unknown language 0x3
But it works now, for reasons unknown to me. So i guess this is problem solved

@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants