[PD] compiling extenrals for mac 32 bits

[IOhannes m zmoelnig]

On 10/19/20 6:24 PM, Alexandre Torres Porres wrote:
> Em seg., 19 de out. de 2020 às 06:31, Dan Wilcox <danomatika at gmail.com>
> escreveu:
> 
>> you just have to set the fat binary extension when building on macOS (and
>> not other platforms) in your makefile:
>>
>> extension=d_fat
>>
> 
> Tried in the makefile and it didn't work, but then I thought you may have
> meant when doing "make install" and it worked ;)

i don't know what you tested.
but you should pass the "extension=..." argument to all invocations of 
make, like so:

```
make extension=d_fat
make extension=d_fat install
```

otherwise the build system might not do exactly what you want.
e.g. if you do:
```
make extension=d_fat
make install
```
then the 1st line will build the fat binaries (with the "d_fat" 
extension); but the 2nd line will try to install the normal binaries 
(with the "pd_darwin" extension), which it won't find.
because "make" is good at resolving dependencies it will then compile 
again to produce (non-fat) .pd_darwin files and install them.


> Now I should just delete the first "Darwin-amd64-32/pd_darwin" from deken, > right?

since you asked: i think people have told you multiple times that you 
should not remove things from deken.
in the general case, there is little to no benefit, but the potential of 
a lot of harm.

> I just want to be clear there's no reason to keep it. If my previous
> package is better in any way or something (like "faster"?). 

the package is smaller.

> I assume it
> would show both options for download and people will just be confused if
> there's no reason to pick one over the other.

if both packages have the same version number and run on your 
architecture, they will both show.
but people will basically get the same thing, regardless whether they 
click on one or the other.
so there's no harm in the confusion (in the end).

if you want to avoid confusion totally (because you are friendly and 
don't want to impose *any* mental stress onto people), upload a new version.


in general i think you should consider the deken storage as immutable 
("don't even think of trying to modify and/or delete stuff once published").
i would love to enforce this on the server-side, but it's very low on my 
TODO list.

gmadsr
IOhannes