A really annoying trouble comes up again. http://www.forum.fs-net.de/vie…3008&hilit=64bit&start=15
Your assistance is required.
Situation:
Installation A: Windows7-32bit, VisualStudio2008 SP1, picocom4_sdk_v101.msi installed
Debug and Release builds of a PicoCOM4 project complete without errors.
Installation B: Windows7-64bit, VisualStudio2008 SP1, picocom4_sdk_v101.msi installed
(Before that, PicoCOM2 had been installed and in use for a while, then uninstalled. As we now only use PicoCOM4 and no PicoCOM2 modules anymore I wanted to clean up my projects.)
The PicoCOM4 project was copied from Installation A to Installation B.
The Release build completes without errors. The Debug build fails with
- 1>uafxcwd.lib(oleunk.obj) : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol ""bool __cdecl ATL::_IsTracingEnabled(unsigned long,unsigned long,unsigned int)" (?_IsTracingEnabled@ATL@@YA_NKKI@Z)" in Funktion ""public: static bool __cdecl ATL::CTrace::IsTracingEnabled(unsigned long,unsigned int)" (?IsTracingEnabled@CTrace@ATL@@SA_NKI@Z)".
- 1>PicoCOM4 (ARMV4I)\Debug/LowVolumeSpectrometer.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise.
Linking uafxcwd.lib or uuid.lib does not help (and was not required with Installation A.)
How do I overcome this?
I observe the same behaviour with other PicoCOM4 projects: Debug build fails, Release build completes while no differences between the project file settings can be found. All these projects were created starting with a new PicoCOM4 project and adding the files from a PicoCOM2 project.
(By the way: see http://forum.fs-net.de/viewtopic.php?f=31&t=1110). PLEASE add the requirement to do a custom install as a readme.txt at the download site of the SDKs. Even better would be to solve the problem.)
