Using jam/VS to build project gives Fatal Error LNK1112
I am attempting to build autoknit on my 64-bit Windows 10 machine with Visual Studio 2017 Community installed on it. I have followed the instructions in the README for the project including cloning the repositories, but when I try to run jam from the "x64 Native Tools Command Prompt for VS 2017" console, I am met with the following error:
...found 186 target(s)...
...updating 3 target(s)...
Link distschedule.exe
objsScheduleCost.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distschedule.exe objsStitch.obj objsScheduleCost.obj objsschedule.obj objsembed_DAG.obj objsplan_transfers.obj objsplan_transfers-draw_beds.obj objsplan_transfers-run_transfers.obj objsplan_transfers-best_collapse.obj objsplan_transfers-best_shift.obj objsplan_transfers-best_expand.obj objsplan_transfers-minimize_winding.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distschedule.exe ...
Link disttest_flatten.exe
distak-link_chains.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:disttest_flatten.exe objstest_flatten.obj distak-link_chains.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link disttest_flatten.exe ...
Link distinterface.exe
msvcprt.lib(MSVCP140.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distinterface.exe distak-trace_graph.obj distak-peel_slice-euclidean.obj distak-trim_model.obj distak-embedded_path.obj distak-build_next_active_chains.obj distak-link_chains.obj distak-extract_level_chains.obj distak-find_first_active_chains.obj distak-sample_chain.obj distInterface.obj distinit.obj distload_obj.obj distak-load_constraints.obj distak-embed_constraints.obj distak-interpolate_values.obj objskitkit.obj objskitkit-SDL2.obj objskitButton.obj objskitLoad.obj objskitMeshBuffer.obj objskitBoneAnimation.obj objskitGLProgram.obj objskitpath.obj objskitload_save_png.obj objskitgl_shims.obj objsStitch.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distinterface.exe ...
...failed updating 3 target(s)...
It both says that x64 machine type conflicts with x86 target type, and that x86 machine type conflicts with x64 target type. This seems illogical, and makes it seem as though the compiler detects a x64 machine but code meant for x86, but also switches to detecting a x86 machine with code meant for x64. I cannot make heads or tails of this, nor figure out how to resolve it. This is a git repository being built using jam and the VS compiler; as far as I can tell, it is not a proper VS project.
c++ build linker visual-studio-2017 jam
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
add a comment |
I am attempting to build autoknit on my 64-bit Windows 10 machine with Visual Studio 2017 Community installed on it. I have followed the instructions in the README for the project including cloning the repositories, but when I try to run jam from the "x64 Native Tools Command Prompt for VS 2017" console, I am met with the following error:
...found 186 target(s)...
...updating 3 target(s)...
Link distschedule.exe
objsScheduleCost.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distschedule.exe objsStitch.obj objsScheduleCost.obj objsschedule.obj objsembed_DAG.obj objsplan_transfers.obj objsplan_transfers-draw_beds.obj objsplan_transfers-run_transfers.obj objsplan_transfers-best_collapse.obj objsplan_transfers-best_shift.obj objsplan_transfers-best_expand.obj objsplan_transfers-minimize_winding.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distschedule.exe ...
Link disttest_flatten.exe
distak-link_chains.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:disttest_flatten.exe objstest_flatten.obj distak-link_chains.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link disttest_flatten.exe ...
Link distinterface.exe
msvcprt.lib(MSVCP140.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distinterface.exe distak-trace_graph.obj distak-peel_slice-euclidean.obj distak-trim_model.obj distak-embedded_path.obj distak-build_next_active_chains.obj distak-link_chains.obj distak-extract_level_chains.obj distak-find_first_active_chains.obj distak-sample_chain.obj distInterface.obj distinit.obj distload_obj.obj distak-load_constraints.obj distak-embed_constraints.obj distak-interpolate_values.obj objskitkit.obj objskitkit-SDL2.obj objskitButton.obj objskitLoad.obj objskitMeshBuffer.obj objskitBoneAnimation.obj objskitGLProgram.obj objskitpath.obj objskitload_save_png.obj objskitgl_shims.obj objsStitch.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distinterface.exe ...
...failed updating 3 target(s)...
It both says that x64 machine type conflicts with x86 target type, and that x86 machine type conflicts with x64 target type. This seems illogical, and makes it seem as though the compiler detects a x64 machine but code meant for x86, but also switches to detecting a x86 machine with code meant for x64. I cannot make heads or tails of this, nor figure out how to resolve it. This is a git repository being built using jam and the VS compiler; as far as I can tell, it is not a proper VS project.
c++ build linker visual-studio-2017 jam
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
add a comment |
I am attempting to build autoknit on my 64-bit Windows 10 machine with Visual Studio 2017 Community installed on it. I have followed the instructions in the README for the project including cloning the repositories, but when I try to run jam from the "x64 Native Tools Command Prompt for VS 2017" console, I am met with the following error:
...found 186 target(s)...
...updating 3 target(s)...
Link distschedule.exe
objsScheduleCost.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distschedule.exe objsStitch.obj objsScheduleCost.obj objsschedule.obj objsembed_DAG.obj objsplan_transfers.obj objsplan_transfers-draw_beds.obj objsplan_transfers-run_transfers.obj objsplan_transfers-best_collapse.obj objsplan_transfers-best_shift.obj objsplan_transfers-best_expand.obj objsplan_transfers-minimize_winding.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distschedule.exe ...
Link disttest_flatten.exe
distak-link_chains.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:disttest_flatten.exe objstest_flatten.obj distak-link_chains.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link disttest_flatten.exe ...
Link distinterface.exe
msvcprt.lib(MSVCP140.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distinterface.exe distak-trace_graph.obj distak-peel_slice-euclidean.obj distak-trim_model.obj distak-embedded_path.obj distak-build_next_active_chains.obj distak-link_chains.obj distak-extract_level_chains.obj distak-find_first_active_chains.obj distak-sample_chain.obj distInterface.obj distinit.obj distload_obj.obj distak-load_constraints.obj distak-embed_constraints.obj distak-interpolate_values.obj objskitkit.obj objskitkit-SDL2.obj objskitButton.obj objskitLoad.obj objskitMeshBuffer.obj objskitBoneAnimation.obj objskitGLProgram.obj objskitpath.obj objskitload_save_png.obj objskitgl_shims.obj objsStitch.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distinterface.exe ...
...failed updating 3 target(s)...
It both says that x64 machine type conflicts with x86 target type, and that x86 machine type conflicts with x64 target type. This seems illogical, and makes it seem as though the compiler detects a x64 machine but code meant for x86, but also switches to detecting a x86 machine with code meant for x64. I cannot make heads or tails of this, nor figure out how to resolve it. This is a git repository being built using jam and the VS compiler; as far as I can tell, it is not a proper VS project.
c++ build linker visual-studio-2017 jam
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
I am attempting to build autoknit on my 64-bit Windows 10 machine with Visual Studio 2017 Community installed on it. I have followed the instructions in the README for the project including cloning the repositories, but when I try to run jam from the "x64 Native Tools Command Prompt for VS 2017" console, I am met with the following error:
...found 186 target(s)...
...updating 3 target(s)...
Link distschedule.exe
objsScheduleCost.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distschedule.exe objsStitch.obj objsScheduleCost.obj objsschedule.obj objsembed_DAG.obj objsplan_transfers.obj objsplan_transfers-draw_beds.obj objsplan_transfers-run_transfers.obj objsplan_transfers-best_collapse.obj objsplan_transfers-best_shift.obj objsplan_transfers-best_expand.obj objsplan_transfers-minimize_winding.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distschedule.exe ...
Link disttest_flatten.exe
distak-link_chains.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:disttest_flatten.exe objstest_flatten.obj distak-link_chains.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link disttest_flatten.exe ...
Link distinterface.exe
msvcprt.lib(MSVCP140.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
link /nologo /nologo /SUBSYSTEM:CONSOLE /LIBPATH:kit-libs-win/out/lib /LIBPATH:kit-libs-win/out/libpng /LIBPATH:kit-libs-win/out/zlib /out:distinterface.exe distak-trace_graph.obj distak-peel_slice-euclidean.obj distak-trim_model.obj distak-embedded_path.obj distak-build_next_active_chains.obj distak-link_chains.obj distak-extract_level_chains.obj distak-find_first_active_chains.obj distak-sample_chain.obj distInterface.obj distinit.obj distload_obj.obj distak-load_constraints.obj distak-embed_constraints.obj distak-interpolate_values.obj objskitkit.obj objskitkit-SDL2.obj objskitButton.obj objskitLoad.obj objskitMeshBuffer.obj objskitBoneAnimation.obj objskitGLProgram.obj objskitpath.obj objskitload_save_png.obj objskitgl_shims.obj objsStitch.obj SDL2main.lib SDL2.lib OpenGL32.lib libpng.lib zlib.lib
...failed Link distinterface.exe ...
...failed updating 3 target(s)...
It both says that x64 machine type conflicts with x86 target type, and that x86 machine type conflicts with x64 target type. This seems illogical, and makes it seem as though the compiler detects a x64 machine but code meant for x86, but also switches to detecting a x86 machine with code meant for x64. I cannot make heads or tails of this, nor figure out how to resolve it. This is a git repository being built using jam and the VS compiler; as far as I can tell, it is not a proper VS project.
c++ build linker visual-studio-2017 jam
c++ build linker visual-studio-2017 jam
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
asked Nov 13 '18 at 16:49
user2649681user2649681
166111
166111
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53285845%2fusing-jam-vs-to-build-project-gives-fatal-error-lnk1112%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53285845%2fusing-jam-vs-to-build-project-gives-fatal-error-lnk1112%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
