LibreCAD › LibreCAD-dev

building with Qt 5.5

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

ravas

building with Qt 5.5

I upgraded to Qt 5.5 last week;
and, just to see what would happen, I ran:

1. Build → Run qmake
2. Build → Rebuild All

It seems to build fine but I get:

Starting C:\1B\librecad\windows\LibreCAD.exe...
The program has unexpectedly finished.
C:\1B\librecad\windows\LibreCAD.exe crashed

and from the debugger log:

CALL: RUN ENGINE
<19-exec-run
>=thread-group-started,id="i1",pid="12916"
sThread group i1 created
dTaking notice of pid 12916
>=thread-created,id="1",group-id="i1"
sThread 1 created
>~"[New Thread 12916.0x3230]\n"
s[New Thread 12916.0x3230]
>19^running
dNOTE: ENGINE RUN AND INFERIOR RUN OK
sRunning.
dState changed from EngineRunRequested(7) to InferiorRunOk(11) [master]
dINFERIOR STARTED
sApplication started
>*running,thread-id="all"
dNOTE: INFERIOR STILL RUNNING IN STATE InferiorRunOk.

>=thread-exited,id="1",group-id="i1"
sThread 1 in group i1 exited
>=thread-group-exited,id="i1"
sThread group i1 exited
>19^error,msg="During startup program exited with code 0xc0000139."
dCOOKIE FOR TOKEN 19 ALREADY EATEN (InferiorRunOk). TWO RESPONSES FOR ONE COMMAND?
dNOTE: INFERIOR EXITED
dState changed from InferiorRunOk(11) to InferiorExitOk(16) [master]
dState changed from InferiorExitOk(16) to InferiorShutdownOk(19) [master]
dState changed from InferiorShutdownOk(19) to EngineShutdownRequested(20) [master]
dQUEUE: SHUTDOWN ENGINE
sExecutable failed: During startup program exited with code 0xc0000139.

In searching for "During startup program exited with code 0xc0000139"
someone suggested Build Environment → Clear system environment
but I tried that (and rebuilt) with the same outcome.

Any thoughts?

ravas

Re: building with Qt 5.5

Qt 5.5 uses mingw492_32

dxli

Re: building with Qt 5.5

wild guess:

make distclean
and try again

or in Qt-Creator, "build->rebuild all"

ravas wrote

Qt 5.5 uses mingw492_32

ravas

Re: building with Qt 5.5

After trying a bunch of stuff and rebuilding 4-5 times... it still didn't work.
Then I hit the search engines even harder and found:

The 0xC0000135 error means "missing component", which may be a driver or
DLL.
The basic problem was that, at least with gcc 4.4.0 in place, gdb needs the
system-wide PATH setting (Control Panel -> System -> Advanced -> Environment

Variables) to include at least MinGW\bin if not even MSYS\bin (or
MSYS\1.0\bin).

https://sourceforge.net/p/mingw/mailman/message/24840777/

Projects→Run→Run Environment→Base environment for this run configuration
I set it to "Build environment" and the program ran.

The others didn't have the bin path.

God bless that guy...

dxli

Re: building with Qt 5.5

that's why I don't use win32:)

life is short, switch to *nix :(

ravas wrote

After trying a bunch of stuff and rebuilding 4-5 times... it still didn't work.
Then I hit the search engines even harder and found:

The 0xC0000135 error means "missing component", which may be a driver or
DLL.
The basic problem was that, at least with gcc 4.4.0 in place, gdb needs the
system-wide PATH setting (Control Panel -> System -> Advanced -> Environment

Variables) to include at least MinGW\bin if not even MSYS\bin (or
MSYS\1.0\bin).

https://sourceforge.net/p/mingw/mailman/message/24840777/

Projects→Run→Run Environment→Base environment for this run configuration
I set it to "Build environment" and the program ran.

The others didn't have the bin path.

God bless that guy...

ravas

Re: building with Qt 5.5

I've thought about it.
I'll probably upgrade this computer to windows 10 in a year or so,
and try something else with my next computer.
I'll wait until PCIe 3 solid state drives are more common.