S4A known directories

 the IDE has grown organically over the years and many things are not documented.

I thought something useful might be the (current) set of directories used by S4A 4.9.2 (note, these things change often)


In ~/Library/Application Support/SwiftForArduino...

Boards

- a supplementary boards.yaml file and related images, allowing you to add board definitions, which will be detected if their USB VID/PID match

Builds

- dynamically created/destroyed folders that contain the files built from source code, created on demand and deleted when you close the project, there is an advanced setting to keep contents

Extensions/Build

- the location for build plugins used by the board definitions, e.g. 0-series atmega chip build plugins

Extensions/Upload

- the location for upload plugins used by the board definitions, e.g. 0-series atmega chip upload plugins

Extensions/Modules

- added into the swift compile and clang compile paths, you can put built modules in here for import into your code

Libraries

- automatically downloaded from the github community site, these are useful swift files that can be imported as tabs into your project

S4A/XXX/Modules

- internally maintained folders containing low level modules deployed automatically with the IDE, HAL metal layer and AVR

Styles

- a supplementary styles.yaml file for altering themed colours in the IDE



In ~/Documents/SwiftForArduino...

Exports

- if you build a project as a module, it's output is placed here, there's an advanced preference to include this on the import list for future project builds, useful for testing built modules

Comments

Post a Comment

Popular posts from this blog

Halloween LED lights on a plastic trick or treat cauldron

Image
Halloween has past but it wasn’t uneventful. My two year old daughter went trick or treating for the first time and it was all so exciting! When i saw the plastic cauldron she was carrying as a trick or treat bag i had an idea. I could use an arduino to operate red LEDs and make the cauldron flash on and off like little evil eyes. I knew she would love it! Once I drilled the holes and got all the pieces I needed: 2 red LEDs soldered in series with a resistor. I connected those to a breadboard arduino I had spare. (See my blog post on making a breadboard arduino.) You can just use a normal Arduino UNO here instead if you prefer. My reasons are because they're cheaper, and also because a breadboard Arduino uses less power and I wanted this to be battery powered. I'm powering the whole thing with 3 AA batteries in a battery case. Because Maplin has shut down in the UK :((( I will have to wait for the battery holder to be delivered... no more weekend fun popping down t...
Read more

Swift for Arduino newsletter - Saturday November 16th 2019

Hello to the Swift for Arduino community! We are so excited to get in touch with you and let you know what's going on. First and foremost... Black Friday/Cyber Monday! We are giving away huge discounts! *** The Swift for Arduino Starter Box... HALF PRICE!! *** (Contains a Seeed Studios Lotus board and connectors, you don't need any of your own hardware, get started right away!) Note: to use this discount, you must enter the discount code BFCM50 in the Shopify store during checkout. This discount is limited in time and number - don't lose out! Offer available from 00:00 on Friday 29th November, closes 23.59 on Monday 2nd December 2019 (For convenience, you can use this link:   https://s4a-elements.com/discount/BFCM50?redirect=%2Fproducts%2Fcopy-of-s4a-silver-standard-box ) *** The Swift for Arduino IDE - license only... 70% OFF!! *** (suitable for customers who already have an Arduino UNO or similar board) This d...
Read more

code signing, entitlements, bundles, sandboxes, hardened runtime, notarisation, app store security

Some people had mentioned troubles with code signing, i thought a brain dump of my learnings on it might be informative and helpful as I've learned a lot in developing a mac app (the s4a IDE).  Some of these concepts are used in ios too but this post is about mac apps. First up, terminology. Code signing. *** This is a variant of normal PKI (public key infrastructure) signing. A hash is made of the binary you're signing (the actual macho executable file), then encrypted with your private key to make a signature that anyone with your public key can decrypt and verify to check your binary hasn't been altered in any way since you signed it. Code signing could in theory be done with any tool, (many of these concepts are NOT mac/ios only concepts but follow general unix/windows/etc. principles and ideas widely used across industry), but in reality, people on a mac use the built in (to macOS) tool "codesign" which is a command line tool that can create, alter, remove an...
Read more