I found out what would make wxwidgets work in my GDL build.
If I delete "-Wl,--subsytem,windows -mwindows" flags from the final link,
the program is working! deleting just -mwindows wasn't sufficient, and the
win API libs that this flag brings in are already present.
What this implies, I don't know. Are there good counter-examples to leave
these flags in the wx-config setup?
On Sat, Feb 20, 2016 at 2:13 PM, Greg Jung <[email protected]> wrote:
> I know there are plenty of "works fine for me" stories out there to
> testify
> to for wxWidgets but I'm having bizarre experience trying to link wxW and
> need some ideas about how to debug this.
> I was a happy camper running my mingw-w64-i686 program (GDL) via a
> command console which is started by running msys64/usr/bin/bash.exe --login
> -i; line edit and bash completion were performing things went well that
> way. Call this the "cons" window (.vs. a "pty" window produced by starting
> msys2_shell.bat).
>
> GDL is basically a "console program" in that it starts out like any other
>
>> int main(int argc, char *argv[])
>> {
>> if( atexit( AtExit) != 0) cerr << "atexit registration failed." << endl;
>
> etc.,
> e.g., some simple command-line argument checking and then it proceeds
> to be an interpretive compiler. The user directs execution from a simple
> command line which is affected by readline and ncurses. This is a
> semi-asynchronous input - the program actively polls the command line
> and integrates this into the event handling. Normally, though, it all
> seems pretty
> sequential.
> Graphics windows can be created to make line drawings via plplot, and
> this works as well on windows now as it does with Linux/xlib.
>
> There are third-party libraries attached, the most relevant to the
> aspect that is breaking down is readline/ncurses, plplot, and wxwidgets.
> Only recently have I gotten the wxWidgets portion to function
> on windows at all, its performance on linux using gtk is excellent. We
> are using
> the msw toolset.
> Running from the mingw32/mintty terminal ("pty") the program is working
> "fine" - with the usual deficit of tty- capabilities.
> It works great in the "cons" window if the program is built without access
> to wxwidgets but when wxwidgets is linked in, it fails at the very outset.
> Before I can get a stderr message out.
> ...
>
> So, wxWidgets incorporation is horrendously broken even before it
> has had a chance to execute. But not when it is begun from the pty
> process!
>
>
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
