vs2017 win7 x64
編譯cef ，下面有cef_gtest cefclient cefsimple ceftests libcef_dll_wrapper等幾個專案
現在選 了x64 也依次看了專案屬性 聯結器 高級 目標計算機選 的是machine:x64
不過并不是所有專案都有這個屬性，有兩個編譯dll lib 的好像就沒有。
其中有個cef_gtest專案，明明已經選了release x64
編譯的時候總報
4>x64\Release\binding_test.obj : fatal error LNK1112: 模塊計算機型別“x64”與目標計算機型別“x86”沖突
4>已完成生成專案“cefclient.vcxproj”的操作 - 失敗。
類似這樣的錯誤 ，而且 有很好幾處。要怎么調才好使啊？
uj5u.com熱心網友回復：
吧vs2017中的平臺改成x64的唄uj5u.com熱心網友回復：
要x64編譯選項就要所有的工程都設定出x64來編譯uj5u.com熱心網友回復：
1>------ 已啟動全部重新生成: 專案: ZERO_CHECK, 配置: Release x64 ------1>Checking Build System
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/CMakeFiles/generate.stamp is up-to-date.
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/libcef_dll_wrapper/CMakeFiles/generate.stamp is up-to-date.
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/cefclient/CMakeFiles/generate.stamp is up-to-date.
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/cefsimple/CMakeFiles/generate.stamp is up-to-date.
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/gtest/CMakeFiles/generate.stamp is up-to-date.
1>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/ceftests/CMakeFiles/generate.stamp is up-to-date.
2>------ 已啟動全部重新生成: 專案: libcef_dll_wrapper, 配置: Release x64 ------
2>Building Custom Rule F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/libcef_dll/CMakeLists.txt
2>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/libcef_dll_wrapper/CMakeFiles/generate.stamp is up-to-date.
2>transfer_util.cc
2>cef_atomicops_x86_gcc.cc
2>cef_bind_helpers.cc
2>cef_callback_helpers.cc
2>cef_callback_internal.cc
2>cef_lock.cc
2>cef_lock_impl.cc
2>cef_logging.cc
2>cef_ref_counted.cc
2>cef_string16.cc
2>cef_thread_checker_impl.cc
2>cef_thread_collision_warner.cc
2>cef_weak_ptr.cc
2>accessibility_handler_cpptoc.cc
2>app_cpptoc.cc
2>base_ref_counted_cpptoc.cc
2>base_scoped_cpptoc.cc
2>browser_process_handler_cpptoc.cc
2>client_cpptoc.cc
2>completion_callback_cpptoc.cc
2>context_menu_handler_cpptoc.cc
2>cookie_visitor_cpptoc.cc
2>delete_cookies_callback_cpptoc.cc
2>dialog_handler_cpptoc.cc
2>display_handler_cpptoc.cc
2>domvisitor_cpptoc.cc
2>download_handler_cpptoc.cc
2>download_image_callback_cpptoc.cc
2>drag_handler_cpptoc.cc
2>end_tracing_callback_cpptoc.cc
2>find_handler_cpptoc.cc
2>focus_handler_cpptoc.cc
2>geolocation_handler_cpptoc.cc
2>get_geolocation_callback_cpptoc.cc
2>jsdialog_handler_cpptoc.cc
2>keyboard_handler_cpptoc.cc
2>life_span_handler_cpptoc.cc
2>load_handler_cpptoc.cc
2>menu_model_delegate_cpptoc.cc
2>navigation_entry_visitor_cpptoc.cc
2>pdf_print_callback_cpptoc.cc
2>print_handler_cpptoc.cc
2>read_handler_cpptoc.cc
2>register_cdm_callback_cpptoc.cc
2>render_handler_cpptoc.cc
2>render_process_handler_cpptoc.cc
2>request_context_handler_cpptoc.cc
2>request_handler_cpptoc.cc
2>resolve_callback_cpptoc.cc
2>resource_bundle_handler_cpptoc.cc
2>resource_handler_cpptoc.cc
2>response_filter_cpptoc.cc
2>run_file_dialog_callback_cpptoc.cc
2>scheme_handler_factory_cpptoc.cc
2>set_cookie_callback_cpptoc.cc
2>string_visitor_cpptoc.cc
2>task_cpptoc.cc
2>urlrequest_client_cpptoc.cc
2>v8accessor_cpptoc.cc
2>v8handler_cpptoc.cc
2>v8interceptor_cpptoc.cc
2>web_plugin_info_visitor_cpptoc.cc
2>web_plugin_unstable_callback_cpptoc.cc
2>write_handler_cpptoc.cc
2>translator_test_ref_ptr_client_child_cpptoc.cc
2>translator_test_ref_ptr_client_cpptoc.cc
2>translator_test_scoped_client_child_cpptoc.cc
2>translator_test_scoped_client_cpptoc.cc
2>browser_view_delegate_cpptoc.cc
2>button_delegate_cpptoc.cc
2>menu_button_delegate_cpptoc.cc
2>panel_delegate_cpptoc.cc
2>textfield_delegate_cpptoc.cc
2>view_delegate_cpptoc.cc
2>window_delegate_cpptoc.cc
2>auth_callback_ctocpp.cc
2>before_download_callback_ctocpp.cc
2>binary_value_ctocpp.cc
2>browser_ctocpp.cc
2>browser_host_ctocpp.cc
2>callback_ctocpp.cc
2>command_line_ctocpp.cc
2>context_menu_params_ctocpp.cc
2>cookie_manager_ctocpp.cc
2>dictionary_value_ctocpp.cc
2>domdocument_ctocpp.cc
2>domnode_ctocpp.cc
2>download_item_callback_ctocpp.cc
2>download_item_ctocpp.cc
2>drag_data_ctocpp.cc
2>file_dialog_callback_ctocpp.cc
2>frame_ctocpp.cc
2>geolocation_callback_ctocpp.cc
2>image_ctocpp.cc
2>jsdialog_callback_ctocpp.cc
2>list_value_ctocpp.cc
2>menu_model_ctocpp.cc
2>navigation_entry_ctocpp.cc
2>post_data_ctocpp.cc
2>post_data_element_ctocpp.cc
2>print_dialog_callback_ctocpp.cc
2>print_job_callback_ctocpp.cc
2>print_settings_ctocpp.cc
2>process_message_ctocpp.cc
2>request_callback_ctocpp.cc
2>request_context_ctocpp.cc
2>request_ctocpp.cc
2>resource_bundle_ctocpp.cc
2>response_ctocpp.cc
2>run_context_menu_callback_ctocpp.cc
2>scheme_registrar_ctocpp.cc
2>select_client_certificate_callback_ctocpp.cc
2>sslinfo_ctocpp.cc
2>sslstatus_ctocpp.cc
2>stream_reader_ctocpp.cc
2>stream_writer_ctocpp.cc
2>task_runner_ctocpp.cc
2>thread_ctocpp.cc
2>urlrequest_ctocpp.cc
2>v8context_ctocpp.cc
2>v8exception_ctocpp.cc
2>v8stack_frame_ctocpp.cc
2>v8stack_trace_ctocpp.cc
2>v8value_ctocpp.cc
2>value_ctocpp.cc
2>waitable_event_ctocpp.cc
2>web_plugin_info_ctocpp.cc
2>x509cert_principal_ctocpp.cc
2>x509certificate_ctocpp.cc
2>xml_reader_ctocpp.cc
2>zip_reader_ctocpp.cc
2>translator_test_ctocpp.cc
2>translator_test_ref_ptr_library_child_child_ctocpp.cc
2>translator_test_ref_ptr_library_child_ctocpp.cc
2>translator_test_ref_ptr_library_ctocpp.cc
2>translator_test_scoped_library_child_child_ctocpp.cc
2>translator_test_scoped_library_child_ctocpp.cc
2>translator_test_scoped_library_ctocpp.cc
2>box_layout_ctocpp.cc
2>browser_view_ctocpp.cc
2>button_ctocpp.cc
2>display_ctocpp.cc
2>fill_layout_ctocpp.cc
2>label_button_ctocpp.cc
2>layout_ctocpp.cc
2>menu_button_ctocpp.cc
2>panel_ctocpp.cc
2>scroll_view_ctocpp.cc
2>textfield_ctocpp.cc
2>view_ctocpp.cc
2>window_ctocpp.cc
2>cef_byte_read_handler.cc
2>cef_closure_task.cc
2>cef_message_router.cc
2>cef_resource_manager.cc
2>cef_scoped_temp_dir.cc
2>cef_stream_resource_handler.cc
2>cef_xml_object.cc
2>cef_zip_archive.cc
2>libcef_dll_wrapper.cc
2>libcef_dll_wrapper2.cc
2>cef_lock.obj : warning LNK4221: 此物件檔案未定義任何之前未定義的公共符號，因此任何耗用此庫的鏈接操作都不會使用此檔案
2>libcef_dll_wrapper.vcxproj -> F:\prj\CEF\cef_binary_3.3163.1666.g052c2d2_windows64\x64\Release\libcef_dll_wrapper.lib
2>已完成生成專案“libcef_dll_wrapper.vcxproj”的操作。
3>------ 已啟動全部重新生成: 專案: cefclient, 配置: Release x64 ------
3>Building Custom Rule F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/cefclient/CMakeLists.txt
3>CMake does not need to re-run because F:/prj/CEF/cef_binary_3.3163.1666.g052c2d2_windows64/tests/cefclient/CMakeFiles/generate.stamp is up-to-date.
3>binding_test.cc
3>browser_window.cc
3>bytes_write_handler.cc
3>client_app_delegates_browser.cc
3>client_browser.cc
3>client_handler.cc
3>client_handler_osr.cc
3>client_handler_std.cc
3>dialog_test.cc
3>drm_test.cc
3>main_context.cc
3>main_context_impl.cc
3>osr_renderer.cc
3>preferences_test.cc
3>response_filter_test.cc
3>root_window.cc
3>root_window_create.cc
3>root_window_manager.cc
3>scheme_test.cc
3>test_runner.cc
3>urlrequest_test.cc
3>window_test.cc
3>window_test_runner.cc
3>client_app_browser.cc
3>geometry_util.cc
3>main_message_loop.cc
3>main_message_loop_external_pump.cc
3>main_message_loop_std.cc
3>resource_util.cc
3>client_app_delegates_common.cc
3>scheme_test_common.cc
3>client_app.cc
3>client_app_other.cc
3>client_switches.cc
3>client_app_delegates_renderer.cc
3>client_renderer.cc
3>performance_test.cc
3>performance_test_tests.cc
3>client_app_renderer.cc
3>cefclient_win.cc
3>browser_window_osr_win.cc
3>browser_window_std_win.cc
3>main_context_impl_win.cc
3>main_message_loop_multithreaded_win.cc
3>osr_accessibility_helper.cc
3>osr_accessibility_node.cc
3>osr_accessibility_node_win.cc
3>osr_dragdrop_win.cc
3>osr_ime_handler_win.cc
3>osr_window_win.cc
3>resource_util_win_idmap.cc
3>root_window_views.cc
3>root_window_win.cc
3>temp_window_win.cc
3>views_menu_bar.cc
3>views_style.cc
3>views_window.cc
3>window_test_runner_views.cc
3>window_test_runner_win.cc
3>main_message_loop_external_pump_win.cc
3>resource_util_win.cc
3>util_win.cc
3>x64\Release\binding_test.obj : fatal error LNK1112: 模塊計算機型別“x64”與目標計算機型別“x86”沖突
3>已完成生成專案“cefclient.vcxproj”的操作 - 失敗。
========== 全部重新生成: 成功 2 個，失敗 1 個，跳過 0 個 ==========
編譯cefclient依賴libcef_dll_wrapper 后者能正常編譯輸出，但在編譯前者的時候出了問題。提示x64與x86沖突 。
明明前面也寫了ceflclient編譯的是release x64的版本 為什么在binding_test.obj 這里提示出錯呢
怎么認為目標肇機型別是x86呢。 cefclient的設定里的目標計算機明明寫的是machine:x64
其它地方也沒看到有什么關于x64 x86的設定。
問題在哪里呢？
uj5u.com熱心網友回復：
查看對應到了工程屬性中，C/C++的CPU編譯型別等
uj5u.com熱心網友回復：
在哪里？沒看到你說的選項啊。我看和編譯的機器架構相關的就這幾個地方：專案屬性-》聯結器-》高級-》目標計算機 MachineX64(/Machine:x64)專案屬性配置-》庫管理-》1.常規-》目標計算機-》MachineX64 2.所有選項-》附加選項：%(AdditionalOptions) /machine:X64 沒有其它地方了吧。你說的 工程屬性中，C/C++的CPU編譯型別等 是指的哪里？ 我確定 是查看了每個工程 的以上專案都是x64
uj5u.com熱心網友回復：
重建所有uj5u.com熱心網友回復：
重建了的啊不知道 為啥 還有這樣的提示
uj5u.com熱心網友回復：
IDE的專案檔案中，在binding_test.cpp檔案上或其所在專案上點滑鼠右鍵，找相關設定，設定其目標計算機型別為x64 ？uj5u.com熱心網友回復：
http://blog.csdn.net/tfy1028/article/details/8660823uj5u.com熱心網友回復：
回答的什么玩意
轉載請註明出處，本文鏈接：https://www.uj5u.com/gongcheng/10486.html
標籤：基礎類