Thanks much for doing this. I think that we have a few housekeeping
items to take care of.
Any info on the qwtbuild.pri and qwt.pro.user files are for?
I see that the qwtbuild.pri file is in the qwt distribution, but it
doesn't seem to be used by any other files.
qwt.pro.user seems to be a superfluous config file left over. It is
not in the official qwt distribution.
Also we should update qwtconfig.pri.in in our repo to reflect the
updated version of qwt. There are some differences between the
qwtconfig.pri file that is distributed with qwt 6.0.1 and what we
have in the repo as qwtconfig.pri.in
All that said, I was able to build on my mac with no issues. Great
job.
Jamie
> --
> _______________________________________________
> Golden-Cheetah-Users mailing list
> golden-che...@googlegroups.com
> http://groups.google.com/group/golden-cheetah-users?hl=en
"You don't use science to show that you're right, you use science to
become right."--xkcd
__________________
Jamie Kimberley
Postdoctoral Fellow
Department of Mechanical Engineering
The Johns Hopkins University
Office: 410.516.5162
Mobile: 217.621.8272
Fax: 410.516.4316
E-Mail:jamie.k...@jhu.edu
sadly the multiple axis patch was not included in qwt 6.0.1
To your observation, I'm guessing the build is pulling in the
header files from your other "stock" qwt install. I think that
while we add our modified qwt to the INCLUDEPATH, qmake finds your
system files first. Is a solution to this just more explicitly
hardcoding the include paths to point directly to the header files
in the qwt dir?
Jamie
Any info on the qwtbuild.pri and qwt.pro.user files are for?
Also we should update qwtconfig.pri.in in our repo to reflect the
updated version of qwt. There are some differences between the
qwtconfig.pri file that is distributed with qwt 6.0.1 and what we
have in the repo as qwtconfig.pri.in