Re-compile source code for several FileMaker plug-ins and sign for M1 Mac using latest Xcode
Budget: $30 – $250 AUD
Prior to this project I have had the source code prepared by a previous freelancer and the code compiled using an old Xcode version for use on Intel Macs (and another re-compilation using Microsoft Visual Studio for Windows), and since then I hadn't seen a need to re-compile as the plug-ins work perfectly (I still use them to this day). However, Apple has, in their kind heart, decided to move to the M1 Macs. Geez, thanks. Now it is time to do it all again (yuk!), and with the potential for some tweaking of the code (is it necessary?) and dealing with the silly GateKeeper just to prove that the plug-ins are really okay and safe for use on the M1 Macs.
Yes, I can hear you salivating. You definitely will have access to the source code in this project and all libraries that I used to create the Intel version. There is one proviso I should mention: please keep the source code for your own personal use (do not resell etc.). In return for giving you the source code, I require from you the following:
1. My fingers are crossed that all libraries are still compatible and can be used to compile the source code for use on M1. If not, please update the relevant libraries as you require. I don't think there is any need to tweak the source code as it has worked perfectly, but your experience will tell me if this is true or not. Let me know of any changes required. I am assuming that this is a straightforward re-compilation of the source code for use on the M1 Macs.
2. Send back to me only those files and libraries that had to be changed so I can keep my archive of the source code and libraries up-to-date.
3. Can you also send me a download link from DropBox or some other file repository (but not Apple) the latest Xcode 13.2 dmg and Command Line Tool. The tools are free, but I am not particularly keen to pay Apple. And anyway, I don't intend to do any serious programming work with it (only on FileMaker Pro itself). With this, I like to see the compilation you performed working at my end (unsigned of course, but this is just to check that it works for me). Instructions on how to do this right on the latest Xcode is important (in case it is different from previous versions).
4. You may use your developer's certificate from Apple to sign the plug-ins. This will hopefully solve the GateKeeper issue. When doing so, there should be no restrictions of any kind (based on time, type of macOS version etc.). I want the plug-ins to work forever (or as long as Apple chooses to stay on the Apple Silicon chips).
To save you time, the Intel version for Windows and old world Macs won't need re-compiling, unless you are feeling generous at this time of year to sign the Intel-based plug-ins for Windows and old world Intel Macs on my behalf so I don't get hassled by Gatekeeper. This is entirely optional. What's is critical here is dealing with the M1 Macs.
Once I have workable plug-ins that I can throw straight into the Extensions folder of FileMaker Pro for the M1 Macs, I definitely won't need to re-compile again, or while Apple decides to stay on the Apple Silicon chip technology. This is a once off re-compilation job, which is why I personally don't care much about giving away the source code. It is better to share and let each person achieve their own goals with it, but do refrain from selling the code in its original state as I do have rights to selling it myself when I distribute my FileMaker solutions to clients.
Thanks.
Yes, I can hear you salivating. You definitely will have access to the source code in this project and all libraries that I used to create the Intel version. There is one proviso I should mention: please keep the source code for your own personal use (do not resell etc.). In return for giving you the source code, I require from you the following:
1. My fingers are crossed that all libraries are still compatible and can be used to compile the source code for use on M1. If not, please update the relevant libraries as you require. I don't think there is any need to tweak the source code as it has worked perfectly, but your experience will tell me if this is true or not. Let me know of any changes required. I am assuming that this is a straightforward re-compilation of the source code for use on the M1 Macs.
2. Send back to me only those files and libraries that had to be changed so I can keep my archive of the source code and libraries up-to-date.
3. Can you also send me a download link from DropBox or some other file repository (but not Apple) the latest Xcode 13.2 dmg and Command Line Tool. The tools are free, but I am not particularly keen to pay Apple. And anyway, I don't intend to do any serious programming work with it (only on FileMaker Pro itself). With this, I like to see the compilation you performed working at my end (unsigned of course, but this is just to check that it works for me). Instructions on how to do this right on the latest Xcode is important (in case it is different from previous versions).
4. You may use your developer's certificate from Apple to sign the plug-ins. This will hopefully solve the GateKeeper issue. When doing so, there should be no restrictions of any kind (based on time, type of macOS version etc.). I want the plug-ins to work forever (or as long as Apple chooses to stay on the Apple Silicon chips).
To save you time, the Intel version for Windows and old world Macs won't need re-compiling, unless you are feeling generous at this time of year to sign the Intel-based plug-ins for Windows and old world Intel Macs on my behalf so I don't get hassled by Gatekeeper. This is entirely optional. What's is critical here is dealing with the M1 Macs.
Once I have workable plug-ins that I can throw straight into the Extensions folder of FileMaker Pro for the M1 Macs, I definitely won't need to re-compile again, or while Apple decides to stay on the Apple Silicon chip technology. This is a once off re-compilation job, which is why I personally don't care much about giving away the source code. It is better to share and let each person achieve their own goals with it, but do refrain from selling the code in its original state as I do have rights to selling it myself when I distribute my FileMaker solutions to clients.
Thanks.