Make it possible to build the C++ version as a library #2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I tried to submit a patch but the button in the 'Pull Requests' tab is always greyed. README.adoc hints that you do not accept direct mail. How can I proceed ?
Regards.
Just found the upload zone below. Posting the patch, in case it might be useful.
This patch adds the following functionalities :
DISCLAIMER : I am not an IT professional, just a hobbyist. I wrote the patch
because it may perhaps be useful to me as a library.
Can't find the patch I just dropped below, don't know how to proceed.
I have written an e-mail to you, we should be able to get this resolved.
I'll try to find a way to prevent such delays in the future.
My bad. My Gitea instance was broken by some of my configuration, should be fixed now.
How to submit a patch ?to Make it possible to build the C++ version as a libraryI don't know. I've "librarified" the program in a separate branch that I've pushed now but I'm not happy with it. C++ is a horrible programming language in terms of libraries and linking.
I think I'll just close this issue for now, since according to our e-mail communication there would be no user for this (sub)change, and one can just fork-exec the current pdf-simple-sign binary to get at the same result anyway. I don't have the time to tinker with this all week.
Still, thank you, you've forced me to put everything /else/ back in order. :)