Uic, exe error 1

uic, exe error 1

Hello! I have tried to build my test project using Visual Studio 2017 version 15.9.17 with Qt VS Tools. It fails with uic error. The project project is copied from computer A to computer B got error: "Error starting process C:\Qt\Qt5.14.2\5.14.2\msvc2017_64\bin\uic.exe. It fails with uic error. I use Qt 5.13.1 on Windows 10. Error description: Severity Code Description Project File Line Suppression State Error 1.

Are: Uic, exe error 1

Uic, exe error 1
Uic, exe error 1
Runtime error r6002
Notti del terrore fotos

Thread: what is this error?

Computers are deterministic: if it works one moment, and nothing changes, then it will work the next moment too. The corollary is that something must have changed between when it worked and when it did not, exe error 1. Just adding a push button has caused the make program to rebuild the corresponding UI file. warning checksum bios error Unfortunately for you, either your Makefile or your environment are badly broken and it cannot find the UI compiler (uic), exe error 1. You have an odd, non-standard set of directory paths so only you can determine exactly what is broken.

qmake is a program that is part of Qt, exe error 1. You find it in the Qt bin directory, exe error 1. Its the thing to that reads and acts on your project (PRO) file to produce a Makefile for a make utility. If you use the wrong uic of qmake, copy a Makefile from another system, or move Qt after install then you can get the sort of problems you are experiencing.

In Qt Creator you want to select the option to Rebuild All from the build menu.

(C++) How to cross-compile a Qt Creator project from Ubuntu to a windows executable: example 4: any application, changing makefile

Go back to Richel Bilderbeek's homepage.

Go back to Richel Bilderbeek's C++ page.

 

 

 

 

 

 

This is example 4, exe error 1 a failed attempt of answering the Qt FAQHow to cross-compile a Qt Creator project from Ubuntu to a windows executable?.

 

 

 

 

 

Project information

 

The project is a standard Hello World program.

 

 

 

 

 

Process

 

Running the following command in the same folder as the .pro file, generates some makefiles:

 

 

As [1] uic, I also typed the following:

 

And then I typed:

 

 

Screen output:

 

 

[ui_dialog.h] Error 127 is a known (yet unsolved) error.

 

 

 

 

 

References

 

 

 

 

 

[1] http://lukast.mediablog.sk/log/?p=155

 

 

 

 

 

 

 

Go back to Richel Bilderbeek's C++ page.

Go back to Richel Bilderbeek's homepage.

 

Valid XHTML 1.0 Strict

Current Process for Building Ostinato on WinXP or Win7

cbro.@gmail.com's profile photo

[email protected]

unread,
May 8, 2014, 10:11:06 PM5/8/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected]

PEASE!!!

I have spent months and have tried hundreds of exe error 1 methods of attempting to build Ostinato and have never once exe error 1 close to it building successfully! All documentation I have found assumes too much or is absolutely wrong or out of date.  Assume that the audience is ONLY Windows literate, Meaning someone like me who is NOT overly familiar with UNIX or any other OS and has no clue how MinGW, Protobuf, or QT  works, could someone, for goodness sake, PLEASE create an UPDATED document stating exactly step by step the process required to build Ostinato using QT Creator on Windows XP or 7 so that people, like me, can begin to modify it to meet our needs?

Carlos G Mendioroz's profile photo

Carlos G Mendioroz

unread,
May 9, 2014, 2:43:49 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], [email protected]

You have to be kidding.
If you really spent months without saying anything at the first problem
and your first exe error 1 is this rude, you have slim chances to get it
working. This is one man work with the help of some who brought some
code.
Why don't you do the first step creating a document stating exactly what
problem you found or where something is wrong so you help a bit ?

-Carlos

[email protected]@ 08/05/2014 15:11 -0300 dixit:
> --
> Get Ostinato News and Updates on Twitter - Follow @ostinato
> (http://twitter.com/ostinato)
> exe error 1
> You received this message because you are subscribed to the Google
> Groups "ostinato" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, uic, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/ostinato?hl=en
> ---
> You received this message because you are subscribed to the Google
> Groups "ostinato" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected]
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout.

--
Carlos G Mendioroz <[email protected]> LW7 EQI Argentina
cbro.@gmail.com's profile photo

[email protected]

unread,
May 9, 2014, 2:53:59 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have exe error 1 to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], [email protected]



On Thursday, May 8, 2014 2:11:06 PM UTC-4, exe error 1, [email protected]:
PEASE!!!

I have spent months and have tried uic of different methods of attempting to build Ostinato and have never once come close to it building successfully! All documentation I have found assumes too much or is absolutely wrong or out of date.  Assume that the audience is ONLY Windows literate, Meaning someone like me who is NOT overly familiar with UNIX or any other OS and has no clue how MinGW, Protobuf, or QT  works, could someone, for goodness sake, exe error 1, PLEASE create an UPDATED document stating exactly step by step the process required to build Ostinato using QT Creator uic Windows XP or 7 so that people, like me, uic, can begin to modify it to meet our needs?

The reason I am just now asking (after trying for so long) for help is that I always find a way to get something to work eventually and this is just confounding me!

I have tried just about every version of QT, MinGW, Protobuf, and every other tool!

Here is just one instance of some compile output from QT:

13:49:26: Running steps for project ost.

13:49:26: Configuration unchanged, skipping qmake step.

13:49:26: Starting: "C:\MinGW\MinGW-gcc440_1\mingw\bin\mingw32-make.exe"

cd extra/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra'

cd qhexedit2/ && c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.Debug

mingw32-make[3]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

g++ -c -g -Wall -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/commands.o ./././Ostinato/extra/qhexedit2/src/commands.cpp

g++ -c -g -Wall -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/qhexedit.o ./././Ostinato/extra/qhexedit2/src/qhexedit.cpp

g++ -c -g -Wall -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/qhexedit_p.o ./././Ostinato/extra/qhexedit2/src/qhexedit_p.cpp

g++ -c -g uic -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/xbytearray.o ./././Ostinato/extra/qhexedit2/src/xbytearray.cpp

C:/Qt/4.7.0/bin/moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -D__GNUC__ -DWIN32 ./././Ostinato/extra/qhexedit2/src/qhexedit.h -o debug/moc_qhexedit.cpp

g++ -c -g -Wall -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/moc_qhexedit.o debug/moc_qhexedit.cpp

C:/Qt/4.7.0/bin/moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -D__GNUC__ -DWIN32 ./././Ostinato/extra/qhexedit2/src/qhexedit_p.h -o debug/moc_qhexedit_p.cpp

g++ -c -g -Wall -frtti -fexceptions -mthreads -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'./././Qt/4.7.0/include/QtCore' -I'./././Qt/4.7.0/include/QtGui' -I'./././Qt/4.7.0/include' -I'./././Qt/4.7.0/include/ActiveQt' -I'debug' -I'./././Ostinato/extra/qhexedit2' -I'.' -I'./././Qt/4.7.0/mkspecs/win32-g++' -o debug/moc_qhexedit_p.o debug/moc_qhexedit_p.cpp

ar -ru debug/libqhexedit2.a debug/commands.o debug/qhexedit.o debug/qhexedit_p.o debug/xbytearray.o debug/moc_qhexedit.o debug/moc_qhexedit_p.o

mingw32-make[3]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/extra'

ar: creating debug/libqhexedit2.a

cd rpc/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.pbrpc

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.pbrpc.Debug

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

g++ -c exe error 1 -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' uic -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'././Ostinato/rpc' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -o debug/rpcserver.o ././Ostinato/rpc/rpcserver.cpp

g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'././Ostinato/rpc' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -o debug/pbrpcchannel.o ././Ostinato/rpc/pbrpcchannel.cpp

C:/Qt/4.7.0/bin/moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'././Ostinato/rpc' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -D__GNUC__ -DWIN32 ././Ostinato/rpc/rpcserver.h -o debug/moc_rpcserver.cpp

g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'././Ostinato/rpc' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -o debug/moc_rpcserver.o debug/moc_rpcserver.cpp

C:/Qt/4.7.0/bin/moc.exe -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'././Ostinato/rpc' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -D__GNUC__ -DWIN32 ././Ostinato/rpc/pbrpcchannel.h -o debug/moc_pbrpcchannel.cpp

g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DHAVE_REMOTE -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' bwin. fatal error. the application will shutdown -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -o debug/moc_pbrpcchannel.o debug/moc_pbrpcchannel.cpp

ar -ru debug/libpbrpc.a debug/rpcserver.o debug/pbrpcchannel.o debug/moc_rpcserver.o debug/moc_pbrpcchannel.o

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

ar: creating debug/libpbrpc.a

cd common/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.ostproto

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/common'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.ostproto.Debug

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/common'

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/pcapfileimport.ui -o ui_pcapfileimport.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/mac.ui -o ui_mac.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/payload.ui -o ui_payload.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/eth2.ui -o ui_eth2.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/dot3.ui -o ui_dot3.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/llc.ui -o ui_llc.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/snap.ui -o ui_snap.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/vlan.ui -o ui_vlan.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/arp.ui -o ui_arp.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/ip4.ui -o ui_ip4.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/ip6.ui -o ui_ip6.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/icmp.ui -o ui_icmp.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/gmp.ui -o ui_gmp.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/tcp.ui -o ui_tcp.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/udp.ui -o ui_udp.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/textproto.ui -o ui_textproto.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/userscript.ui -o ui_userscript.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/hexdump.ui -o ui_hexdump.h

c:/Qt/4.7.0/bin/uic.exe ././Ostinato/common/sample.ui battlefield 3 runtime error ui_sample.h

g++ -c -g -frtti -fexceptions -mthreads -Wall -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_SCRIPT_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -I'././Qt/4.7.0/include/QtCore' -I'././Qt/4.7.0/include/QtNetwork' -I'././Qt/4.7.0/include/QtGui' -I'././Qt/4.7.0/include/QtXml' -I'././Qt/4.7.0/include/QtScript' -I'././Qt/4.7.0/include' -I'././Ostinato/extra/qhexedit2/src' -I'././Qt/4.7.0/include/ActiveQt' -I'debug' -I'.' -I'././Ostinato/common' -I'.' -I'././Qt/4.7.0/mkspecs/win32-g++' -o debug/ostprotolib.o ././Ostinato/common/ostprotolib.cpp

protoc --cpp_out=. --proto_path=. ././Ostinato/common/protocol.proto

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/common'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/common'

process_begin: CreateProcess(NULL, protoc --cpp_out=. --proto_path=. ././Ostinato/common/protocol.proto. .) failed.

make (e=2): The system cannot find the file specified.

mingw32-make[2]: *** [protocol.pb.h] Error 2

mingw32-make[1]: *** [debug] Error 2

mingw32-make: *** [sub-common-ostproto-pro-make_default-ordered] Error 2

13:50:44: The process "C:\MinGW\MinGW-gcc440_1\mingw\bin\mingw32-make.exe" exited with code 2.

Error while building/deploying project ost (kit: MINgwoldgcc)

When executing step 'Make'

13:50:44: Elapsed time: 01:19.

Srivats P's profile photo

Srivats P

unread,
May 9, 2014, uic, 7:06:41 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], ostinato

@cbrogley

I can understand you are frustrated with your failed attempts at
building Ostinato.

If you have a problem that you can't solve yourself, search the
Ostinato mailing list's archives followed by a generic google search.
There's a very good chance that someone else has also faced the uic
problem - may be with Ostinato or may be with some other code, but the
problem and its solution is likely to be the same.

If a search doesn't help, uic, ask on the mailing list. Nicely.

Provide as much information as possible. Specify what is your exact
problem, what have you tried, what didn't work, what platform error 49 hp 2055 are
on and anything else that you think could be useful - you have to put
yourself in the other person's shoes and think about what information
may be needed. If you expect other people to take the time to help
you, you need to take the time to provide all the information.

It is always more productive to ask for specific help rather than
generic i.e. instead of asking for procedure to build (generic), say
you tried the procedure given at <specify-url> and at step
#<specify-number> you face a problem (specific). Then provide the
problem details.

For the failed build output that you provided, the problem is that
make couldn't find the protobuf compiler protoc, exe error 1. You either don't have
protobuf installed or protoc is not in the path. And autocad 2008 error graphics not generated you had
searched the mailing list archives, you would have found your answer
as someone has asked the same question earlier.

Solving build problems over email is a highly inefficient process, so
I highly recommend that you take help of a knowledgeable developer
friend or colleague locally to help you. Building open-source software
on Windows platforms is not easy and you have to be prepared to be
frustrated and have to put the time to learn things on the way. I did.
When I first started working on Ostinato, exe error 1, I did not know anything
about Qt or protobuf either. And my primary development platform for
Ostinato is Windows.

Srivats

> --
> Get Ostinato News and Updates on Twitter - Follow @ostinato
> (http://twitter.com/ostinato)
> ---------
> You received this message because you are subscribed to the Google Groups
> "ostinato" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/ostinato?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "ostinato" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to [email protected]

> For more options, visit https://groups.google.com/d/optout.



--

http://ostinato.org/
@ostinato
cbro.@gmail.com's profile photo

[email protected]

unread,
May 9, 2014, exe error 1, 10:06:22 PM5/9/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], [email protected]


Here is another log from another build I attempted:

14:01:41: Running steps for project ost.

14:01:41: Configuration unchanged, skipping qmake step.

14:01:41: Starting: "C:\MinGW\MinGW-gcc440_1\mingw\bin\mingw32-make.exe"

cd extra/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra'

cd qhexedit2/ && c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.Debug

mingw32-make[3]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

mingw32-make[3]: Nothing to be done for `first'.

mingw32-make[3]: Leaving uic `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/extra/qhexedit2'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/extra'

cd rpc/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.pbrpc

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.pbrpc.Debug

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

mingw32-make[2]: Nothing to be done for uic Leaving directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/rpc'

cd common/ && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.ostproto

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/common'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.ostproto.Debug

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/common'

mingw32-make[2]: Nothing to be done for `first'.

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/common'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/common'

cd uic && C:/MinGW/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.drone

mingw32-make[1]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/server'

c:/mingw/MinGW-gcc440_1/mingw/bin/mingw32-make -f Makefile.drone.Debug

mingw32-make[2]: Entering directory `c:/build-ost-MINgwoldgcc-Debug/server'

mingw32-make[2]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/server'

mingw32-make[1]: Leaving directory `c:/build-ost-MINgwoldgcc-Debug/server'

mingw32-make[2]: *** No rule to make target `drone_main.cpp', needed by `version.cpp'. Stop.

mingw32-make[1]: *** [debug] Error 2

mingw32-make: *** [sub-server-drone-pro-make_default-ordered] Error 2

14:02:05: The process "C:\MinGW\MinGW-gcc440_1\mingw\bin\mingw32-make.exe" exited with code 2.

Error while building/deploying project ost (kit: MINgwoldgcc)

When executing step 'Make'

14:02:05: Elapsed time: 00:24.

Srivats P's profile photo

Srivats P

unread,
May 12, 2014, uic, 8:07:37 PM5/12/14

Reply to author

Sign in to exe error 1 to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to chris brogley, ostinato

Looks like make did not find drone_main.cpp in
c:/build-ost-MINgwoldgcc-Debug/server directory.

Is it present in that directory?

If it is present, change your QtCreator Build Settings to uncheck the
"Shadow Build" checkbox and try again.

Srivats
cbro.@gmail.com's profile photo

[email protected]

unread,
May 13, 2014, 4:41:23 PM5/13/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], chris brogley

Unchecking the "Shadow Build" helped alot! I was actually able to get that instance to build but both the drone and Ostinato crash w/out any error uic using the debugger it just stopped unexpectedly.  I think there is some version incompatibilities. I had alot of errors with the version stuff related to version.cpp, which never seems to get created during the build, I just hard coded dummy version/revision info to get past the error so it would build successfully. 

Could you tell me the best combination of prerequisite versions of MinGW, QT, QT Creator, exe error 1, and Protobuf. (i.e. a good qt creator kit :) )


Thanks for all of your time by the way! 

Srivats P's profile photo

Srivats P

unread,
May exe error 1, 2014, 7:02:38 PM5/13/14

Reply to author

Sign in l7 critical error 84 42 reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the uic message

to chris brogley, exe error 1, ostinato

Do Ostinato and Drone print something before crashing?

Versions of MinGW and QtCreator should not matter.

Minimum versions for other prerequisites like Qt, Protobuf etc. is
listed uic the BuildingFromSource wiki page.

I would exe error 1 you start with a fresh new tarball (or hg clone) and re-try.

Srivats

PS - It would also be good if you could subscribe to the mailing list
so that I don't have to keep moderating your emails, exe error 1.
will.@gmail.com's profile photo

[email protected]

unread,
May 14, 2014, 6:34:52 PM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], chris brogley

@Chris I tried for weeks to build Ostinato to no avail. I have deep respect for those who provide great tools like Ostinato open source, so I'm not complaining! But like yourself I could never figure out the exact versions of QT, protobuf, MinGw that would all play nicely together. So if you get the project to build, exe error 1, please please post back so I can follow your lead.

cbro.@gmail.com's profile photo

[email protected]

unread,
May 14, 2014, uic, 7:06:59 PM5/14/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], chris brogley

There was no debug information nvidia system error install archives failed either of the executables crashed other than it stating that they unexpectedly stopped. Even when run standalone they would just launch and stop without error. 

I have recently tried new tars and various versions of MinGW, exe error 1, QT, protobuf (I was finally able to build 2.3 fixing the subprocess.h file that was not working in the source download that is available), and still cannot get a working build. I will continue to experiment with all the variables until I find a working kit. 



On Tuesday, uic, May 13, 2014 11:02:38 AM UTC-4, Srivats P wrote:

cbro.@gmail.com's profile photo

[email protected]

unread,
May 19, 2014, 9:43:17 PM5/19/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report uic as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], chris brogley

Ok Using QT 4.6.4/MinGW 4.4.0 Protobuf 2.4.1 I was able to get it all to compile successfully without any errors, but when I run either Drone or Ostinato they crash:

Starting C:\Ostinato051\client\debug\ostinato.exe.

The program has unexpectedly finished.

C:\Ostinato051\client\debug\ostinato.exe crashed

Starting C:\Ostinato051\client\debug\ostinato.exe.

The program has unexpectedly finished.

C:\Ostinato051\client\debug\ostinato.exe crashed


On Tuesday, May 13, 2014 11:02:38 AM UTC-4, Srivats P wrote:
Srivats P's profile photo

Srivats P

unread,
May 20, 2014, uic, 6:24:52 PM5/20/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to chris brogley, ostinato

Chris,

Please join the mailing list to continue the conversation, uic.

Srivats
Srivats P's profile photo

Srivats P

unread,
May 21, 2014, 8:06:17 PM5/21/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to chris brogley, ostinato

Chris,

Some suggestions -
* Try using the debugger to see where it crashes
* If it crashes very early on even before main(), maybe it can't find
the DLLs it depends upon
* Are you able to compile and run any of the sample Qt projects?
* Are you using the release or debug configuration for your build -
try with both
* There could also be a problem of binary compatibility between the
various libraries - did you install the mingw or ViStudio versions of
Qt? Are you using the compiler that was installed by Qt or did you
download/install mingw separately. You need to use the same compiler
as what was included in the Qt distribution (assuming you are using
the pre-built DLLs in the download and did not compile Qt yourself) to
compile Ostinato and all its dependencies, uic.
* Do a google search for the error and see if any pointers there help.


Srivats

On Mon, exe error 1, May 19, 2014 at 11:13 PM, <[email protected]> wrote:

chris brogley's profile photo

chris brogley

unread,
May 22, 2014, 7:55:48 PM5/22/14

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], chris brogley

Hi :)

1. I tried and I immediately get Debugging has failed.

2. I suspect some issue with protobuf. Version 2.4.1 is the only version that will even finish compiling without all kinds of errors

3. Yes as well as example mingw projects

4, uic. Tried Both

5. I have only installed QT with mingw versions making sure to match the versions of mingw matches the version that QT expects when installing QT.

6. I have Googled til my eyes are bugged out and have made little progress  - the most frustrating thing is that I finally get it to build even without any Warnings and still it crashes. I really think it has something to do with the Protocol buffers but I have built and rebuilt them countless times as well as used the pre-compiled versions. I tried running the executable on another machine I did get a windows error: Error signature  - ModName: libprotobuf-7.dll.

Why do I have to compile the protobuf library files - why arent they just included in the win32 package?

On a exe error 1 ditch today I installed QT 4.3.3 with Mingw 3.2.0 using clean version of Ostinato 0.5.1 src and several versions of protobuf but even that failed miserably:  

C:\Ostinato051>dir

 Volume in drive C is Windows

 Volume Serial Number is 52E8-0B83

 Directory of C:\Ostinato051

05/22/2014  09:12 AM    <DIR>          .

05/22/2014  09:12 AM    <DIR>          .

07/30/2012  09:26 AM                78 .vimrc

05/22/2014  09:06 AM    <DIR>          client

05/22/2014  09:17 AM    <DIR>          common

07/30/2012  09:26 AM            35,147 COPYING

05/22/2014  09:12 AM    <DIR>          extra

07/30/2012  09:26 AM               361 install.pri

05/22/2014  09:12 AM            18,321 Makefile

07/30/2012  09:26 AM               154 ost.pro

07/30/2012  09:31 AM         1,648,640 ostinato-src-0.5.1.tar

07/30/2012  09:26 AM             1,097 protobuf.pri

05/22/2014  09:12 AM    <DIR>          rpc

05/22/2014  09:18 AM    <DIR>          server

05/22/2014  09:00 AM    <DIR>          test

07/30/2012  09:28 AM               773 version.pri

               8 File(s)      1,704,571 bytes

               8 Dir(s)  772,620,636,160 bytes free

C:\Ostinato051>qmake

C:\Ostinato051>make

cd extra\ && mingw32-make -f Makefile

mingw32-make[1]: Entering directory `C:/Ostinato051/extra'

cd qhexedit2\ && mingw32-make -f Makefile

mingw32-make[2]: Entering directory `C:/Ostinato051/extra/qhexedit2'

mingw32-make -f Makefile.Debug

mingw32-make[3]: Entering directory `C:/Ostinato051/extra/qhexedit2'

mingw32-make[3]: Nothing to be done for `first'.

mingw32-make[3]: Leaving directory `C:/Ostinato051/extra/qhexedit2'

mingw32-make[2]: Leaving directory `C:/Ostinato051/extra/qhexedit2'

mingw32-make[1]: Leaving directory `C:/Ostinato051/extra'

cd rpc\ && mingw32-make -f Makefile.pbrpc

mingw32-make[1]: Entering directory `C:/Ostinato051/rpc'

mingw32-make -f Makefile.pbrpc.Debug

mingw32-make[2]: Entering directory `C:/Ostinato051/rpc'

mingw32-make[2]: Nothing to be done for `first'.

mingw32-make[2]: Leaving directory `C:/Ostinato051/rpc'

mingw32-make[1]: Leaving directory `C:/Ostinato051/rpc'

cd common\ && mingw32-make -f Makefile.ostproto

mingw32-make[1]: Entering directory `C:/Ostinato051/common'

mingw32-make -f Makefile.ostproto.Debug

mingw32-make[2]: Entering directory `C:/Ostinato051/common'

mingw32-make[2]: Nothing to be done for `first'.

mingw32-make[2]: Leaving directory `C:/Ostinato051/common'

mingw32-make[1]: Leaving directory `C:/Ostinato051/common'

cd server\ && mingw32-make -f Makefile.drone

mingw32-make[1]: Entering directory `C:/Ostinato051/server'

mingw32-make -f Makefile.drone.Debug

mingw32-make[2]: Entering directory `C:/Ostinato051/server'

g++ -enable-stdcall-fixup -Wl,-enable-auto-import -Wl,-enable-runtime-pseudo-reloc -mthreads -Wl -Wl,-subsystem,windows

-o debug\drone.exe object_script.drone.Debug  -L"c:\Qt\4.3.3\lib" -lmingw32 -lqtmaind -lwpcap -lpacket -L./common/debug

 -lostproto -L./rpc/debug -lpbrpc -lm -lprotobuf -L./extra/qhexedit2/debug/ -lqhexedit2 -lQtScriptd4 -lQtGuid4 -lQtNet

workd4 -lQtCored4

C:\MinGW320\bin\.\lib\gcc\mingw32\3.4.2\.\.\.\.\mingw32\bin\ld.exe: cannot find -lQtScriptd4

collect2: ld returned 1 exit status

mingw32-make[2]: *** [debug\drone.exe] Error 1

mingw32-make[2]: Leaving directory `C:/Ostinato051/server'

mingw32-make[1]: *** [debug] Error 2

mingw32-make[1]: Leaving directory `C:/Ostinato051/server'

mingw32-make: *** [sub-server-drone-pro-make_default-ordered] Error 2

C:\Ostinato051>

On Wednesday, May 21, 2014 12:06:17 PM UTC-4, Srivats P wrote:
Chris,

Some suggestions -
1. Try using the debugger to see where uic crashes
2. If it crashes very early on even before main(), maybe it can't find

3, uic. Are you able to compile and run any of the sample Qt projects?
4, uic. Are you using uic release or debug configuration for your build -
try with both
5, uic. There could also be a problem of binary compatibility between the

various libraries - did you install the mingw or ViStudio versions of
Qt? Are you using the compiler that was installed by Qt or did you
download/install mingw separately. You need to use the same compiler
as what was included in the Qt distribution (assuming you are using
the pre-built DLLs in the download and did not compile Qt yourself) to
compile Ostinato and all its dependencies.

6. Do a google error 035 argument type mismatch for the error and see if any pointers there help.

Srivats P's profile photo

Srivats P

unread,
May 23, 2014, 7:09:14 PM5/23/14

QT - UIC.exe error #7436

Sometime in the last 4 months one of the MSYS2 updates has caused my current QT app to fail building. I am running the latest packages as of this morning 13-Dec-2020 (GMT + 10hrs, Australia).

Hopefully the relevant versions of canon pixma mp160 error e5 problem packages are:
mingw-w64-x86_64-qt-creator 4.13.2-1
mingw-w64-x86_64-qt5 5.15.1-1
mingw-w64-x86_64-qt5-static 5.15.1-1
mingw-w64-x86_64-cmake 3.19.1-2
mingw-w64-x86_64-make 4.3-1

The problem is that it appears that the uic.exe is not generating the *.h from the *.ui form files. A snippet of the compile output is:
C:/msys64/mingw64/bin/mingw32-make.exe -f Makefile.Debug
mingw32-make[1]: Entering directory 'C:/GM_Work/NSW_X_Decoder_QT'
/C/msys64/mingw64/bin/uic.exe Forms/AGMMA_MultiGame_Form.ui -o build/debug/.ui/ui_AGMMA_MultiGame_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/AGMMA_Peripheral_Form.ui -o build/debug/.ui/ui_AGMMA_Peripheral_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/AGMMA_TITO_TIME_Form.ui -o build/debug/.ui/ui_AGMMA_TITO_TIME_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/CCCE_Logger_Form.ui -o build/debug/.ui/ui_CCCE_Logger_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/CCCE_Transfer_Form.ui exe error 1 build/debug/.ui/ui_CCCE_Transfer_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/CDB_Form.ui -o build/debug/.ui/ui_CDB_Form.h
/C/msys64/mingw64/bin/uic.exe Forms/FDB_Form.ui -o build/debug/.ui/ui_FDB_Form.h
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No exe error 1 file or directory
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
/C/msys64/mingw64/bin/uic.exe Forms/Message_Display_Form.ui -o build/debug/.ui/ui_Message_Display_Form.h
mingw32-make[1]: *** [Makefile.Debug:3974: build/debug/.ui/ui_AGMMA_MultiGame_Form.h] Error 127
mingw32-make[1]: *** Waiting for unfinished jobs.
mingw32-make[1]: *** [Makefile.Debug:3978: build/debug/.ui/ui_AGMMA_Peripheral_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
mingw32-make[1]: *** [Makefile.Debug:3982: build/debug/.ui/ui_AGMMA_TITO_TIME_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
mingw32-make[1]: *** [Makefile.Debug:3986: build/debug/.ui/ui_CCCE_Logger_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
mingw32-make[1]: *** [Makefile.Debug:3990: build/debug/.ui/ui_CCCE_Transfer_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
mingw32-make[1]: *** [Makefile.Debug:3994: build/debug/.ui/ui_CDB_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file uic directory
mingw32-make[1]: *** [Makefile.Debug:3998: build/debug/.ui/ui_FDB_Form.h] Error 127
/usr/bin/sh: /C/msys64/mingw64/bin/uic.exe: No such file or directory
mingw32-make[1]: *** [Makefile.Debug:4002: build/debug/.ui/ui_Message_Display_Form.h] Error 127
mingw32-make[1]: Leaving directory 'C:/GM_Work/NSW_X_Decoder_QT'
mingw32-make: *** [Makefile:45: debug] Error 2

Any ideas on how to fix this?
Should I try and install the previous version of QT creator 4.12.4 and see if this fixes it?

1 Comments

Leave a Comment