[nanomsg] Re: x64 Windows Build
- From: "Dave" <dave@xxxxxxxxxxxxxxxxxx>
- To: <nanomsg@xxxxxxxxxxxxx>
- Date: Thu, 29 May 2014 07:57:08 -0500
Thanks so much, I've pulled down the repo and will track down 248. Does
that mean that the x64 fixes were not automatically embedded into the
master?
From: nanomsg-bounce@xxxxxxxxxxxxx [mailto:nanomsg-bounce@xxxxxxxxxxxxx] On
Behalf Of Stan Mihai
Sent: Wednesday, May 28, 2014 10:57 PM
To: nanomsg@xxxxxxxxxxxxx
Subject: [nanomsg] Re: x64 Windows Build
Cmake without arguments will automatically select a compiler, which happens
to be the 32 bit one.
For a 64 build you can specify the generator option to cmake, as in `cmake .
-G"Visual Studio 11 Win64"
Of course this means two different solutions and build folders for the 32
and 64 bit versions.
(see
http://cmake.3232098.n2.nabble.com/On-WINDOWS-Is-it-Possible-to-build-64-bit
-and-32-bit-Solutions-in-One-Go-td7292182.html)
About the warnings, I also noticed the problem recently and have created a
pull request addressing them.
https://github.com/nanomsg/nanomsg/pull/248
Please let me know if you have any suggestions to improve it.
(I also have no idea if I should have mentioned the pull request in the
mailing list also).
On 29 May 2014 06:25, Andrew Starks <andrew.starks@xxxxxxxx> wrote:
On Wednesday, May 28, 2014, Dave <Dave@xxxxxxxxxxxxxxxxxx> wrote:
I have recently downloaded .3 beta. I used CMake to create the solution
files needs and built the Win32 version without any problems. But I was
unable to get a x64 build. I get 3 succeeded and 37 failing projects. I
get lots of linker errors saying that an machine module x64 was in conflict
with a /MACHINE type of x86. This is despite the fact that I've checked
all the projects and all /MACHINE types are set to x64. Further the
solution configurations are all "x64" in the build types.
In addition I get lots of truncation warnings. All of this seems to
replicate the issues that are documented from last September and in reading
those posts it seemed like the problems were resolved. I assumed that this
fix was included in the "master" for beta .3. I hope I'm not missing
something obvious, but is my assumption incorrect. If not, what in the
world am I neglecting to do.
thanks
dave
I never got the cmake file to work because <inflammatory remarks redacted
/>.
I was able to build it using VS 2010. I made a nuget of it, as well. Later,
I'll push the nuget. If you want, I can post the project file (which should
work from the root of the repository.)
-Andrew
Other related posts:
