-
Notifications
You must be signed in to change notification settings - Fork 123
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
Compiling for Windows Using MSYS #287
Comments
If this is a native compile, it expects cc or gcc to be available. If cross compile, use —host=mingw32 |
Hello!!! Thank you! We've made more progress with our MSYS host. It's actually trying to build now, but we get the following errors (after removing the output redirection in
These all look like trivial things to solve by adding However, after looking at the comment at the top of For our purposes, it looks as though this is the only file that will need to be modified, since it's the only issue with our build... Our actual target is |
Fixes #287 Signed-off-by: Steve Bennett <[email protected]>
OK, that's promising. Because jimsh0.c has to build with no configuration step, it has to take a few shortcuts for autoconfiguration. Looks like we do need a few more checks for your platform. Note that jimsh0.c is build by build-make-bootstrap-jim so the changes should be made there or in the source files. Please try branch bootstrap-jimsh and let me know how it goes. |
We have progress! That fixed the
I have confirmed that we have |
Hmmm, still seem strange to me. GetProcessId() should be included in processthreadsapi.h, which is included by winbase.h Also I would be concerned about CLOCK_REALTIME being defined, but not an int. Are you somehow picking up some cygwin things? |
Oh, I see. Need at least WinXP compatibility. I pushed a small change. With this, jimsh0.exe builds. However I still see a few issues:
|
Just wanted to follow up with you here. I was able to get as far as you said on your updated branch, definitely got Is there anything you need us to check or try out on our end? Thanks for helping to support us, btw. We really appreciate it! |
I'll get to it. I just have limited access to a Windows machine that can run the SDK so when I next get back to it I'll take a look at the outstanding issues. Should be this week. |
See also my previous branch fixing MSYS2 on Jim 0.79, at TheMarkitecht@558f556 |
I did have a bit more of a look at this. Not being able to detect isatty() reliably is annoying. I took a look at how git does it and it is complicated. And the exec issue is messy. In the case I found it was trying to exec a shell script, but that's not a standard windows thing. That is an msys2 thing. So I think there needs to a build for msys2 separate from mingw, but how you detect the difference and what to do about it, I don't know. I don't have reliable access to a Windows platform so I'm inclined to leave all this to someone who does and can test reliably across mingw, msys2 and cygwin. |
Hello jimtcl team!
Long story short, we've added support for this lovely library to the independent Sega Dreamcast SDK, KallistiOS, as another scripting language we wish to offer first-party support for as an add-on library within our package manager system. We already have at least one person using it for an upcoming Dreamcast engine as well.
That being said, KOS and its ports have to build on and get maintained for a myriad of host OSes, Windows, Mac, Linux, BSD, etc... Shortly after officially adding jimtcl, we ran into issues with only a single host platform: MSYS for Windows. It seems as though the configuration script immediately fails with the following error:
I played with this for maybe an hour or so this morning, attempting to manually set the
CC
or evenCC_FOR_BUILD
environment variables to no avail. It seems like no matter what I tried,autosetup-find-tclsh
was unable to find the correct compiler? The following are the binary names for the toolchain used within the environment:I understand that perhaps MSYS has not been a priority or may not even be advertised as working yet. I also saw that everything did work just fine under Cygwin; however, most of our Windows users are using "DreamSDK" (https://www.dreamsdk.org/) which is completely built around MSYS (as Cygwin is typically the problem child for us)... Anyway, I was wondering if you guys had any pointers or advice in terms of just getting things configured? I'm unfamiliar with this particular build system, but once I'm past the configuration stage, if there are any actual code changes required to support MSYS, I believe we should be able to take care of them over here and PR them back to you if you're interested?
Anyway, sorry for the novel. Thank you very much for allowing us to bring Tcl to the Dreamcast. We look forward to showing you the cool stuff we're doing with it!
The text was updated successfully, but these errors were encountered: