# Building for different architectures
**URL:** https://framelib.discourse.group/t/building-for-different-architectures/86
**Category:** Documentation
**Created:** [21 February 2021 14:16 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86 "2021-02-21T14:16:38Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@james.bradbury](https://framelib.discourse.group/u/james.bradbury)
#### Post date: [21 February 2021 14:16 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/1 "2021-02-21T14:16:38Z")
This is perhaps worth at least raising for developer documentation. I managed with @a.harker 's help to build FrameLib for the M1 architecture. It is relatively simple to do - you just need to change some of the Xcode configurations.
Below is the diff of my `.xcconfig`
```auto
diff --git a/Config_FrameLib.xcconfig b/Config_FrameLib.xcconfig
index fa6074da..ae7ea8b1 100755
--- a/Config_FrameLib.xcconfig
+++ b/Config_FrameLib.xcconfig
@@ -5,12 +5,12 @@ PRODUCT_NAME = $(TARGET_NAME)
// Per architecture and deployment settings
-ARCHS = i386 x86_64
+ARCHS = x86_64
-MACOSX_DEPLOYMENT_TARGET = 10.7
+MACOSX_DEPLOYMENT_TARGET = 11.1
CLANG_CXX_LANGUAGE_STANDARD = c++11
CLANG_CXX_LIBRARY = libc++
-CLANG_X86_VECTOR_INSTRUCTIONS = avx
+CLANG_X86_VECTOR_INSTRUCTIONS = sse4.2
LLVM_LTO = Monolithic
```
Very simple!
---
### Author:  [@a.harker](https://framelib.discourse.group/u/a.harker)
#### Post date: [21 February 2021 14:29 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/2 "2021-02-21T14:29:34Z")
Thanks James!
Just to clarify - technically this is a build for intel 64 bit but set up so that it will run on Rosetta 2 - it isn’t yet an ARM build…
Likely when cycling74 go to ARM then I’ll move the default build settings to Universal Binary 2, meaning that the externals should run on Intel and M1 native.
---
### Author:  [@james.bradbury](https://framelib.discourse.group/u/james.bradbury)
#### Post date: [21 February 2021 14:32 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/3 "2021-02-21T14:32:55Z")
> [@a.harker](#):
>
> Just to clarify - technically this is a build for intel 64 bit but set up so that it will run on Rosetta 2 - it isn’t yet an ARM build…
Ah yes, I forgot to clarify this. Thanks.
> [@a.harker](#):
>
> Likely when cycling74 go to ARM then I’ll move the default build settings to Universal Binary 2, meaning that the externals should run on Intel and M1 native.
cool
---
### Author:  [@o.green](https://framelib.discourse.group/u/o.green)
#### Post date: [21 February 2021 18:20 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/4 "2021-02-21T18:20:07Z")
Does the Mac OS deployment target make a substantial difference here?
---
### Author:  [@a.harker](https://framelib.discourse.group/u/a.harker)
#### Post date: [21 February 2021 20:44 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/5 "2021-02-21T20:44:26Z")
I can’t see why that change would be needed to run on M1, but it’s possible James needed to change it because the SDK wouldn’t support something so old.
---
### Author:  [@james.bradbury](https://framelib.discourse.group/u/james.bradbury)
#### Post date: [22 February 2021 10:19 UTC](https://framelib.discourse.group/t/building-for-different-architectures/86/6 "2021-02-22T10:19:07Z")
Actually, I changed that line _with_ the instruction flag so its likely it can be whatever you want I imagine.