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

Unable to build on Visual Studo 2015 x64 #472

Closed
Yoshi325 opened this Issue Oct 12, 2015 · 9 comments

Comments

Projects
None yet
2 participants
@Yoshi325

Yoshi325 commented Oct 12, 2015

Following the documented steps to build nanomsg on Windows, the build fails.

CMake appears to create the Solution and Project files without issue, but msbuild does not seem to be able to build the generated Solution/Project files.

> "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x64

> cd nanomsg

> cmake . -G "Visual Studio 14 Win64"
-- The C compiler identification is unknown
-- Check for working C compiler using: Visual Studio 14 2015 Win64
-- Check for working C compiler using: Visual Studio 14 2015 Win64 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: ./nanomsg

> msbuild /target:Build /property:Configuration=Release nanomsg.sln
Microsoft (R) Build Engine version 14.0.23107.0
Copyright (C) Microsoft Corporation. All rights reserved.

Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 10/12/2015 6:33:57 PM.
Project ".\nanomsg\nanomsg.sln" on node 1 (Build target(s)).
ValidateSolutionConfiguration:
  Building solution configuration "Release|X64".
ValidateProjects:
  The project "INSTALL" is not selected for building in solution configuration "Release|x64".
  The project "PACKAGE" is not selected for building in solution configuration "Release|x64".
  The project "RUN_TESTS" is not selected for building in solution configuration "Release|x64".
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.Net.CoreRuntime.targets (68,11)" does not exist in the project, and will be ignored.
The target "_GeneratePrisForPortableLibraries" listed in a BeforeTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.Net.CoreRuntime.targets (177,11)" does not exist in the project, and will be ignored.
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.NetNative.targets (126,11)" does not exist in the project, and will be ignored.
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.NetNative.targets (174,11)" does not exist in the project, and will be ignored.
The target "BeforeGenerateProjectPriFile" listed in a BeforeTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets (149,61)" does not exist in the project, and will be ignored.
Project ".\nanomsg\nanomsg.sln" (1) is building ".\nanomsg\ALL_BUILD.vcxproj.metaproj" (2) on node 1 (default targets).
Project ".\nanomsg\ALL_BUILD.vcxproj.metaproj" (2) is building ".\nanomsg\ZERO_CHECK.vcxproj" (3) on node 1 (default targets).
InitializeBuildStatus:
  Creating "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
  Checking Build System
  CMake does not need to re-run because ./nanomsg/CMakeFiles/generate.stamp is up-to-date.
  CMake does not need to re-run because ./nanomsg/src/CMakeFiles/generate.stamp is up-to-date.
FinalizeBuildStatus:
  Deleting file "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild".
  Touching "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\ZERO_CHECK.lastbuildstate".
Done Building Project ".\nanomsg\ZERO_CHECK.vcxproj" (default targets).
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.Net.CoreRuntime.targets (68,11)" does not exist in the project, and will be ignored.
The target "_GeneratePrisForPortableLibraries" listed in a BeforeTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.Net.CoreRuntime.targets (177,11)" does not exist in the project, and will be ignored.
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.NetNative.targets (126,11)" does not exist in the project, and will be ignored.
The target "AfterGenerateAppxManifest" listed in an AfterTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\.NetNative\Microsoft.NetNative.targets (174,11)" does not exist in the project, and will be ignored.
The target "BeforeGenerateProjectPriFile" listed in a BeforeTargets attribute at "C:\Program Files (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets (149,61)" does not exist in the project, and will be ignored.
Project ".\nanomsg\ALL_BUILD.vcxproj.metaproj" (2) is building ".\nanomsg\block.vcxproj.metaproj" (4) on node 1 (default targets).
Project ".\nanomsg\block.vcxproj.metaproj" (4) is building ".\nanomsg\src\nanomsg.vcxproj.metaproj" (5) on node 1 (default targets).
Project ".\nanomsg\src\nanomsg.vcxproj.metaproj" (5) is building ".\nanomsg\src\nanomsg.vcxproj" (6) on node 1 (default targets).
InitializeBuildStatus:
  Touching "nanomsg.dir\Release\nanomsg.tlog\unsuccessfulbuild".
CustomBuild:
  All outputs are up-to-date.
ClCompile:
  All outputs are up-to-date.
Link:
  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\link.exe /ERRORREPORT:QUEUE /OUT:".\nanomsg\Release\nanomsg.dll" /INCREMENTAL /NOLOGO "-lws2_32.lib" "-lMswsock.lib" "-lAdvapi32.lib" /MANIFEST /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /manifest:embed /PDB:"./nanomsg/Release/nanomsg.pdb" /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:"./nanomsg/Release/nanomsg.lib" /MACHINE:X64 /DLL nanomsg.dir\Release\ep.obj
  nanomsg.dir\Release\epbase.obj
  nanomsg.dir\Release\global.obj
  nanomsg.dir\Release\pipe.obj
  nanomsg.dir\Release\poll.obj
  nanomsg.dir\Release\sock.obj
  nanomsg.dir\Release\sockbase.obj
  nanomsg.dir\Release\symbol.obj
  nanomsg.dir\Release\ctx.obj
  nanomsg.dir\Release\fsm.obj
  nanomsg.dir\Release\poller.obj
  nanomsg.dir\Release\pool.obj
  nanomsg.dir\Release\timer.obj
  nanomsg.dir\Release\timerset.obj
  nanomsg.dir\Release\usock.obj
  nanomsg.dir\Release\worker.obj
  nanomsg.dir\Release\alloc.obj
  nanomsg.dir\Release\atomic.obj
  nanomsg.dir\Release\chunk.obj
  nanomsg.dir\Release\chunkref.obj
  nanomsg.dir\Release\clock.obj
  nanomsg.dir\Release\closefd.obj
  nanomsg.dir\Release\efd.obj
  nanomsg.dir\Release\err.obj
  nanomsg.dir\Release\glock.obj
  nanomsg.dir\Release\hash.obj
  nanomsg.dir\Release\list.obj
  nanomsg.dir\Release\msg.obj
  nanomsg.dir\Release\mutex.obj
  nanomsg.dir\Release\queue.obj
  nanomsg.dir\Release\random.obj
  nanomsg.dir\Release\sem.obj
  nanomsg.dir\Release\sleep.obj
  nanomsg.dir\Release\thread.obj
  nanomsg.dir\Release\wire.obj
  nanomsg.dir\Release\device.obj
  nanomsg.dir\Release\tcpmuxd.obj
  nanomsg.dir\Release\dist.obj
  nanomsg.dir\Release\excl.obj
  nanomsg.dir\Release\fq.obj
  nanomsg.dir\Release\lb.obj
  nanomsg.dir\Release\priolist.obj
  nanomsg.dir\Release\bus.obj
  nanomsg.dir\Release\xbus.obj
  nanomsg.dir\Release\push.obj
  nanomsg.dir\Release\pull.obj
  nanomsg.dir\Release\xpull.obj
  nanomsg.dir\Release\xpush.obj
  nanomsg.dir\Release\pair.obj
  nanomsg.dir\Release\xpair.obj
  nanomsg.dir\Release\pub.obj
  nanomsg.dir\Release\sub.obj
  nanomsg.dir\Release\trie.obj
  nanomsg.dir\Release\xpub.obj
  nanomsg.dir\Release\xsub.obj
  nanomsg.dir\Release\req.obj
  nanomsg.dir\Release\rep.obj
  nanomsg.dir\Release\task.obj
  nanomsg.dir\Release\xrep.obj
  nanomsg.dir\Release\xreq.obj
  nanomsg.dir\Release\respondent.obj
  nanomsg.dir\Release\surveyor.obj
  nanomsg.dir\Release\xrespondent.obj
  nanomsg.dir\Release\xsurveyor.obj
  nanomsg.dir\Release\backoff.obj
  nanomsg.dir\Release\dns.obj
  nanomsg.dir\Release\iface.obj
  nanomsg.dir\Release\literal.obj
  nanomsg.dir\Release\port.obj
  nanomsg.dir\Release\streamhdr.obj
  nanomsg.dir\Release\base64.obj
  nanomsg.dir\Release\binproc.obj
  nanomsg.dir\Release\cinproc.obj
  nanomsg.dir\Release\inproc.obj
  nanomsg.dir\Release\ins.obj
  nanomsg.dir\Release\msgqueue.obj
  nanomsg.dir\Release\sinproc.obj
  nanomsg.dir\Release\aipc.obj
  nanomsg.dir\Release\bipc.obj
  nanomsg.dir\Release\cipc.obj
  nanomsg.dir\Release\ipc.obj
  nanomsg.dir\Release\sipc.obj
  nanomsg.dir\Release\atcp.obj
  nanomsg.dir\Release\btcp.obj
  nanomsg.dir\Release\ctcp.obj
  nanomsg.dir\Release\stcp.obj
  nanomsg.dir\Release\tcp.obj
  nanomsg.dir\Release\atcpmux.obj
  nanomsg.dir\Release\btcpmux.obj
  nanomsg.dir\Release\ctcpmux.obj
  nanomsg.dir\Release\stcpmux.obj
  nanomsg.dir\Release\tcpmux.obj
  nanomsg.dir\Release\aws.obj
  nanomsg.dir\Release\bws.obj
  nanomsg.dir\Release\cws.obj
  nanomsg.dir\Release\sws.obj
  nanomsg.dir\Release\ws.obj
  nanomsg.dir\Release\ws_handshake.obj
  nanomsg.dir\Release\sha1.obj
LINK : warning LNK4044: unrecognized option '/lws2_32.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]
LINK : warning LNK4044: unrecognized option '/lMswsock.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]
LINK : warning LNK4044: unrecognized option '/lAdvapi32.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]
     Creating library ./nanomsg/Release/nanomsg.lib and object ./nanomsg/Release/nanomsg.exp

LINK : fatal error LNK1000: Internal error during IMAGE::Pass1 [.\nanomsg\src\nanomsg.vcxproj]

    Version 14.00.23026.0

    ExceptionCode            = C0000005
    ExceptionFlags           = 00000000
    ExceptionAddress         = 00007FF7EDE3CD27 (00007FF7EDDD0000) "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\link.exe"
    NumberParameters         = 00000002
    ExceptionInformation[ 0] = 0000000000000000
    ExceptionInformation[ 1] = 0000000000000008

  CONTEXT:
    Rax    = 0000000000000000  R8     = 0000000000000000
    Rbx    = 0000000000000000  R9     = 000000000000005A
    Rcx    = 77763717EAE10000  R10    = 000000E75FAA46C0
    Rdx    = 000000000000001E  R11    = 000000E75DA0D170
    Rsp    = 000000E75DA0D5F0  R12    = 0000000000000000
    Rbp    = 000000E75DA0D6F0  E13    = 000000E75FB5FEF8
    Rsi    = 000000E75FA7E0BE  R14    = 0000000000000000
    Rdi    = 0000000200400000  R15    = 0000000000000080
    Rip    = 00007FF7EDE3CD27  EFlags = 0000000000010246
    SegCs  = 0000000000000033  SegDs  = 000000000000002B
    SegSs  = 000000000000002B  SegEs  = 000000000000002B
    SegFs  = 0000000000000053  SegGs  = 000000000000002B
    Dr0    = 0000000000000000  Dr3    = 0000000000000000
    Dr1    = 0000000000000000  Dr6    = 0000000000000000
    Dr2    = 0000000000000000  Dr7    = 0000000000000000
Done Building Project ".\nanomsg\src\nanomsg.vcxproj" (default targets) -- FAILED.
Done Building Project ".\nanomsg\src\nanomsg.vcxproj.metaproj" (default targets) -- FAILED.
Done Building Project ".\nanomsg\block.vcxproj.metaproj" (default targets) -- FAILED.
Done Building Project ".\nanomsg\ALL_BUILD.vcxproj.metaproj" (default targets) -- FAILED.
Done Building Project ".\nanomsg\nanomsg.sln" (Build target(s)) -- FAILED.

Build FAILED.

".\nanomsg\nanomsg.sln" (Build target) (1) ->
".\nanomsg\ALL_BUILD.vcxproj.metaproj" (default target) (2) ->
".\nanomsg\block.vcxproj.metaproj" (default target) (4) ->
".\nanomsg\src\nanomsg.vcxproj.metaproj" (default target) (5) ->
".\nanomsg\src\nanomsg.vcxproj" (default target) (6) ->
(Link target) -> 
  LINK : warning LNK4044: unrecognized option '/lws2_32.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]
  LINK : warning LNK4044: unrecognized option '/lMswsock.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]
  LINK : warning LNK4044: unrecognized option '/lAdvapi32.lib'; ignored [.\nanomsg\src\nanomsg.vcxproj]


".\nanomsg\nanomsg.sln" (Build target) (1) ->
".\nanomsg\ALL_BUILD.vcxproj.metaproj" (default target) (2) ->
".\nanomsg\block.vcxproj.metaproj" (default target) (4) ->
".\nanomsg\src\nanomsg.vcxproj.metaproj" (default target) (5) ->
".\nanomsg\src\nanomsg.vcxproj" (default target) (6) ->
(Link target) -> 
  LINK : fatal error LNK1000: Internal error during IMAGE::Pass1 [.\nanomsg\src\nanomsg.vcxproj]

    3 Warning(s)
    1 Error(s)

Time Elapsed 00:00:02.71


@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Oct 21, 2015

Contributor

This looks like a problem with your build environment. Link errors etc. I don't know anything about the Windows tooling here; what I can say is that we build regularly on AppVeyor and don't see these problems. I'm not sure VS14 is supported though -- apparently new versions of cmake support VS14, but I've not had a chance to try it. What version of cmake are you using?

You'll note that cmake complained above: "The C compiler identification is unknown"

So it really is just guessing (and probably badly) about how to produce programs.

Contributor

gdamore commented Oct 21, 2015

This looks like a problem with your build environment. Link errors etc. I don't know anything about the Windows tooling here; what I can say is that we build regularly on AppVeyor and don't see these problems. I'm not sure VS14 is supported though -- apparently new versions of cmake support VS14, but I've not had a chance to try it. What version of cmake are you using?

You'll note that cmake complained above: "The C compiler identification is unknown"

So it really is just guessing (and probably badly) about how to produce programs.

@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Oct 22, 2015

Contributor

You need to update your cmake. I've verified that we can build on VS14 on AppVeyor.:

Make suite maintained and supported by Kitware (kitware.com/cmake).
cmake ..
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler using: Visual Studio 14 2015
-- Check for working C compiler using: Visual Studio 14 2015 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/projects/nanomsg/build
cmake --build .

Contributor

gdamore commented Oct 22, 2015

You need to update your cmake. I've verified that we can build on VS14 on AppVeyor.:

Make suite maintained and supported by Kitware (kitware.com/cmake).
cmake ..
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler using: Visual Studio 14 2015
-- Check for working C compiler using: Visual Studio 14 2015 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/projects/nanomsg/build
cmake --build .

@gdamore gdamore closed this Oct 22, 2015

@Yoshi325

This comment has been minimized.

Show comment
Hide comment
@Yoshi325

Yoshi325 Nov 9, 2015

  • cmake-3.4.0-rc3-win32-x86
  • nanomsg-0.7-beta
  • Microsoft Visual Studio Community 2015 Version 14.0.23107.0

Updating cmake resolved "The C compiler identification is unknown" error, but did not resolve the LNK1000 error.

Any input on how I can resolve them?

Yoshi325 commented Nov 9, 2015

  • cmake-3.4.0-rc3-win32-x86
  • nanomsg-0.7-beta
  • Microsoft Visual Studio Community 2015 Version 14.0.23107.0

Updating cmake resolved "The C compiler identification is unknown" error, but did not resolve the LNK1000 error.

Any input on how I can resolve them?

@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Nov 9, 2015

Contributor

Microsoft says this: https://msdn.microsoft.com/en-us/library/89cx16e6.aspx

Specifically,

You may get this error if you mix standard header files (for example, dos.h) and your own files. #include the standard headers first, followed by your own header files.

I've not looked into this in any depth, as I lack the necessary environment to do so. But maybe this will give you a hint. If you figure out, please do let us know.

Contributor

gdamore commented Nov 9, 2015

Microsoft says this: https://msdn.microsoft.com/en-us/library/89cx16e6.aspx

Specifically,

You may get this error if you mix standard header files (for example, dos.h) and your own files. #include the standard headers first, followed by your own header files.

I've not looked into this in any depth, as I lack the necessary environment to do so. But maybe this will give you a hint. If you figure out, please do let us know.

@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Nov 9, 2015

Contributor

Oh, and there is this, which suggests it may be a bug in the compilers themselves:

https://support.microsoft.com/en-us/kb/826326

Contributor

gdamore commented Nov 9, 2015

Oh, and there is this, which suggests it may be a bug in the compilers themselves:

https://support.microsoft.com/en-us/kb/826326

@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Nov 9, 2015

Contributor

And more info:
http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage

Again, this looks like a problem with the Microsoft linker, not with our code.

Contributor

gdamore commented Nov 9, 2015

And more info:
http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage

Again, this looks like a problem with the Microsoft linker, not with our code.

@Yoshi325

This comment has been minimized.

Show comment
Hide comment
@Yoshi325

Yoshi325 Nov 10, 2015

Unfortunately all the solutions I can find along those lines are for older versions of the OS, Linker, or Visual Studio.

For example, https://support.microsoft.com/en-us/kb/826326 has this:

Article ID: 826326 - Last Review: 10/25/2005 18:30:00 - Revision: 1.3

Applies to
Microsoft Visual C++ .NET 2002 Standard Edition

And http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage has this:

I am trying to recompile solution file for memcached project on Windows 7 64 bit with Visual Studio 2008 and got the following error:

As I've gone further and further down the google rabbit hole, all I've been able to find are resolutions for old product versions.

Can you share any further details about the AppVeyor VS14 configuration you were able to compile it on?

Yoshi325 commented Nov 10, 2015

Unfortunately all the solutions I can find along those lines are for older versions of the OS, Linker, or Visual Studio.

For example, https://support.microsoft.com/en-us/kb/826326 has this:

Article ID: 826326 - Last Review: 10/25/2005 18:30:00 - Revision: 1.3

Applies to
Microsoft Visual C++ .NET 2002 Standard Edition

And http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage has this:

I am trying to recompile solution file for memcached project on Windows 7 64 bit with Visual Studio 2008 and got the following error:

As I've gone further and further down the google rabbit hole, all I've been able to find are resolutions for old product versions.

Can you share any further details about the AppVeyor VS14 configuration you were able to compile it on?

@gdamore

This comment has been minimized.

Show comment
Hide comment
@gdamore

gdamore Nov 10, 2015

Contributor

You can check appveyors website. There is also a .appveyor.yml file in the repo I think.

Sent from my iPhone

On Nov 10, 2015, at 2:03 PM, Charles Y. notifications@github.com wrote:

Unfortunately all the solutions I can find along those lines are for older versions of the OS, Linker, or Visual Studio.

For example, https://support.microsoft.com/en-us/kb/826326 has this:

Article ID: 826326 - Last Review: 10/25/2005 18:30:00 - Revision: 1.3

Applies to
Microsoft Visual C++ .NET 2002 Standard Edition
And http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage has this:

I am trying to recompile solution file for memcached project on Windows 7 64 bit with Visual Studio 2008 and got the following error:
As I've gone further and further down the google rabbit hole, all I've been able to find are resolutions for old product versions.

Can you share any further details about the AppVeyor VS14 configuration you were able to compile it on?


Reply to this email directly or view it on GitHub.

Contributor

gdamore commented Nov 10, 2015

You can check appveyors website. There is also a .appveyor.yml file in the repo I think.

Sent from my iPhone

On Nov 10, 2015, at 2:03 PM, Charles Y. notifications@github.com wrote:

Unfortunately all the solutions I can find along those lines are for older versions of the OS, Linker, or Visual Studio.

For example, https://support.microsoft.com/en-us/kb/826326 has this:

Article ID: 826326 - Last Review: 10/25/2005 18:30:00 - Revision: 1.3

Applies to
Microsoft Visual C++ .NET 2002 Standard Edition
And http://stackoverflow.com/questions/2001289/how-to-resolve-fatal-error-lnk1000-internal-error-during-incrbuildimage has this:

I am trying to recompile solution file for memcached project on Windows 7 64 bit with Visual Studio 2008 and got the following error:
As I've gone further and further down the google rabbit hole, all I've been able to find are resolutions for old product versions.

Can you share any further details about the AppVeyor VS14 configuration you were able to compile it on?


Reply to this email directly or view it on GitHub.

@Yoshi325

This comment has been minimized.

Show comment
Hide comment
@Yoshi325

Yoshi325 Nov 11, 2015

I can't seem to locate the .appveyor.yml file.

I will try running the build again and compare it to the recent builds on AppVeyor.

A couple of interesting notes:

Environment: GENERATOR=Visual Studio 11 2012, VS_VERSION=11.0
cmake --version
cmake version 3.3.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
cmake ..
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler using: Visual Studio 14 2015

It seems that AppVeyor and CMake don't line up, but it still builds fine.

Also, AppVeyor addes this step (which isn't noted in the README):

call "C:/Program Files (x86)/Microsoft Visual Studio %VS_VERSION%/Common7/Tools/vsvars32.bat"

Yoshi325 commented Nov 11, 2015

I can't seem to locate the .appveyor.yml file.

I will try running the build again and compare it to the recent builds on AppVeyor.

A couple of interesting notes:

Environment: GENERATOR=Visual Studio 11 2012, VS_VERSION=11.0
cmake --version
cmake version 3.3.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
cmake ..
-- Building for: Visual Studio 14 2015
-- The C compiler identification is MSVC 19.0.23026.0
-- Check for working C compiler using: Visual Studio 14 2015

It seems that AppVeyor and CMake don't line up, but it still builds fine.

Also, AppVeyor addes this step (which isn't noted in the README):

call "C:/Program Files (x86)/Microsoft Visual Studio %VS_VERSION%/Common7/Tools/vsvars32.bat"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment