{"id":28369,"date":"2021-08-10T19:45:49","date_gmt":"2021-08-10T19:45:49","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=28369"},"modified":"2025-08-12T22:21:48","modified_gmt":"2025-08-12T22:21:48","slug":"arm64ec-support-in-visual-studio","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/arm64ec-support-in-visual-studio\/","title":{"rendered":"ARM64EC Support in Visual Studio"},"content":{"rendered":"<p>ARM64EC (\u201cEmulation Compatible\u201d) is a new application binary interface (ABI) for building apps for Windows 11 on ARM. With ARM64EC, you can build new native apps that can run on ARM or incrementally transition existing x64 apps to native performance on ARM. For more information about ARM64EC, check out the <a href=\"https:\/\/aka.ms\/arm64ecannounceblog\">Windows Developer blog<\/a>.<\/p>\n<h2>Why Should Developers Target ARM64EC?<\/h2>\n<p>Applications that are built to run on ARM, give customers the benefit of a great native experience that unlocks the full power of the ARM device. However, from a developer perspective, porting an app to run on ARM can be all-or-nothing, since <strong>all<\/strong> the binaries within a process need to be rebuilt as ARM before a customer can enjoy the benefits.<\/p>\n<p>With ARM64EC, you can choose to start small and build incrementally. Once you identify the part of your codebase that would benefit most from native performance, you can simply rebuild it as ARM64EC. The rest of the app will remain fully functional as emulated x64, but the recompiled ARM64EC parts will now have native speed.<\/p>\n<p>In addition, the ability to mix and match x64 and ARM64EC makes it possible to build an app on ARM even if it depends on x64 code outside of your control. For example, projects with third-party dependencies that don\u2019t support ARM can leave them as x64. Also, apps with an in-proc plugin ecosystem can build as ARM64EC to get native speed on ARM, while continuing to load and use x64 plugins.<\/p>\n<h2>How to Target ARM64EC in Visual Studio<\/h2>\n<p>To start using Visual Studio to build your projects as ARM64EC, you&#8217;ll need to install these prerequisites:<\/p>\n<ul>\n<li>The latest\u00a0<a href=\"https:\/\/aka.ms\/windowsinsidersdk\">Windows Insider SDK build<\/a>\u00a0which is available through the Windows Insider program.<\/li>\n<li>The latest <a href=\"https:\/\/visualstudio.microsoft.com\/vs\/preview\/\" target=\"_blank\" rel=\"noopener\">Visual Studio 2019 Preview<\/a> or <a href=\"https:\/\/visualstudio.microsoft.com\/vs\/preview\/vs2022\/\" target=\"_blank\" rel=\"noopener\">Visual Studio 2022 Preview<\/a><\/li>\n<li>The ARM64EC tools from the Visual Studio Installer:<\/li>\n<\/ul>\n<p style=\"padding-left: 40px;\"><img decoding=\"async\" width=\"713\" height=\"275\" class=\"wp-image-28370\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-email.png\" alt=\"Graphical user interface, text, application, email Description automatically generated\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-email.png 713w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-email-300x116.png 300w\" sizes=\"(max-width: 713px) 100vw, 713px\" \/><\/p>\n<p>Once you have installed all the prerequisites, you can now target ARM64EC in your MSBuild and CMake Projects as explained in the following sections.<\/p>\n<p><strong>Note<\/strong>: In 17.4, in order to get ARM64EC support, install the ARM64 build tools instead.<\/p>\n<h3>MSBuild Projects<\/h3>\n<p>Open your C++ project or solution in Visual Studio. If you don\u2019t have one yet, create a new one by navigating to: <strong>Create a new project &gt; C++ Console App<\/strong>:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28371\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica.png\" alt=\"A screenshot of a computer Description automatically generated with medium confidence\" width=\"858\" height=\"371\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica.png 2552w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-300x130.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1024x443.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-768x332.png 768w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1536x664.png 1536w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-2048x885.png 2048w\" sizes=\"(max-width: 858px) 100vw, 858px\" \/><\/p>\n<p>Open up the configuration manager by navigating to the tool bar and clicking <strong>build &gt; configuration manager<\/strong>:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28372\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1.png\" alt=\"A screenshot of a computer Description automatically generated\" width=\"409\" height=\"362\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1.png 1118w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1-300x266.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1-1024x908.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/a-screenshot-of-a-computer-description-automatica-1-768x681.png 768w\" sizes=\"(max-width: 409px) 100vw, 409px\" \/><\/p>\n<p>In the\u00a0Active solution platform\u00a0box, select\u00a0<strong>&lt;New\u2026&gt;<\/strong> to create a new platform:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28373\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word.png\" alt=\"Graphical user interface, text, application, Word, email Description automatically generated\" width=\"683\" height=\"261\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word.png 1709w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word-300x115.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word-1024x391.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word-768x293.png 768w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-word-1536x587.png 1536w\" sizes=\"(max-width: 683px) 100vw, 683px\" \/><\/p>\n<p>Select\u00a0<strong>ARM64EC<\/strong>, Copy settings from\u00a0<strong>x64<\/strong>, check the\u00a0<strong>Create new project platforms<\/strong>\u00a0checkbox and click <strong>OK<\/strong>:<\/p>\n<p><a href=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/Picture1.png\"><img decoding=\"async\" class=\"alignnone wp-image-28383\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/Picture1-300x220.png\" alt=\"Image Picture1\" width=\"378\" height=\"277\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/Picture1-300x220.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/Picture1.png 624w\" sizes=\"(max-width: 378px) 100vw, 378px\" \/><\/a><\/p>\n<p>Finally, ensuring that ARM64EC is the active solution configuration, select <strong>Build <\/strong>from the menu to successfully build your ARM64EC project.<\/p>\n<p><strong>Note<\/strong>: By design, not all projects in the ARM64EC solution need to be targeting ARM64EC as they can target x64 instead. Ensure that you configure those x64 projects in the configuration manager to target x64 under the ARM64EC solution build:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28375\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description.png\" alt=\"Graphical user interface, application Description automatically generated\" width=\"884\" height=\"345\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description.png 1664w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description-300x117.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description-1024x399.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description-768x300.png 768w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-application-description-1536x599.png 1536w\" sizes=\"(max-width: 884px) 100vw, 884px\" \/><\/p>\n<p>For more information on working with MSBuild C++ Projects, see our documentation on\u00a0<a href=\"https:\/\/docs.microsoft.com\/en-us\/cpp\/build\/creating-and-managing-visual-cpp-projects?view=msvc-160\">Visual Studio Projects &#8211; C++ | Microsoft Docs<\/a> and <a href=\"https:\/\/docs.microsoft.com\/en-us\/visualstudio\/debugger\/remote-debugging-cpp?view=vs-2019\">Remote Debug a C++ Project &#8211; Visual Studio (Windows) | Microsoft Docs<\/a><\/p>\n<h3>CMake Projects<\/h3>\n<p>If you haven\u2019t already, install the CMake Build tools from the Visual Studio Installer:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28376\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr.png\" alt=\"Graphical user interface, text, application Description automatically generated\" width=\"425\" height=\"238\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr.png 800w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-300x168.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-768x430.png 768w\" sizes=\"(max-width: 425px) 100vw, 425px\" \/><\/p>\n<p>Open your C++ CMake project in Visual Studio. If you don\u2019t have one yet, create a new one by navigating to: <strong>Create a new project &gt; CMake Project<\/strong>:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28377\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall.png\" alt=\"Graphical user interface Description automatically generated\" width=\"704\" height=\"342\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall.png 2468w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall-300x146.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall-1024x497.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall-768x373.png 768w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall-1536x746.png 1536w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-description-automaticall-2048x994.png 2048w\" sizes=\"(max-width: 704px) 100vw, 704px\" \/><\/p>\n<p>With <a href=\"https:\/\/cmake.org\/cmake\/help\/latest\/manual\/cmake-presets.7.html\">CMakePresets.json<\/a> integration in Visual Studio, the default active configuration of the new project will be the Windows default which targets configuring and building on the local Windows Machine. This is the scenario we are interested in.<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28378\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1.png\" alt=\"Graphical user interface, text, application Description automatically generated\" width=\"673\" height=\"158\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1.png 1975w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1-300x70.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1-1024x241.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1-768x180.png 768w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-application-descr-1-1536x361.png 1536w\" sizes=\"(max-width: 673px) 100vw, 673px\" \/><\/p>\n<p>Open up the CMakePresets.json file by going to the active configuration dropdown and selecting <strong>Manage Configurations<\/strong>:<\/p>\n<p><img decoding=\"async\" class=\"wp-image-28379\" src=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-description-automa.png\" alt=\"Graphical user interface, text Description automatically generated\" width=\"717\" height=\"230\" srcset=\"https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-description-automa.png 1175w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-description-automa-300x96.png 300w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-description-automa-1024x329.png 1024w, https:\/\/devblogs.microsoft.com\/cppblog\/wp-content\/uploads\/sites\/9\/2021\/07\/graphical-user-interface-text-description-automa-768x246.png 768w\" sizes=\"(max-width: 717px) 100vw, 717px\" \/><\/p>\n<p>Modify the architecture property under the windows configuration you want for ARM64EC:<\/p>\n<pre class=\"prettyprint\"> \"architecture\": { \r\n    \"value\": \"arm64ec\", \r\n    \"strategy\": \"external\"\r\n }<\/pre>\n<p><strong>Note: <\/strong>The default generator is Ninja. If using the visual studio generator (2019 or 2022), change the strategy field to<strong> set.<\/strong><\/p>\n<p>If using Ninja generator, you\u2019ll also need to set some environment variables by adding the <strong>environment <\/strong> object to your CMakePresets configuration:<\/p>\n<pre class=\"prettyprint\"> \"environment\": { \r\n    \"CXXFLAGS\": \"\/arm64EC\",\r\n    \"CFLAGS\": \"\/arm64EC\" \r\n }<\/pre>\n<p>Save the CMakePresets file and make sure the active configuration is set to the arm64ec configuration. From the menu bar, select <strong>project menu, <\/strong>then select<strong> Configure &lt;Project Name&gt; <\/strong>in order to generate your CMake cache.<\/p>\n<p>Build your CMake Project targeting ARM64EC like any other CMake project: navigate to the <strong>Build Menu <\/strong>and select <strong>build all<\/strong>.<\/p>\n<p>For more information on working with CMake projects and CMakePresets, see our documentation on\u00a0 <a href=\"https:\/\/docs.microsoft.com\/en-us\/cpp\/build\/cmake-projects-in-visual-studio?view=msvc-160\">CMake projects in Visual Studio | Microsoft Docs<\/a> , <a href=\"https:\/\/docs.microsoft.com\/en-us\/cpp\/build\/cmake-presets-vs?view=msvc-160\">Configure and build with CMake Presets | Microsoft Docs<\/a> and <a href=\"https:\/\/docs.microsoft.com\/en-us\/cpp\/build\/cmake-remote-debugging?view=msvc-160\">Tutorial: Debug a CMake project on a remote Windows machine | Microsoft Docs<\/a>.<code><\/code><\/p>\n<p><code><\/code><\/p>\n<h4>Developer Command Prompt<\/h4>\n<p>If you are interested in using the Visual Studio Developer Command Prompt for compiling and linking source files for ARM64EC, you need to use the<strong> ARM64<\/strong> Developer Command Prompt, and then run your cl and link commands separately:<\/p>\n<p><code>vsdevcmd -host_arch=x64 -arch=arm64<\/code> \/\/ creates an ARM64 Developer Command Prompt from your default Developer Command Prompt<\/p>\n<p><code>cl \/arm64EC \/c &lt;args&gt;<\/code><\/p>\n<p><code>link \/MACHINE:ARM64EC &lt;args&gt;<\/code><\/p>\n<p><strong>Note: <\/strong>When using the Ninja generator for ARM64EC CMake builds in the developer command prompt, you must explicitly set the environment variables <code data-start=\"570\" data-end=\"578\">CFLAGS<\/code> and <code data-start=\"583\" data-end=\"593\">CXXFLAGS<\/code> to <code data-start=\"597\" data-end=\"607\">\/arm64EC<\/code>. Run these commands in your developer command prompt before running CMake:<\/p>\n<p><code>set CFLAGS=\/arm64EC<\/code><code><\/code><code><\/code><code><\/code><\/p>\n<p><code>set CXXFLAGS=\/arm64EC<\/code><\/p>\n<h2>Give us your feedback<\/h2>\n<p>Download\u00a0the latest\u00a0<a href=\"https:\/\/visualstudio.microsoft.com\/vs\/preview\/&quot; \\t &quot;_blank\">Visual Studio 2019 Preview<\/a> or <a href=\"https:\/\/visualstudio.microsoft.com\/vs\/preview\/vs2022\/\" target=\"_blank\" rel=\"noopener\">Visual Studio 2022 Preview<\/a> \u00a0today and give it a try. We\u2019d love to hear from you to help us prioritize and build the right features for you. We can be reached via the comments below,\u00a0<a href=\"https:\/\/developercommunity.visualstudio.com\/spaces\/8\/index.html\" target=\"_blank\" rel=\"noopener\">Developer Community<\/a>, and Twitter (<a href=\"https:\/\/twitter.com\/visualc\" target=\"_blank\" rel=\"noopener\">@VisualC<\/a>). The best way to file a bug or suggest a feature is via Developer Community.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>ARM64EC (\u201cEmulation Compatible\u201d) is a new application binary interface for building apps for Windows 11 on ARM. With ARM64EC, you can build new native apps that can run on ARM or incrementally transition existing x64 apps to native performance on ARM. With Visual Studio, you can start building your projects as ARM64EC and enjoy the benefits.<\/p>\n","protected":false},"author":53792,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-28369","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus"],"acf":[],"blog_post_summary":"<p>ARM64EC (\u201cEmulation Compatible\u201d) is a new application binary interface for building apps for Windows 11 on ARM. With ARM64EC, you can build new native apps that can run on ARM or incrementally transition existing x64 apps to native performance on ARM. With Visual Studio, you can start building your projects as ARM64EC and enjoy the benefits.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/28369","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/53792"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=28369"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/28369\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/35994"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=28369"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=28369"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=28369"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}