-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
one solution would be to handle this syntax:
```
struct Foo {
int foo;
char bar;
}
```
maybe just use dword, byte, ... instead of int/char... then we should just define labels for those fields like …
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…
-
```
Gyp includes the -arch parameters from xcode_emulation with the makefile
generator when the flavour is set to mac, and cannot be removed. (It can be
modified by setting ARCHS, but not completely…