Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any workaround with ILMerge? #145

Open
kratunatami opened this issue Dec 30, 2014 · 6 comments
Open

Any workaround with ILMerge? #145

kratunatami opened this issue Dec 30, 2014 · 6 comments

Comments

@kratunatami
Copy link

Anyone knows any workaround how can i embed tesseract.dll into my application?

I am using the Nuget package, and since version 2.0.0.1 when the Tesseract.Interop was made internal I am not able to embed it in my app as it throws an exception "the interface ILeptonicaAPISignatures should be public"

Any help will be highly appreciated!

@VahidN
Copy link

VahidN commented Dec 30, 2014

Try Fody/Costura

@kratunatami
Copy link
Author

Just tried that, thanks for the share, but had no luck with it as well.. still throwing an exception :(

@charlesw
Copy link
Owner

I could make these public and document that only those classes that are in
the Tesseract namespace are part of the public api. Would that work?
On 31 Dec 2014 08:44, "kratunatami" notifications@github.com wrote:

Just tried that, thanks for the share, but had no luck with it as well..
still throwing an exception :(


Reply to this email directly or view it on GitHub
#145 (comment).

@kratunatami
Copy link
Author

Yes, that might work, however I am not specialist enough to tell if thats the correct thing to do

You can find out about Internalizing with ILMerge here:
http://www.blackwasp.co.uk/ILMergeInternalize.aspx

@charlesw
Copy link
Owner

charlesw commented Jan 8, 2015

Unfortunately you can not internalize these interfaces
(Tesseract.Interop.ILeptonicaApiSignatures and
Tesseract.Interop.ITessApiSignatures) as they need to be public so that a
class can be dynamically created that implements them which resides in a
(different) dynamically generated assembly. That being said you can still
use ILMerge but not with the /internalize option.

On Wed, Dec 31, 2014 at 6:37 PM, kratunatami notifications@github.com
wrote:

Yes, that might work, however I am not specialist enough to tell if thats
the correct thing to do

You can find out about Internalizing with ILMerge here:
http://www.blackwasp.co.uk/ILMergeInternalize.aspx


Reply to this email directly or view it on GitHub
#145 (comment).

@kratunatami
Copy link
Author

I see,ok, thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants