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

Made it so TidyManaged will automatically switch between the 32bit and 64bit version of libtidy. #5

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

freethenation
Copy link

Made it so TidyManaged will automatically switch between the 32bit and 64bit version of libtidy. The 32bit version of libtidy should be named "libtidy32.dll" and the 64bit version of libtidy should be named "libtidy64.dll"

…d 64bit version of libtidy. The 32bit version of libtidy should be named "libtidy32.dll" and the 64bit version of libtidy should be named "libtidy64.dll"
… log. Libtidy used to write its error log to standard out. Also added an overloaded of CleanAndRepair that allows the error log to be written to a stream.
@markbeaton
Copy link
Owner

Hi there - thanks for this. I don't suppose you've tested it on non-Windows platforms? I suppose we can remap the DllImport library names via some sort of Mono-specific configuration in an assembly.config file... although it'd be nice if that wasn't necessary.

Let me know & I'll have a look if you haven't tested already.

Thanks,
Mark

@freethenation
Copy link
Author

I have not tested my changes on mono. My changes should not significantly change how libtidy loads on mono. Something similar to the config section below should work.

<configuration>
<dllmap dll="libtidy32.dll" target="/Users/Mark/Code/Tidy/TestHarness/libtidy32.dylib"/>
<dllmap dll="libtidy64.dll" target="/Users/Mark/Code/Tidy/TestHarness/libtidy64.dylib"/>
</configuration>

Regards,
Richard

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

Successfully merging this pull request may close these issues.

3 participants