Return to site

Visual C Mac

broken image


Ufed 4 pc software free. In this tutorial, you configure Visual Studio Code on macOS to use the Clang/LLVM compiler and debugger.

  1. Download Microsoft Visual C++ 2015
  2. Visual C++ Download

After configuring VS Code, you will compile and debug a simple C++ program in VS Code. This tutorial does not teach you about Clang or the C++ language. For those subjects, there are many good resources available on the Web.

If you have any trouble, feel free to file an issue for this tutorial in the VS Code documentation repository.

Prerequisites

To successfully complete this tutorial, you must do the following:

  1. Install Visual Studio Code on macOS.

  2. Install the C++ extension for VS Code. You can install the C/C++ extension by searching for 'c++' in the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)).

Ensure Clang is installed

Clang may already be installed on your Mac. To verify that it is, open a macOS Terminal window and enter the following command:

In Visual Studio for Mac visual studio for mac fixed in: visual studio 2019 for mac version 8.8 preview 4 Fixed - Pending Release Feedback Bot commented Oct 14, '20 6 Votes. The moderator on the second link said specifically that the visual studio version for Mac does not support C, it only supports ' Mobile with.NET: Android, iOS, tvOS, watchOS Mac desktop apps.NET Core applications ASP.NET Core Web applications Cross-platform Unity games' I find this really disappointing.

  1. If Clang isn't installed, enter the following command to install the command line developer tools:

Create Hello World

From the macOS Terminal, create an empty folder called projects where you can store all your VS Code projects, then create a subfolder called helloworld, navigate into it, and open VS Code in that folder by entering the following commands:

The code . command opens VS Code in the current working folder, which becomes your 'workspace'. As you go through the tutorial, you will create three files in a .vscode folder in the workspace:

  • tasks.json (compiler build settings)
  • launch.json (debugger settings)
  • c_cpp_properties.json (compiler path and IntelliSense settings)

Add hello world source code file

Download Microsoft Visual C++ 2015

In the File Explorer title bar, select New File and name the file helloworld.cpp.

Paste in the following source code:

Now press ⌘S (Windows, Linux Ctrl+S) to save the file. Notice that your files are listed in the File Explorer view (⇧⌘E (Windows, Linux Ctrl+Shift+E)) in the side bar of VS Code:

You can also enable Auto Save to automatically save your file changes, by checking Auto Save in the main File menu.

The Activity Bar on the edge of Visual Studio Code lets you open different views such as Search, Source Control, and Run. You'll look at the Run view later in this tutorial. You can find out more about the other views in the VS Code User Interface documentation.

Note: When you save or open a C++ file, you may see a notification from the C/C++ extension about the availability of an Insiders version, which lets you test new features and fixes. You can ignore this notification by selecting the X (Clear Notification).

Explore IntelliSense

In the helloworld.cpp file, hover over vector or string to see type information. After the declaration of the msg variable, start typing msg. as you would when calling a member function. You should immediately see a completion list that shows all the member functions, and a window that shows the type information for the msg object:

You can press the Tab key to insert the selected member. Then, when you add the opening parenthesis, you'll see information about arguments that the function requires.

Build helloworld.cpp

Next, you'll create a tasks.json file to tell VS Code how to build (compile) the program. This task will invoke the Clang C++ compiler to create an executable file from the source code.

It's important to have helloworld.cpp open in the editor because the next step uses the active file in the editor as context to create the build task in the next step.

From the main menu, choose Terminal > Configure Default Build Task. A dropdown will appear listing various predefined build tasks for the compilers that VS Code found on your machine. Choose C/C++ clang++ build active file to build the file that is currently displayed (active) in the editor.

This will create a tasks.json file in the .vscode folder and open it in the editor.

Replace the contents of that file with the following:

The JSON above differs from the default template JSON in the following ways:

  • 'args' is updated to compile with C++17 because our helloworld.cpp uses C++17 language features.
  • Changes the current working directory directive ('cwd') to the folder where helloworld.cpp is.

The command setting specifies the program to run. https://headpoker-ruby-slippers-slot-free.peatix.com. In this case, 'clang++' is the driver that causes the Clang compiler to expect C++ code and link against the C++ standard library.

The args array specifies the command-line arguments that will be passed to clang++. https://vruj.over-blog.com/2021/02/stronghold-crusader-steam.html. These arguments must be specified in the order expected by the compiler. https://site-3743088-3702-6898.mystrikingly.com/blog/quick-hit-slots-free-coins-facebook.

This task tells the C++ compiler to compile the active file (${file}), and create an output file (-o switch) in the current directory (${fileDirname}) with the same name as the active file (${fileBasenameNoExtension}), resulting in helloworld for our example.

The label value is what you will see in the tasks list. Name this whatever you like.

The problemMatcher value selects the output parser to use for finding errors and warnings in the compiler output. For clang++, you'll get the best results if you use the $gcc problem matcher.

The 'isDefault': true value in the group object specifies that this task will be run when you press ⇧⌘B (Windows, Linux Ctrl+Shift+B). This property is for convenience only; if you set it to false, you can still build from the Terminal menu with Terminal > Run Build Task.

Note: You can learn more about task.json variables in the variables reference.

Running the build

  1. Go back to helloworld.cpp. Because we want to build helloworld.cpp it is important that this file be the one that is active in the editor for the next step.

  2. To run the build task that you defined in tasks.json, press ⇧⌘B (Windows, Linux Ctrl+Shift+B) or from the Terminal main menu choose Run Build Task.

  3. When the task starts, you should see the Integrated Terminal window appear below the code editor. After the task completes, the terminal shows output from the compiler that indicates whether the build succeeded or failed. For a successful Clang build, the output looks something like this:

  4. Create a new terminal using the + button and you'll have a new terminal with the helloworld folder as the working directory. Run ls and you should now see the executable helloworld along with the debugging file (helloworld.dSYM).

  5. You can run helloworld in the terminal by typing ./helloworld.

Modifying tasks.json

You can modify your tasks.json to build multiple C++ files by using an argument like '${workspaceFolder}/*.cpp' instead of ${file}. This will build all .cpp files in your current folder. You can also modify the output filename by replacing '${fileDirname}/${fileBasenameNoExtension}' with a hard-coded filename (for example '${workspaceFolder}/myProgram.out').

Debug helloworld.cpp

Purchase lightroom for mac. Next, you'll create a launch.json file to configure VS Code to launch the LLDB debugger when you press F5 to debug the program.

From the main menu, choose Run > Add Configuration. and then choose C++ (GDB/LLDB).

You'll then see a dropdown for predefined debugging configurations. Choose clang++ build and debug active file.

VS Code creates a launch.json file, opens it in the editor, and builds and runs 'helloworld'. Your launch.json file will look something like this:

The program setting specifies the program you want to debug. Here it is set to the active file folder ${fileDirname} and active filename ${fileBasenameNoExtension}, which if helloworld.cpp is the active file will be helloworld.

By default, the C++ extension won't add any breakpoints to your source code and the stopAtEntry value is set to false.

Change the stopAtEntry value to true to cause the debugger to stop on the main method when you start debugging.

Ensure that the preLaunchTask value matches the label of the build task in the task.json file.

Start a debugging session

  1. Go back to helloworld.cpp so that it is the active file in the editor. This is important because VS Code uses the active file to determine what you want to debug.
  2. Press F5 or from the main menu choose Run > Start Debugging. Before you start stepping through the source code, let's take a moment to notice several changes in the user interface:
  • The Integrated Terminal appears at the bottom of the source code editor. In the Debug Output tab, you see output that indicates the debugger is up and running.

  • The editor highlights the first statement in the main method. This is a breakpoint that the C++ extension automatically sets for you:

  • The Run view on the left shows debugging information. You'll see an example later in the tutorial.

  • Use xbox one controller on mac. At the top of the code editor, a debugging control panel appears. You can move this around the screen by grabbing the dots on the left side.

Visual C Mac

Step through the code

Now you're ready to start stepping through the code.

  1. Click or press the Step over icon in the debugging control panel so that the for (const string& word : msg) statement is highlighted.

    The Step Over command skips over all the internal function calls within the vector and string classes that are invoked when the msg variable is created and initialized. Notice the change in the Variables window. The contents of msg are visible because that statement has completed.

  2. Press Step over again to advance to the next statement (skipping over all the internal code that is executed to initialize the loop). Now, the Variables window shows information about the loop variable.

  3. Press Step over again to execute the cout statement. Note As of the March 2019 version of the extension, no output will appear in the DEBUG CONSOLE until the last cout completes.

Set a watch

You might want to keep track of the value of a variable as your program executes. You can do this by setting a watch on the variable.

  1. Place the insertion point inside the loop. In the Watch window, click the plus sign and in the text box, type word, which is the name of the loop variable. Now view the Watch window as you step through the loop.

  2. To quickly view the value of any variable while execution is paused, you can hover over it with the mouse pointer.

C/C++ configuration

Visual C++ Download

For more control over the C/C++ extension, create a c_cpp_properties.json file, which allows you to change settings such as the path to the compiler, include paths, which C++ standard to compile against (such as C++17), and more.

View the C/C++ configuration UI by running the command C/C++: Edit Configurations (UI) from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

This opens the C/C++ Configurations page.

Visual Studio Code places these settings in .vscode/c_cpp_properties.json. If you open that file directly, it should look something like this:

You only need to modify the Include path setting if your program includes header files that are not in your workspace or the standard library path.

Compiler path

compilerPath is an important configuration setting. The extension uses it to infer the path to the C++ standard library header files. When the extension knows where to find those files, it can provide useful features like smart completions and Go to Definition navigation.

The C/C++ extension attempts to populate compilerPath with the default compiler location based on what it finds on your system. The compilerPath search order is:

  • Your PATH for the names of known compilers. The order the compilers appear in the list depends on your PATH.
  • Then hard-coded XCode paths are searched, such as /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/

Mac framework path

On the C/C++ Configuration screen, scroll down and expand Advanced Settings and ensure that Mac framework path points to the system header files. For example: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks

Reusing your C++ configuration

VS Code is now configured to use Clang on macOS. The configuration applies to the current workspace. To reuse the configuration, just copy the JSON files to a .vscode folder in a new project folder (workspace) and change the names of the source file(s) and executable as needed.

Troubleshooting

Compiler and linking errors

The most common cause of errors (such as undefined _main, or attempting to link with file built for unknown-unsupported file format, and so on) occurs when helloworld.cpp is not the active file when you start a build or start debugging. This is because the compiler is trying to compile something that isn't source code, like your launch.json, tasks.json, or c_cpp_properties.json file.

Next steps

  • Explore the VS Code User Guide.
  • Review the Overview of the C++ extension
  • Create a new workspace, copy your .json files to it, adjust the necessary settings for the new workspace path, program name, and so on, and start coding!
-->

Per iniziare a sviluppare app .NET native e multipiattaforma in macOS, installare Visual Studio 2019 per Mac seguendo i passaggi indicati di seguito.To start developing native, cross-platform .NET apps on macOS, install Visual Studio 2019 for Mac following the steps below. Using google drive on a mac.

RequisitiRequirements

  • Mac con macOS High Sierra 10.13 o versione successiva.A Mac with macOS High Sierra 10.13 or above.

Per compilare app Xamarin per iOS o macOS, è anche necessario:To build Xamarin apps for iOS or macOS, you'll also need:

  • Xcode 10.0 o versione successiva.Xcode 10.0 or above.È in genere consigliabile usare la versione stabile più recente.The latest stable version is usually recommended.
  • ID Apple.An Apple ID.Se non si ha ancora un ID Apple, è possibile crearne uno nuovo all'indirizzo https://appleid.apple.com.If you don't have an Apple ID already you can create a new one at https://appleid.apple.com.L'ID Apple è necessario per installare Xcode e accedervi.It's necessary to have an Apple ID for installing and signing into Xcode.

Istruzioni per l'installazioneInstallation instructions

  1. Scaricare il programma di installazione dalla pagina di download di Visual Studio per Mac.Download the installer from the Visual Studio for Mac download page.

  2. Al termine del download, fare clic su VisualStudioforMacInstaller.dmg per montare il programma di installazione, quindi eseguirlo facendo doppio clic sul logo a forma di freccia:Once the download is complete, click the VisualStudioforMacInstaller.dmg to mount the installer, then run it by double-clicking the arrow logo:

  3. È possibile che venga visualizzato un avviso relativo al download dell'applicazione da Internet.You may be presented with a warning about the application being downloaded from the Internet.Fare clic su Apri.Click Open.

  4. Attendere mentre il programma di installazione verifica il sistema:Wait while the installer checks your system:

  5. Verrà visualizzato un avviso che chiede di accettare le condizioni di licenza e l'informativa sulla privacy.An alert will appear asking you to acknowledge the privacy and license terms.Seguire i collegamenti per leggerle e quindi premere Continua se si accettano:Follow the links to read them, then press Continue if you agree:

  6. Verrà visualizzato l'elenco dei carichi di lavoro disponibili.The list of available workloads is displayed.Selezionare i componenti da usare:Select the components you wish to use:

    Se non si desidera installare tutte le piattaforme, usare la guida seguente per decidere quali piattaforme installare:If you do not wish to install all platforms, use the guide below to help you decide which platforms to install:

    Tipo di appType of AppDestinazioneTargetSelezioneSelectionNoteNotes
    App che usano NovellApps Using XamarinXamarin.FormsXamarin.FormsSelezionare le piattaforme Android e iOSSelect Android and iOS platformsÈ necessario installare XcodeYou will need to install Xcode
    Solo iOSiOS onlySelezionare la piattaforma iOSSelect iOS platformÈ necessario installare XcodeYou will need to install Xcode
    Solo AndroidAndroid onlySeleziona piattaforma AndroidSelect Android platformSi noti che è necessario selezionare anche le dipendenze rilevantiNote that you should also select the relevant dependencies
    Solo MacMac onlySeleziona piattaforma MacOS (Cocoa)Select macOS (Cocoa) platformÈ necessario installare XcodeYou will need to install Xcode
    Applicazioni .NET Core.NET Core applicationsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Applicazioni Web ASP.NET CoreASP.NET Core Web ApplicationsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Funzioni di AzureAzure FunctionsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Sviluppo di giochi Unity multipiattaformaCross-platform Unity Game DevelopmentNon è necessario installare altre piattaforme oltre Visual Studio per Mac.No additional platforms need to be installed beyond Visual Studio for Mac.Fare riferimento alla guida all'installazione di Unity per altre informazioni sull'installazione dell'estensione di Unity.Refer to the Unity setup guide for more information on installing the Unity extension.
  7. Dopo aver effettuato le selezioni, premere il pulsante Installa.After you have made your selections, press the Install button.

  8. Il programma di installazione visualizzerà lo stato di avanzamento del download e dell'installazione di Visual Studio per Mac e dei carichi di lavoro selezionati.The installer will display progress as it downloads and installs Visual Studio for Mac and the selected workloads.Verrà richiesto di immettere la password per concedere i privilegi necessari per l'installazione:You will be prompted to enter your password to grant the privileges necessary for installation.:

  9. Una volta installato, Visual Studio per Mac chiederà di personalizzare l'installazione effettuando l'accesso e selezionando i tasti di scelta rapida che si vuole usare:Once installed, Visual Studio for Mac will prompt you to personalize your installation by signing in and selecting the key bindings that you'd like to use:

Se si riscontrano problemi di rete durante l'installazione in un ambiente aziendale, rivedere le istruzioni per l'installazione di Visual Studio per Mac protetto da un firewall o un proxy.If you have network trouble while installing in a corporate environment, review the installing behind a firewall or proxy instructions.

Altre informazioni sulle modifiche sono disponibili nelle note sulla versione.Learn more about the changes in the release notes.

Nota

Se si è scelto di non installare una piattaforma o uno strumento durante l'installazione originale (deselezionandolo nel passaggio 6), è necessario eseguire di nuovo il programma di installazione se si vogliono aggiungere i componenti in un secondo momento.If you chose not to install a platform or tool during the original installation (by unselecting it in step #6), you must run the installer again if you wish to add the components later.

Installare Visual Studio per Mac protetto da un firewall o un server proxyInstall Visual Studio for Mac behind a firewall or proxy server

Per installare Visual Studio per Mac protetto da un firewall, determinati endpoint devono essere resi accessibili per consentire i download degli strumenti e degli aggiornamenti necessari per il software.To install Visual Studio for Mac behind a firewall, certain endpoints must be made accessible in order to allow downloads of the required tools and updates for your software.

Configurare la rete per consentire l'accesso alle posizioni seguenti:Configure your network to allow access to the following locations:

Passaggi successiviNext steps

L'installazione di Visual Studio per Mac consente di iniziare a scrivere codice per le app.Installing Visual Studio for Mac allows you to start writing code for your apps.Le guide seguenti vengono fornite per eseguire i passaggi successivi di scrittura e distribuzione dei progetti.The following guides are provided to guide you through the next steps of writing and deploying your projects.

iOSiOS

  1. Provisioning di dispositivi (per eseguire l'applicazione nel dispositivo).Device Provisioning(To run your application on device).

AndroidAndroid

app .NET core, app Web ASP.NET Core, sviluppo di giochi Unity.NET Core apps, ASP.NET Core web apps, Unity game development

Per altri carichi di lavoro, vedere la pagina Carichi di lavoro.For other Workloads, refer to the Workloads page.

Video correlatoRelated Video

Vedi ancheSee also





broken image