久久久久久久av_日韩在线中文_看一级毛片视频_日本精品二区_成人深夜福利视频_武道仙尊动漫在线观看

        <bdo id='Sf6vv'></bdo><ul id='Sf6vv'></ul>
        <tfoot id='Sf6vv'></tfoot>
        <i id='Sf6vv'><tr id='Sf6vv'><dt id='Sf6vv'><q id='Sf6vv'><span id='Sf6vv'><b id='Sf6vv'><form id='Sf6vv'><ins id='Sf6vv'></ins><ul id='Sf6vv'></ul><sub id='Sf6vv'></sub></form><legend id='Sf6vv'></legend><bdo id='Sf6vv'><pre id='Sf6vv'><center id='Sf6vv'></center></pre></bdo></b><th id='Sf6vv'></th></span></q></dt></tr></i><div class="qwawimqqmiuu" id='Sf6vv'><tfoot id='Sf6vv'></tfoot><dl id='Sf6vv'><fieldset id='Sf6vv'></fieldset></dl></div>

      1. <legend id='Sf6vv'><style id='Sf6vv'><dir id='Sf6vv'><q id='Sf6vv'></q></dir></style></legend>

      2. <small id='Sf6vv'></small><noframes id='Sf6vv'>

        如何在 Visual Studio Code 中包含編譯器標志?

        How to include compiler flags in Visual Studio Code?(如何在 Visual Studio Code 中包含編譯器標志?)

        <small id='xdehd'></small><noframes id='xdehd'>

        <legend id='xdehd'><style id='xdehd'><dir id='xdehd'><q id='xdehd'></q></dir></style></legend>

            <tbody id='xdehd'></tbody>
          <i id='xdehd'><tr id='xdehd'><dt id='xdehd'><q id='xdehd'><span id='xdehd'><b id='xdehd'><form id='xdehd'><ins id='xdehd'></ins><ul id='xdehd'></ul><sub id='xdehd'></sub></form><legend id='xdehd'></legend><bdo id='xdehd'><pre id='xdehd'><center id='xdehd'></center></pre></bdo></b><th id='xdehd'></th></span></q></dt></tr></i><div class="qwawimqqmiuu" id='xdehd'><tfoot id='xdehd'></tfoot><dl id='xdehd'><fieldset id='xdehd'></fieldset></dl></div>
        • <tfoot id='xdehd'></tfoot>
                • <bdo id='xdehd'></bdo><ul id='xdehd'></ul>

                • 本文介紹了如何在 Visual Studio Code 中包含編譯器標志?的處理方法,對大家解決問題具有一定的參考價值,需要的朋友們下面隨著小編來一起學習吧!

                  問題描述

                  我有一個程序,我試圖在使用 fftw 函數的 Visual Studio Code 調試器中運行該程序.它用命令編譯

                  I have a program that I am trying to run in the Visual Studio Code debugger that uses fftw functions. It compiles with the command

                  g++ dimer.cpp -std=c++11 -lfftw3 
                  

                  在我電腦上的終端上,沒有抱怨未定義的引用.但是,在生成 launch.json 文件后,我的程序會抱怨 fftw 庫函數和 -std=c++14 編譯器標志.

                  on the terminal on my computer without complaining about undefined references. However, after generating a launch.json file, my program complains about fftw library functions and about the -std=c++14 compiler flag.

                  我相信它只需要 -std=c++11-lfftw3 的額外標志使 Visual Studio Code 中的調試器正常工作.我正在使用 Microsoft 的 C/C++ 擴展和 Code Runner 擴展.

                  I believe that it needs just the extra flags of -std=c++11 and -lfftw3 for the debugger in Visual Studio Code to work. I am using Microsoft's C/C++ extension and the Code Runner extension.

                  我正在嘗試將 Mathematica 代碼文檔轉換為 C++.

                  I am trying to transform a Mathematica document of code into c++.

                  以下是我從輸出中得到的錯誤.

                  Below are the errors I get from the output.

                  Executing task: /usr/bin/g++ -g /home/msammartino/Documents/twochain/dimer.cpp -o /home/msammartino/Documents/twochain/dimer <
                  
                  In file included from /usr/include/armadillo:54:0,
                               from /home/msammartino/Documents/twochain/dimer.cpp:6:
                  /usr/include/armadillo_bits/compiler_setup.hpp:530:108: note: #pragma message: NOTE: suggest to enable C++14 mode for faster code; add -std=c++14 to compiler flags
                   #pragma message ("NOTE: suggest to enable C++14 mode for faster code; add -std=c++14 to compiler flags")
                                                                                                                          ^
                  /tmp/ccgb7Xsv.o: In function `r2r_dsine_fftw_forward_dimer(int, double*, double*, Eigen::Matrix<double, 2, 2, 0, 2, 2> (&) [2048], Eigen::Matrix<double, 2, 2, 0, 2, 2> (&) [2048])':
                  /home/msammartino/Documents/twochain/dimer.cpp:99: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:100: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:101: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:102: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:103: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:104: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:105: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:106: undefined reference to `fftw_execute'
                  /tmp/ccgb7Xsv.o: In function `r2r_dsine_fftw_backward_dimer(int, double*, double*, Eigen::Matrix<double, 2, 2, 0, 2, 2> (&) [2048], Eigen::Matrix<double, 2, 2, 0, 2, 2> (&) [2048])':
                  /home/msammartino/Documents/twochain/dimer.cpp:166: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:167: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:168: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:169: undefined reference to `fftw_plan_r2r_1d'
                  /home/msammartino/Documents/twochain/dimer.cpp:170: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:171: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:172: undefined reference to `fftw_execute'
                  /home/msammartino/Documents/twochain/dimer.cpp:173: undefined reference to `fftw_execute'
                  collect2: error: ld returned 1 exit status
                  The terminal process terminated with exit code: 1
                  
                  Terminal will be reused by tasks, press any key to close it.
                  

                  如果我提出這個問題的方式有任何問題,請告訴我.

                  Please let me know about any problems with the way I have asked this question.

                  推薦答案

                  簡單的選擇是 在 tasks.json 配置中將它們作為 args 傳遞:

                  The easy option is to pass them as args in your tasks.json configuration:

                  {
                    "version": "2.0.0",
                    "tasks": [
                      {
                        "label": "build-all",
                        "type": "shell",
                        "args": [
                            "-std=c++11",
                            "-lfftw3",
                            "-L",
                            "/path/to/libs",
                            "/path/to/file.cpp"
                        ],
                        "command": "g++",
                      }
                    ]
                  }
                  

                  更易于維護和共享的選項是創建一個 Makefile 并將它們全部設置在那里:

                  The more maintainable, shareable option is to create a Makefile and set them all there:

                  # Specify compiler to be used
                  CXX = g++
                  CXXFLAGS += -g -std=c++11 -fPIC -march=x86-64
                  
                  # Specify paths to headers
                  INCLUDES += -I include
                  
                  # Specify paths to the libraries
                  LDFLAGS  += -L /path/to/libs
                  
                  # Specify the link libraries
                  LLIBS    += -lfftw3
                  
                  # ... add other configs ...
                  
                  $(OBJ_DIR)/%.o: $(SRC_DIR)/%.cpp $(OBJ_DIR)
                      $(CXX) -c $(CXXFLAGS) $(INCLUDES) $< -o $@
                  
                  $(OBJ_DIR)/$(PROGRAM): $(OBJS)
                      $(CXX) $(LDFLAGS) $^ $(LLIBS) -o $@
                  

                  然后在您的任務配置中,只需調用make:

                  Then in your task configuration, just call make:

                  {
                    "version": "2.0.0",
                    "tasks": [
                      {
                        "label": "build-all",
                        "type": "shell",
                        "options": {
                            "cwd": "${workspaceFolder}",
                            "env": {
                              ...
                            }
                        },
                        "command": "make -f Makefile.x86_64",
                      }
                    ]
                  }
                  

                  如果你有依賴于 env 的路徑,你可以在你的 Makefile 中指定一個變量(例如 MY_LIBS),然后在任務配置的 env 塊中設置它們(例如,MY_LIBS":/path/to/libs").

                  If you have env-dependent paths, you can specify a variable in your Makefile (ex. MY_LIBS) and then set them in the env block of the task configuration (ex. "MY_LIBS": "/path/to/libs").

                  Makefile 選項的優點在于:

                  The advantage of the Makefile option is that:

                  • 不使用 VS Code 的人仍然可以編譯您的代碼(從控制臺或其他 IDE).
                  • 如果您使用的是 CI/CD 管道,則不需要單獨的配置.您可以使用相同的 Makefile 使用 VS Code 在本地進行構建,也可以使用 CI/CD 進行構建.
                  • 您可以將 Makefile 提交到存儲庫,然后只需在本地 tasks.json 配置中使用環境變量來指定特定于環境的設置.

                  這篇關于如何在 Visual Studio Code 中包含編譯器標志?的文章就介紹到這了,希望我們推薦的答案對大家有所幫助,也希望大家多多支持html5模板網!

                  【網站聲明】本站部分內容來源于互聯網,旨在幫助大家更快的解決問題,如果有圖片或者內容侵犯了您的權益,請聯系我們刪除處理,感謝您的支持!

                  相關文檔推薦

                  In what ways do C++ exceptions slow down code when there are no exceptions thown?(當沒有異常時,C++ 異常會以何種方式減慢代碼速度?)
                  Why catch an exception as reference-to-const?(為什么要捕獲異常作為對 const 的引用?)
                  When and how should I use exception handling?(我應該何時以及如何使用異常處理?)
                  Scope of exception object in C++(C++中異常對象的范圍)
                  Catching exceptions from a constructor#39;s initializer list(從構造函數的初始化列表中捕獲異常)
                  Difference between C++03 throw() specifier C++11 noexcept(C++03 throw() 說明符 C++11 noexcept 之間的區別)
                • <legend id='EzMed'><style id='EzMed'><dir id='EzMed'><q id='EzMed'></q></dir></style></legend>
                      1. <i id='EzMed'><tr id='EzMed'><dt id='EzMed'><q id='EzMed'><span id='EzMed'><b id='EzMed'><form id='EzMed'><ins id='EzMed'></ins><ul id='EzMed'></ul><sub id='EzMed'></sub></form><legend id='EzMed'></legend><bdo id='EzMed'><pre id='EzMed'><center id='EzMed'></center></pre></bdo></b><th id='EzMed'></th></span></q></dt></tr></i><div class="qwawimqqmiuu" id='EzMed'><tfoot id='EzMed'></tfoot><dl id='EzMed'><fieldset id='EzMed'></fieldset></dl></div>
                          <tbody id='EzMed'></tbody>

                          <small id='EzMed'></small><noframes id='EzMed'>

                          • <bdo id='EzMed'></bdo><ul id='EzMed'></ul>

                            <tfoot id='EzMed'></tfoot>
                            主站蜘蛛池模板: 国产亚洲视频在线观看 | 亚洲欧洲av | 黄色片免费观看 | 精品少妇一区二区三区免费观 | 99久久综合| 黄色福利视频 | 91久久国产综合久久91精品网站 | 九九综合网 | 这里都是精品 | av免费不卡 | 激情小说亚洲 | 岛国精品在线播放 | 欧美黄色一区二区 | 成人黄色在线视频 | 激情丁香婷婷 | 日本亚洲欧美 | 国产一级免费视频 | 国产精品一区在线观看 | av高清在线观看 | 三级视频在线观看 | 一区二区三区免费 | 特级西西444www大精品视频 | 国产成人网 | 最新中文字幕在线 | 日韩欧美精品一区 | 午夜视频免费看 | 成人免费看片在线观看 | 久久夜色精品国产欧美乱极品 | 黄色大片儿 | 日韩精品一 | 中文字幕日本在线 | 亚洲精品日韩精品 | 精品国产乱码一区二区三 | 一区二区高清视频 | 亚洲精品在线视频观看 | 亚洲理论片 | 国产天堂网 | 国产精品自在线 | 男女啪啪免费 | 久久视频在线 | 久久狠 |