-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
This signing thing is cumbersome. Can't someone just get an apple developer certificate and release signed installers or something? Xcode extensions can also be distributed via the mac app store
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …
-
```
Currently the xcode generator makes a range of assumptions regarding file
extensions. It contains hardcoded lists of extensions like .c .cpp .h .m .s
etc.
To work around the need to support .S …