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

question re: Windows/MSVC support #25

Closed
turtle-dragonfly opened this issue Mar 8, 2024 · 3 comments
Closed

question re: Windows/MSVC support #25

turtle-dragonfly opened this issue Mar 8, 2024 · 3 comments

Comments

@turtle-dragonfly
Copy link
Contributor

I am currently in the process of porting bsdnt to run on Windows, for my local project.

Are you interested in changes like that being merged back into the mainline?

I notice that in older releases, MSVC was supported, but it was removed in fb3037b.

Is it an anti-feature for this project?

I realize that the autoconf/bash-driven configuration for the arch/inline/xxx code is not easy to convert. I'm not planning on dealing with that, just updating the main plain-C codebase to compile under MSVC.

@wbhart
Copy link
Owner

wbhart commented Mar 8, 2024

I'm not really actively maintaining this project at the moment. It's offered as is for anyone interested.

I'm not interested in adding visual solution files back into the project, but I might consider a CMake build that works for MSVC.

One of the issues here is that some of the code is assembly language and this is very toolchain dependent. I'm not keen on making it more difficult to maintain in the future. This project was mainly designed to be a really simple, easy to maintain project which doesn't have terrible performance. Making it all singing and all dancing wasn't a design goal.

@turtle-dragonfly
Copy link
Contributor Author

turtle-dragonfly commented Mar 9, 2024

Ok, thanks. I suppose for now I'll just keep it in my fork, in case anyone wants to reference it.

Related: I've also hit some issues with using 32-bit word_t - various casts to (long) fail, and some other issues. I think that this is meant to be a supported configuration, so would you be interested in those changes?

@wbhart
Copy link
Owner

wbhart commented Mar 9, 2024 via email

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

2 participants