• State Not Answered
  • Replies 3 replies
  • Subscribers 17 subscribers
  • Views 796 views
  • Users 0 members are here
Options
Related

Setup VisualStudio to launch the simulator on Mac

Cristi B
over 3 years ago

Hi,

I'm back into developing my watchface after a short break and i already forgot all the commands and step i was doing so had to research again.

First thing was to run the export command to my current sdk to make the terminal aware of it, for some reason is forgetting it after each restart although i added it in some hidden file as instructed. Not sure i did a mistake there but since i restart once every few weeks/months is not a problem, but since the path changes with each sdk update i'm not sure that is very usefull. Also, what is 'set as current sdk' doing in sdkmanager because i see no change?

Then is the build command in visual studio monkey c extension, which is the easiest part.

But then to see my app in simulator i need to switch to the terminal, open connectiq once, then run monkeydo to launch my prg, then to run it again need to stop the previous command

So there are a lot of useless steps, is there a way to do all this from visual studio in one step?

  • 0 over 3 years ago

    What platform are you on? It’s not nearly that hard.

  • 0 over 3 years ago

    Sounds like the problem here is that you are doing some manual steps in the terminal (which shouldn't be necessary unless something is broken).

    "Set as current SDK" will change the current SDK used by the Monkey C plugin in Visual Studio Code and Eclipse. It won't affect what SDK is used when you type commands from the terminal.

    If you want to run your app, it should be as simple as selecting an MC file and pressing F5. If you have a touchbar Mac, you can also press the Run icon on the touchbar, which looks like this:

    You'll be prompted for the device to build for, and once you select it, the build should run and the simulator should open automatically and launch the app.

    If that doesn't work, then something is wrong (an issue with your setup, or a bug in the SDK or VS Code plugin).

  • 0 over 3 years ago in reply to flowstate

    That was easier than i expected, it does work, thank you.