I'm not sure, because SIMBL is GPL.
A:
- Are you linking with any SIMBL libraries or including SIMBL header files? If so, then you would need to have a GPL compatible license for your code.
- Are you modifying SIMBL in any way? If so, you would need to release your changes to SIMBL.
If either of those conditions don't apply, then you are safe from the GPL.
Disclaimer: I am not a lawyer. This is not legal advice.
Yann Ramin
2010-06-14 17:04:34
Thank you, Theatrus!2. I do not modify SIMBL in any way.1. Actually, SIMBL invades in all processes running on Mac OS and allows my module to be dynamically loaded into a particular process which a choose.There're several SIMBL plug-ins which are proprietary and seems like closed source (like the PitHelmet), that's why I'm confused...
iUm
2010-06-14 17:30:17
@iUm: You can always ask the developers of SIMBL as well if you want warm fuzzy feelings about what you are doing.
Yann Ramin
2010-06-14 20:18:27
A:
Here's the answer from the official web-page:
- You can use SIMBL for anything you like.
- You can include the SIMBL.pkg with your distribution, but you need to include the original license and ReadMe files so people know what they are getting.
- If you want more from SIMBL, check out the source and make change suggestions. You can modify the code, but if you release it, you must release the source code as well. On a more general note, please do not distribute a modified version of the code under the SIMBL name -- it would make my life a nightmare. If we can't work your changes into the real SIMBL, give it another fairly different sounding name!
- There is no warranty of any kind.
- If you are using SIMBL in a commercial product, please make a donation to support this project.
iUm
2010-06-16 15:32:44