Current Process for Building Ostinato on WinXP or Win7

428 views
Skip to first unread message

cbro...@gmail.com

unread,
May 8, 2014, 2:11:06 PM5/8/14
to osti...@googlegroups.com
PEASE!!!
I have spent months and have tried hundreds 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, 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

unread,
May 9, 2014, 6:43:49 AM5/9/14
to cbro...@gmail.com, osti...@googlegroups.com
You have to be kidding...
If you really spent months without saying anything at the first problem
and your first message 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

cbro...@gmail.com @ 08/05/2014 15:11 -0300 dixit:
> --
> 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 osti...@googlegroups.com
> To unsubscribe from this group, send email to
> ostinato+u...@googlegroups.com
> 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 ostinato+u...@googlegroups.com
> <mailto:ostinato+u...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

--
Carlos G Mendioroz <tr...@huapi.ba.ar> LW7 EQI Argentina

cbro...@gmail.com

unread,
May 9, 2014, 6:53:59 AM5/9/14
to osti...@googlegroups.com, cbro...@gmail.com


On Thursday, May 8, 2014 2:11:06 PM UTC-4, cbro...@gmail.com wrote:
PEASE!!!
I have spent months and have tried hundreds 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, 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?

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 -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/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 -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/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' -I'../../Ostinato/rpc' -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 -o 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

unread,
May 9, 2014, 11:06:41 AM5/9/14
to cbro...@gmail.com, 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 same
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, 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 you 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. You either don't have
protobuf installed or protoc is not in the path. And if 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, 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 osti...@googlegroups.com
> To unsubscribe from this group, send email to
> ostinato+u...@googlegroups.com
> 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 ostinato+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
http://ostinato.org/
@ostinato

cbro...@gmail.com

unread,
May 9, 2014, 2:06:22 PM5/9/14
to osti...@googlegroups.com, cbro...@gmail.com

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 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'

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 `first'.

mingw32-make[2]: 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 server/ && 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

unread,
May 12, 2014, 12:07:37 PM5/12/14
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

unread,
May 13, 2014, 8:41:23 AM5/13/14
to osti...@googlegroups.com, 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 even 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, and Protobuf. (i.e. a good qt creator kit :) )

Thanks for all of your time by the way! 

Srivats P

unread,
May 13, 2014, 11:02:38 AM5/13/14
to chris brogley, 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 on the BuildingFromSource wiki page.

I would recommend 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.

will...@gmail.com

unread,
May 14, 2014, 10:34:52 AM5/14/14
to osti...@googlegroups.com, 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, please please post back so I can follow your lead.

cbro...@gmail.com

unread,
May 14, 2014, 11:06:59 AM5/14/14
to osti...@googlegroups.com, chris brogley
There was no debug information when 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, 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, May 13, 2014 11:02:38 AM UTC-4, Srivats P wrote:

cbro...@gmail.com

unread,
May 19, 2014, 1:43:17 PM5/19/14
to osti...@googlegroups.com, 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

unread,
May 20, 2014, 10:24:52 AM5/20/14
to chris brogley, ostinato
Chris,

Please join the mailing list to continue the conversation.

Srivats

Srivats P

unread,
May 21, 2014, 12:06:17 PM5/21/14
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.
* Do a google search for the error and see if any pointers there help.

Srivats

On Mon, May 19, 2014 at 11:13 PM, <cbro...@gmail.com> wrote:

chris brogley

unread,
May 22, 2014, 11:55:48 AM5/22/14
to osti...@googlegroups.com, 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. 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 last 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 it crashes
2. If it crashes very early on even before main(), maybe it can't find
the DLLs it depends upon
3. Are you able to compile and run any of the sample Qt projects?
4. Are you using the release or debug configuration for your build -
try with both
5. 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 search for the error and see if any pointers there help.

Srivats P

unread,
May 23, 2014, 11:09:14 AM5/23/14
to chris brogley, ostinato
Chris,

This one is easy to fix. 

The error indicates that the Qt DLLs are not found. I see that it is looking for QtXXXd i.e the debug version of the libraries. Check if you have the debug versions of those - they are the ones ending with 'd'. If you don't, just build the release version by doing "qmake -config release" instead of "qmake"

Srivats

chris brogley

unread,
May 27, 2014, 10:31:49 AM5/27/14
to osti...@googlegroups.com, chris brogley
Thanks, that one worked...I had to use qmake CONFIG+=release to force the project to only build release version. The Ostinato.exe crashes just after loading Drone on my Win7 machine but runs fine on my WinXP machine? I tried running it in XP compatability mode but it still crashed. The funny thing is that I built it on the Win7 machine... 

So to recap... I installed QT 4.3.3 with Mingw 3.2.0 using clean version of Ostinato 0.5.1 src and protobuf 2.3.0 (that I compiled with mingw 3.2.0) and configured qmake to Release ONLY and I was able to run the compiled Ostinato/Drone on my XP machines.

Today I installed QT Creator 2.2.1 (Without the MinGW in the package!!!!!) Then used QT 4.3.3 with Mingw 3.2.0 and I could build just fine!
I was able to run Drone Fine But Ostinato still crashed on the Win7 machine.

Srivats P

unread,
May 27, 2014, 10:56:48 AM5/27/14
to chris brogley, ostinato
Congrats Chris on getting Ostinato to build and run successfully (at least on one platform)!

Before I get to the Win7 Crash problem, can you identify what is it that you are doing different now while building from earlier when you were not able to build? It would benefit other people if you are able to identify any differences and come up with "an UPDATED document stating exactly step by step the process required to build Ostinato using QT Creator on Windows XP or 7". Yes - it's payback time ;-)

Regarding the crash, since Ostinato is progressing far enough to at least start drone, you should be able to run it through the debugger. What's the last thing it prints on the console?

Srivats

chris brogley

unread,
May 27, 2014, 11:47:49 AM5/27/14
to osti...@googlegroups.com, chris brogley
Well I think the key is somehow getting all the correct versions of the prerequisites and getting the protocol buffers built, which for me was really hard because of so many different versions of MinGW and several versions of the Protobufs. This link was very helpful in building the protocol buffers: 
http://stackoverflow.com/questions/9243816/how-to-build-google-protocol-buffers-in-windows-for-mingw
If you just install the latest of everything, which seems by far, the easiest and most logical solution, then nothing will work at all. There are just too many differences between QT 4 and 5 and all versions of MinGW. The only prerequisite that seemed straightforward was WinCap in which I just installed the latest SDK and added location to the CPLUS_INCLUDE_PATH and LIBRARY_PATH along with the location of the compiled Protobufs. 
One has to search and find all the specific links to each prerequisite and carefully install everything one by one. 
It would be exceptionally easier for everyone if there was a repository that held the compiled Protocol buffer versions (protoc.exe) and include the associated compiled DLLs) 
A much better solution would be to update the project to the latest QT 5.3.0, QT Creator 3.1.1, MinGW 4.8.x, and Protobuf 2.5.x. I really tried to do this but failed :(. This way everyone could get off the ground running very quickly. 

Another thing I found that was annoying is that the release folder did not contain all the necessary QT/MinGW DLLs required to launch the compiled executables. I had to find and copy them from their respective QT/MinGW folders.

As for debugging the Win7 issues with the Ostinato.exe I couldn't figure out how to set up the debugging using QT creator...It mentions something about 'Cdb engine' not configured properly...

chris brogley

unread,
Jun 11, 2014, 12:47:49 PM6/11/14
to osti...@googlegroups.com, cbro...@gmail.com
Final Thoughts!
See Attachment
OstinatoBuildHelpNoPics.doc
Reply all
Reply to author
Forward
0 new messages