I’m attempting to port the open source QuickFix engine from http://www.quickfixengine.com to QNX 6.3.0 and am struggling. Admittedly as a LONG time C programmer (I’ve been writing C longer than some of my coworkers have been alive!), C++ is a bit of a foreign to me – I know just enough to be dangerous – and that might be the problem. However to my naive eye it looks like there are incompatibilities in the QNX C++ headers.
As directed, I downloaded and made and installed lib-xml2 first. That went without problem.
Then I downloaded the Linux QuickFix hoping that would compile. My first attempt at had the configure script creating makefiles that called g++ which seemed to be a problem, so I did a ‘make clean’ then reran configure as:
./configure CC=qcc CXX=QCC
That worked a little better, but eventually very standard things that the code (and I) expected to be in the headers were missing.
Can anyone suggest what I might be doing wrong? Or what additional info do you need before you can give me guidance.
P.S. Yes, I’m THAT Bill Flowers! Rumors of my death or abandonment of QNX are premature.
I posted this question before and no one had anything to say. If dynamic libraries foo.so needed to be compiled with the same compiler as your program, then how could programs compiled with different compilers work at all since the all need libc.so, right? I assume that your libxml2 is libxml2.so Bill.
Success! Compiling with 3.3.1 (that came with my 6.3.0 release) compiled all the code and linked all the test apps.
I ran out of time to run the tests though because I had to fly to Boston Friday night, join my wife who had been away for 3 months, then drive back home to Clearwater through the remains of Tropical Storms Gustav and Hanna. We did the 22 hour drive (est. without stops) in 26 hours elapsed.
Thanks to everyone for the advice in getting this going.
A friend tried a small piece of test code under 6.3.0 SP3 and reported that such an assertion would succeed there, so I upgraded and tried again with the gcc 3.3.5.
Now the executables produced won’t even load! I get reports of “unknown relocation type” and memory faults.
I’ve been using QNX for 25+ years but with trying to port this package I am feeling like a total n00b. Nothing that I can see is wrong but nothing works, and I’m running out of time.
Is there a porting guru out there that could try a quick download, configure and make to see if I’m just doing (or forgetting) something stupid, or if there is a real problem so I can stop wasting my time.
Lunch time is over, here is what I found so far. AR in libtool points to ar and RANLIB points to ranlib. I replaced AR with QCC -v… -A and got rid of RANLIB. With this it’s able to build libquickfixcpptest.a without any error. Will resume later today.
Bill you can’t mix the 2.95.3 and 3.3.5 stuff at all - you have to set the 3.3.5 version for BOTH compile and link. Probably the safest thing to do is to set the global default to the 3.3.5 (check the qcc usemsg for how to do that).
Colin, I appreciate your advice but what if it doesn’t use qcc to link? It appears to be using ntox86-ld directly.
I’ve set the default as suggested and left it compiling while I’m at the office. (This project is one of 3 jobs I’m holding down at the same time, besides father and husband.) Tonight I’ll see if it worked.
So far I still can’t get this to port and my client is telling me to move on … that I’ve wasted too much time trying to get this to work under QNX. I’ve been forced to give up trying to port this to QNX so unless someone can give me the magic incantation today that makes it work then I’m outta here.
I really want to stick with QNX if I could but tonight I will be forced to look at other platforms.