Xcode FileMaker Plug-in Rebuild & Debug
Budget: $750 – $1,500 AUD
I need an expert to re-build and debug my Xcode FileMaker plug-ins (written in C++) using the provided source code. There are a total of 6 plug-ins, and most are quite simple, with the exception of FileManipulator plug in. The final product should be 6 successfully built plug-ins that can run on Apple Silicon Macs and FileMaker Pro app (including the latest or version 21.0.2 with macOS Sonoma where I see my old Intel plug-ins no longer showing up in FileMaker Pro despite Rosetta running and tell it to run the plug-ins in emulation mode).
Key Tasks:
- Re-build the plug-ins for compatibility with Apple Silicon and visible in the FileMaker Pro app.
- If it is possible, it would be outstanding if you could create a Universal plug-in using existing Intel libraries, but this is not essential.
- Update any relevant libraries (or, if needed, replace with new libraries) and fix source code as needed to enable existing functions of the plug-ins to work.
- One plug-in may need an update for SFTP as servers nowadays are becoming more secure.
The ideal candidate for this project should have extensive experience with Xcode, FileMaker plug-ins, and debugging. Knowledge of Apple Silicon architecture and familiarity with the latest FileMaker Pro app is advisable, but not essential.
If you do not have FileMaker Pro , this can be provided if you need to check plug-ins are properly loaded in the Preferences section and the functions are visible in scripts created through the Scripts menu.
Also provided to the successful freelancer(s) is the updated FileMaker Plug-in SDK as of December 2024, with headers and resources updated appropriately. Since it has been a long time since the source code of the plug-ins have been built, the freelancer will need to fix any bugs and errors that may appear during the new build process.
Finally, for the project to be considered complete, I will need to be able to test the build process at my end and see the successful build of the plug-ins using my current Xcode (version 13.2.1). NOTE: I may update Xcode if recommended by the freelancer so long as the build produces plug-ins that are compatible on older macOS versions from Monterey or higher.
As for code-signing, this is unnecessary. If you want to code-sign them that is fine, but please do not put any restrictions, such as time-limits or which version of macOS or FileMaker Pro I can use them. The plug-ins must work as flexible as Apple will allow through Xcode for at the life of the plug-ins (until such time as Claris decides to remove the plug-in feature from all future FileMaker Pro apps).
Thanks, and good luck!
Attached is a screenshot of the FileMaker Pro plug-ins folder showing how they are organised- plug-ins source code at bottom, FileMaker plug-in template in the middle, and general information at the top. Technically you should be able to open up a plug-in folder, find the Xcode project file, open it, and start building, but under Apple Silicon and latest Xcode, various changes are needed, which is where your programming expertise is required.
Key Tasks:
- Re-build the plug-ins for compatibility with Apple Silicon and visible in the FileMaker Pro app.
- If it is possible, it would be outstanding if you could create a Universal plug-in using existing Intel libraries, but this is not essential.
- Update any relevant libraries (or, if needed, replace with new libraries) and fix source code as needed to enable existing functions of the plug-ins to work.
- One plug-in may need an update for SFTP as servers nowadays are becoming more secure.
The ideal candidate for this project should have extensive experience with Xcode, FileMaker plug-ins, and debugging. Knowledge of Apple Silicon architecture and familiarity with the latest FileMaker Pro app is advisable, but not essential.
If you do not have FileMaker Pro , this can be provided if you need to check plug-ins are properly loaded in the Preferences section and the functions are visible in scripts created through the Scripts menu.
Also provided to the successful freelancer(s) is the updated FileMaker Plug-in SDK as of December 2024, with headers and resources updated appropriately. Since it has been a long time since the source code of the plug-ins have been built, the freelancer will need to fix any bugs and errors that may appear during the new build process.
Finally, for the project to be considered complete, I will need to be able to test the build process at my end and see the successful build of the plug-ins using my current Xcode (version 13.2.1). NOTE: I may update Xcode if recommended by the freelancer so long as the build produces plug-ins that are compatible on older macOS versions from Monterey or higher.
As for code-signing, this is unnecessary. If you want to code-sign them that is fine, but please do not put any restrictions, such as time-limits or which version of macOS or FileMaker Pro I can use them. The plug-ins must work as flexible as Apple will allow through Xcode for at the life of the plug-ins (until such time as Claris decides to remove the plug-in feature from all future FileMaker Pro apps).
Thanks, and good luck!
Attached is a screenshot of the FileMaker Pro plug-ins folder showing how they are organised- plug-ins source code at bottom, FileMaker plug-in template in the middle, and general information at the top. Technically you should be able to open up a plug-in folder, find the Xcode project file, open it, and start building, but under Apple Silicon and latest Xcode, various changes are needed, which is where your programming expertise is required.