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
Reintroduce Win-x86 support #874
Comments
Hi @MarcinZiabek -Are we working on this ? My company is considering buying your library but I found it doesn't support x86. |
I have already attempted to compile the library with the x86 architecture. It requires a special toolchain and is not straightforward. Therefore, some research may be necessary to make it work. I will do one more try next week. If anyone decides to share the feedback in this thread, please explain why you need the x86 support and why the x64 is insufficient. It would also be great to learn how you use the library. Thank you for your patience and collaboration! 😄 |
It will be nice to keep x86 support, some old computers exist !! Thanks |
Regarding Feedback: Our software e.g. relies on some external devices which only work with x86. Allthough the architecture is outdated it would be a pain to replace the devices, therefore we still run on x86 and would require it's support for QuestPDF. |
We have same issue, we are using third party libraries which only works with x86. |
Hello, They have 3 computers , and one is only x86 !! It is why I always publish the tool in X86 (.NET Core 8). Thanks a lot, sorry for my english, I am french! |
The |
It worked great on Windows 10 x86. |
It works !Thanks a lot Le 15 mai 2024 03:18, Luis Fernando de Souza Santos ***@***.***> a écrit :
It worked great on Windows 10 x86.
@MarcinZiabek Thank you very much for the fantastic work.
I love this library!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
@MarcinZiabek Edit: Not sure about it but this problems might be caused by the Calling Convention. There are differences between x86 and x64. It might be necessary to specify the CallingConventionAttribute on the DllImport |
Is your feature request related to a problem? Please describe.
Many old devices and free hosting servers have RAM restrictions and only support Win-x86
Describe the solution you'd like
I would really like to see Win-x86 support reintroduced. Yes, it is an old architecture, but it is still widely used on low-cost equipment and servers with free hosting options that have RAM usage restrictions.
The text was updated successfully, but these errors were encountered: