grag38 / qextserialport

Automatically exported from code.google.com/p/qextserialport
0 stars 0 forks source link

Cannot run example on Windows XP #55

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. Install latest version of Qt (4.6.2 32bit) on Windows XP
2. Try compiling qextserialport.pro via Qt Creator

What is the expected output? What do you see instead?

First, I was getting errors compiling because the linker couldn't find the
library, qextserialportd.  I noticed that in the src/build/ directory there
was a qextserialportd1 library, so I added the '1' to the .pro files for
the enumerator and event examples.  Now the code compiles, but as soon as I
run it, I get an error message box saying "Executable failed: You can't do
that without a process to debug".  Then it hangs all of Qt Creator, so I
have to kill it and restart from scratch.  I've tried changing to the
'Release' configuration but get the same problem.  Any ideas?

What version of the product are you using? On what operating system?

Qt (4.6.2 32bit) on Windows XP
Latest clone as of 10 April 2010.

Please provide any additional information below.

Everything worked fine on Mac OS X.

Original issue reported on code.google.com by stahl.k...@gmail.com on 11 Apr 2010 at 2:20

GoogleCodeExporter commented 8 years ago
There's a problem at the moment with the naming of that DLL.  Maybe try 
commenting out the VERSION line in 
src.pro.  Still pending a proper fix for that...

Original comment by lst...@gmail.com on 11 Apr 2010 at 2:40

GoogleCodeExporter commented 8 years ago
Ok, I tried commenting out that line, but no luck.  Now I'm trying to recompile 
Qt
statically, including the static .a library.  I hope this works - the decision
whether to use Qt or Java for my team's next project depends on whether I can 
get the
serial port working on both Windows and Mac platforms.  Any idea when there 
might be
a fix for the DLL naming problem?

Original comment by stahl.k...@gmail.com on 11 Apr 2010 at 6:02

GoogleCodeExporter commented 8 years ago
Related to http://code.google.com/p/qextserialport/issues/detail?id=12 (i.e. 
also related to build issues).

Continuing on the fork referenced in that issue 
(http://code.google.com/p/qextserialport/issues/detail?
id=12#c1): http://github.com/wimleers/qextserialport.

I *did* find that commenting out VERSION helped. Immediately after that, the 
examples would build.

For reference, here is the relevant portion of a .pro file that links in 
QextSerialPort:
<code>
# Link against the QextSerialPort library.
INCLUDEPATH += lib/qextserialport/src
QMAKE_LIBDIR += lib/qextserialport/src/build
CONFIG(debug, debug|release):LIBS += -lqextserialportd
else:LIBS += -lqextserialport
</code>

Original comment by mail%wim...@gtempaccount.com on 17 May 2010 at 11:45

GoogleCodeExporter commented 8 years ago
I agree.  I tried commenting that line again, and it worked great.  Something 
must have 
gotten fixed along the way.  It's working beautifully for me on both Windows XP 
and Mac 
Snow Leopard now.

Original comment by stahl.k...@gmail.com on 18 May 2010 at 12:06

GoogleCodeExporter commented 8 years ago
Likewise :)

Also, if you want to copy the .dll's automatically, see 
http://stackoverflow.com/questions/1740534/qmake-
how-do-i-copy-dll-sos-to-the-output-directory/2853740#2853740

Original comment by mail%wim...@gtempaccount.com on 18 May 2010 at 12:10

GoogleCodeExporter commented 8 years ago

Original comment by dbzhang...@gmail.com on 16 Mar 2012 at 8:49