Merge pull request #626 from dawidborycki/LP-batch-1

Learning paths batch 1

Author: pareenaverma

content/learning-paths/laptops-and-desktops/win_arm64ec_porting/_index.md

@@ -0,0 +1,36 @@
+---
+title: Port Your Applications to Arm64 Using Arm64EC
+
+minutes_to_complete: 90
+
+who_is_this_for: This is an introductory topic for developers who want to learn how to port their applications to Arm64 using Arm64EC. 
+
+learning_objectives:
+    - Build a Qt-based Python desktop application
+    - Create C/C++ dependencies and use them in the Qt-based Python app
+    - Learn how to port the C/C++ based dependencies to Arm64 using Arm64EC.
+
+prerequisites:
+    - A Windows on Arm computer such as [Windows Dev Kit 2023](https://learn.microsoft.com/en-us/windows/arm/dev-kit), Lenovo Thinkpad X13s running Windows 11 or Windows on Arm[virtual machine](/learning-paths/cross-platform/woa_azure/).
+    - Any code editor, we recommend using [Visual Studio Code for Arm64](https://code.visualstudio.com/docs/?dv=win32arm64user).
+    - Visual Studio 2022 with Arm build tools. [Refer to this guide for the installation steps](https://developer.arm.com/documentation/102528/0100/Install-Visual-Studio).
+    
+author_primary: Dawid Borycki
+
+### Tags
+skilllevels: Introductory
+subjects: Migration to Arm
+armips:
+    - Cortex-A
+operatingsystems:
+    - Windows
+tools_software_languages:
+    - C/C++
+    - Qt    
+
+### FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 1                       # _index.md always has weight of 1 to order correctly
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+learning_path_main_page: "yes"  # This should be surfaced when looking for related content. Only set for _index.md of learning path content.
+---

content/learning-paths/laptops-and-desktops/win_arm64ec_porting/_next-steps.md

@@ -0,0 +1,39 @@
+---
+# ================================================================================
+#       Edit
+# ================================================================================
+
+next_step_guidance: >   
+   You have learned how to to port C/C++ DLLs to Arm64 using Arm64EC using CMake and MSBuild projects. You also learned how to use DLLs in the Python app with ctypes. You might be interested in learning how to build a native Windows on Arm application using the .NET framework.
+# 1-3 sentence recommendation outlining how the reader can generally keep learning about these topics, and a specific explanation of why the next step is being recommended.
+
+recommended_path: "/learning-paths/laptops-and-desktops/win_net"
+# Link to the next learning path being recommended(For example this could be /learning-paths/servers-and-cloud-computing/mongodb).
+
+
+# further_reading links to references related to this path. Can be:
+    # Manuals for a tool / software mentioned   (type: documentation)
+    # Blog about related topics                 (type: blog)
+    # General online references                 (type: website) 
+
+further_reading:
+    - resource:
+        title: Arm64EC - Build and port apps for native performance on Arm
+        link: https://learn.microsoft.com/en-us/windows/arm/arm64ec
+        type: documentation
+    - resource:
+        title: Visual Studio on Arm-powered devices
+        link: https://learn.microsoft.com/en-us/visualstudio/install/visual-studio-on-arm-devices?view=vs-2022
+        type: documentation
+    - resource:
+        title: Load x64 Plug-ins (like VSTs) from your Arm Code using Arm64EC
+        link: https://devblogs.microsoft.com/windows-music-dev/load-x64-plug-ins-like-vsts-from-your-arm-code-using-arm64ec/
+        type: blog    
+
+# ================================================================================
+#       FIXED, DO NOT MODIFY
+# ================================================================================
+weight: 21                  # set to always be larger than the content in this path, and one more than 'review'
+title: "Next Steps"         # Always the same
+layout: "learningpathall"   # All files under learning paths have this same wrapper
+---

content/learning-paths/laptops-and-desktops/win_arm64ec_porting/_review.md

@@ -0,0 +1,41 @@
+---
+# ================================================================================
+#       Edit
+# ================================================================================
+
+# Always 3 questions. Should try to test the reader's knowledge, and reinforce the key points you want them to remember.
+    # question:         A one sentence question
+    # answers:          The correct answers (from 2-4 answer options only). Should be surrounded by quotes.
+    # correct_answer:   An integer indicating what answer is correct (index starts from 0)
+    # explanation:      A short (1-3 sentence) explanation of why the correct answer is correct. Can add additional context if desired
+
+
+review:
+    - questions:
+        question: >
+            Is it possible to import a C/C++ library to a Python application?
+        answers:
+            - "Yes"
+            - "No"            
+        correct_answer: 1
+        explanation: >
+            Yes, you can import C/C++ DLLs to a Python application using ctypes.
+
+    - questions:
+        question: >
+            How do you port C/C++ code to ARM64 using ARM64EC and MSBuild?
+        answers:
+            - "Using a command line tool port-to-arm64"
+            - "Using a command line tool port-to-arm64-msbuild"
+            - "By targeting the ARM64EC build configuration"
+        correct_answer: 3                     
+        explanation: >
+            For the MSBuild projects you use ARM64EC build configuration to compile the DLL to ARM64EC
+
+# ================================================================================
+#       FIXED, DO NOT MODIFY
+# ================================================================================
+title: "Review"                 # Always the same title
+weight: 20                      # Set to always be larger than the content in this path
+layout: "learningpathall"       # All files under learning paths have this same wrapper
+---