These are chat archives for highfidelity/hifi

24th
Jul 2014
David Rowe
@ctrlaltdavid
Jul 24 2014 18:25
Anyone know about qxmpp_d0.dll etc. versus qxmpp_d.dll etc. (without the '0')? ... My Windows build environment broke w.r.t. QXMPP on 22 Jul
David Rowe
@ctrlaltdavid
Jul 24 2014 19:01

I now have QXMPP (i.e., chat window) working again on my Windows builds:

  • Set environment variable QXMPP_INCLUDE_DIRS (with an 'S') instead of the old QXMPP_INCLUDE_DIR (without an 'S')
  • Copied my qxmpp0.dll etc. (with a '0') as qxmpp.dll etc. (without a '0') so that the configuration step finds
  • But the executable still needs the '0' versions of the files in order to run

I don't know what the '0' business is about: my build of QXMPP included the '0's and they used to be accepted during build configuration.
So something's not quite right but at least my building with QXMPP is up and running again and I don't need to be so antisocial when running development builds!

David Rowe
@ctrlaltdavid
Jul 24 2014 19:09
However, I still can no longer run Windows Debug builds because of "DevicesDLL.dll is missing" error ... hmmm
David Rowe
@ctrlaltdavid
Jul 24 2014 19:25
Actually, it's DeviceDLL.dll and is included in one of the Sixense SDK samples ... will investigate further after lunch
David Rowe
@ctrlaltdavid
Jul 24 2014 21:44
Re missing DeviceDLL.dll in Windows debug builds: currently you need to copy the file from the SDK's sample application into your debug build directory.
Have submitted a pull request to revert to using Sixense release DLLs in Windows debug builds.