On Saturday, May 29, 2021 at 8:17:00 PM UTC-4, Chris Burrows wrote:
> On Saturday, May 29, 2021 at 10:59:27 PM UTC+9:30, drro...@gmail.com
> > On Friday, May 28, 2021 at 2:54:25 PM UTC-4, bri...@glmotorsports.net
> > > On Wednesday, April 28, 2021 at 7:19:38 PM UTC-4, rob wrote:
> > > > Not for me. My code uses the TextWindows module. It compiles but still fails to link, saying I have undefined symbols from WINUSER and WIN32, both are part of the Windows interface
> > > I see that the latest ADW update was posted to modula2.org
just a few days ago. Have you had a chance to grab it and give it a try yet?
> > I did, and it does not work, either. I do not see a version that is later than Mar 8, 2021. I tried that before I posted in April.
> > Still no-go
> Have you tried checking the 'Allow undefined symbols' in Linker Options > Main?
still no-go. Now an .exe is created, but does nothing when I try to run it.
I noticed that the behavior of the M2 environment is different. Back in the day, I would install it, and upon first opening it would compile it's run time library. Stonybrook's would do that (and still does) in my VM of WinXP. This is working for me.
It doesn't do that now under Win10. Every time I open the ADW environment (ASCII in my case), it remains on the sources of the runtime library, and it seems to be expecting me to do something.
Not knowing what to do, I click on the compile all button. That compiles all, AFAICT. I do that for each of the 4 choices, ie, rtl-win-amd64, rtl-win-ia32, rtldll-win-amd64 and rtldll-win-ia32.
I have no idea if that's what it expects me to do, or even if it is expecting me to do anything.
My code compiles, but fails to link. Either I get the undefined symbols from WINUSER and WIN32, or sometimes I get an error saying that i need to compile WINUSER.
It still does not work for me on Win10, now at 21H1