Forum

Hi,

I cannot get the integration wizard to compile anything under VC6 SP5. Here is an exmaple of the report that’s generated:

/*******************************************************************/
    REPORT FILE [2-26-2006, 9:6]
/*******************************************************************/

Library build for Visual Studio 98
    Build "ProfUIS252nd - ANSI/Debug (profuisdll - Win32 ANSI Debug)" - failed
    Output file: "C:\Program Files\FOSS Software Inc\Prof-UIS\BIN_600\ProfUIS252nd.dll"
    0 errors, 0 warnings
    Report file: "C:\Program Files\FOSS Software Inc\Prof-UIS\BIN_600\ANSIDebug\profuisdll\buildlog.htm"


But the report file/directory does not exist. I can build manually though which is a PITA due to the amount of targets :(


Next, when I try to build ProfAuto manually it errors out like so:


--------------------Configuration: ProfAuto - Win32 Unicode Release--------------------
Compiling resources...
Compiling...
StdAfx.cpp
Prof-UIS multiple monitor support:
built-in
Automatically linking with Prof-UIS library: ProfUIS252u.lib
(Professional User Interface Suite)
Compiling...
AutoCommands.cpp
AutoCustomizeSite.cpp
ExtAutoCategories.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoCategories.cpp(65) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoCommand.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoCommand.cpp(61) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoCommandsCollection.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoCommandsCollection.cpp(71) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoStatusBar.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoStatusBar.cpp(61) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoStatusBarItem.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoStatusBarItem.cpp(61) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoStatusBarItemsCollection.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoStatusBarItemsCollection.cpp(61) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoToolbar.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoToolbar.cpp(65) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoToolbarsCollection.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoToolbarsCollection.cpp(57) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoToolButton.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoToolButton.cpp(69) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoToolButtonsCollection.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoToolButtonsCollection.cpp(69) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ExtAutoWindow.cpp
C:\Program Files\FOSS Software Inc\Prof-UIS\ProfAuto\ExtAutoWindow.cpp(96) : error C2668: ’InlineIsEqualGUID’ : ambiguous call to overloaded function
ProfAuto.cpp
Generating Code...
Error executing cl.exe.

ProfAuto252u.dll - 11 error(s), 0 warning(s)


Any ideas?

These errors may occur if you earlier installed some new Platform SDK. In this case please check the include folders list of your Visual Studio settings and move the folders of the Platform SDK to the bottom of the list.

Hi,

I took the Platform SDK out of my list of directories (both include and lib) and the compilation problem has gone, however the integration issue still exists.

We need more details to resolve the issue:

1) The exact list of include folders of your Visual Studio.

2) Whether you able to build the libraries with Visual Studio (i.e., e.g. with the Batch Build dialog, not with the wizard)?

3) Whether the wizard compiles successfully if you remove all the .NCB files in ProfUISDLL, ProfUISLIB and ProfAuto folders?

1) Here you go ...

Include Dirs: C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE;C:\Program Files\Microsoft Visual Studio\VC98\MFC\INCLUDE;C:\Program Files\Microsoft Visual Studio\VC98\ATL\INCLUDE;D:\DEVELOPMENT\PERFORCE\C\JCLASSLIB;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CXIMAGE;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\MD5;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CPPUNIT\INCLUDE;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\ID3LIB;C:\Program Files\FOSS Software Inc\Prof-UIS\INCLUDE

Library Dirs: C:\Program Files\Microsoft Visual Studio\VC98\LIB;C:\Program Files\Microsoft Visual Studio\VC98\MFC\LIB;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CPPUNIT\LIB;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CXIMAGE;C:\PROGRAM FILES\MICROSOFT SPEECH SDK 5.1\LIB\I386;D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\ID3LIB;C:\Program Files\FOSS Software Inc\Prof-UIS\BIN_600

Path Dirs: C:\Program Files\Microsoft SDK\bin\winnt;C:\Program Files\Microsoft SDK\bin;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\VC98\BIN;C:\Program Files\Microsoft Visual Studio\Common\TOOLS;C:\Program Files\Microsoft Visual Studio\Common\TOOLS\WINNT;d:\bin;C:\Perl\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IDM Computer Solutions\UltraEdit-32;C:\Program Files\doxygen\bin;C:\PROGRA~1\ATT\Graphviz\bin;C:\PROGRA~1\ATT\Graphviz\bin\tools;C:\Program Files\Perforce;C:\Program Files\Reflection;C:\Program Files\Common Files\Compuware

Source Dirs: C:\Program Files\Microsoft Visual Studio\VC98\MFC\SRC;C:\Program Files\Microsoft Visual Studio\VC98\MFC\INCLUDE;C:\Program Files\Microsoft Visual Studio\VC98\ATL\INCLUDE;C:\Program Files\Microsoft Visual Studio\VC98\CRT\SRC;C:\Program Files\FOSS Software Inc\Prof-UIS\SRC


2) Already answered that ... Remember you were the ones who told me to put the Platform SDK dir to the bottom of the list.


3) Nope

We would like to ask you to put the Prof-UIS include folder at the fourth position and to try to compile it again:

C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE
C:\Program Files\Microsoft Visual Studio\VC98\MFC\INCLUDE
C:\Program Files\Microsoft Visual Studio\VC98\ATL\INCLUDE
C:\Program Files\FOSS Software Inc\Prof-UIS\INCLUDE
D:\DEVELOPMENT\PERFORCE\C\JCLASSLIB
D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY
D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CXIMAGE
D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\MD5
D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\CPPUNIT\INCLUDE
D:\DEVELOPMENT\PERFORCE\C\THIRDPARTY\ID3LIB

Still the same:

/*******************************************************************/
    REPORT FILE [3-2-2006, 18:40]
/*******************************************************************/

Library build for Visual Studio 98
    Build "ProfUIS252nd - ANSI/Debug (profuisdll - Win32 ANSI Debug)" - failed
    Output file: "C:\Program Files\FOSS Software Inc\Prof-UIS\BIN_600\ProfUIS252nd.dll"
    0 errors, 0 warnings
    Report file: "C:\Program Files\FOSS Software Inc\Prof-UIS\BIN_600\ANSIDebug\profuisdll\buildlog.htm"

The bug relates the .../Prof-UIS/Support/IntegrationWizard.exe tool. It was caused by renaming the profuisdll and profuislib projects to ProfUISDLL and ProfUISLIB. We updated the installers (profuis2.52.exe and profuis2.52_trial.exe). But you can download this small ZIP file, unpack it and update the IntegrationWizard.exe tool in the .../Prof-UIS/Support/ folder instead of downloading the installer again:
http://www.prof-uis.com/download/IntegrationWizard.zip.

Anyway you can compile the desired configurations of profuisdll and/or profuislib projects with Visual Studio manually (instead of using the Integration Wizard): Just open the Batch Build dialog and select the configurations you need for the profuisdll project.

I know you can build manually ... I said that in my original post. The problem with that is that you haven’t set any of the dependancies therefore when you want to compile a demo or say the Automation stuff it fails.

Anyway, the IntegrationWizard.exe in that small zip file did not work. FYI it’s v2.1.0.1 @ 1,847,296 bytes.

I downloaded the profuis2.52.exe, uninstalled, reinstalled and tried to build. The same thing happened.

We can help you effectively by connecting to your desktop remotely. We believe we will manage to find out what’s wrong. Drop us a line at support@prof-uis.com so that we can arrange a web conference.

Hi,

I am uncomfortable with allowing you remote access. Can’t you just provide a version of the .EXE with debugging in it?

We can send you the integration wizard with its source code and related debug configuration of Prof-UIS if it will help you. Anyway, we will revise the integration wizard before the next major release.

Returning to your previous post when your said: I know you can build manually ... I said that in my original post. The problem with that is that you haven’t set any of the dependancies therefore when you want to compile a demo or say the Automation stuff it fails. . In fact, it is really easy to build Prof-UIS with Visual Studio directly. All you need to do is to open ProfUIS_600.dsw and compile one of the profuisdll projects. Having compiled profuisdll, you can compile ProfAuto as it depends on profuisdll. This is enough to compile ActiveScripts. We do not see here any difficulties.

> We can send you the integration wizard with its source code and related debug configuration of Prof-UIS if it will help you. Anyway, we will revise the integration wizard before the next major release.

I’ll wait till you sort the problem out.


> We do not see here any difficulties.

That’s because you know the dependancies ... your customers don’t. What’s stopping you from setting them up so anyone can go into a project and click compile without having to worry what they need to get a demo working?

We appreciate your help in making Prof-UIS more user-friendly. Of course, we tried to set dependencies earlier. But the VS algorithm allows you to set dependencies like "project1" - "project2" only, not "project1 configuration" - "project2 configuration". So when two projects have different set of configurations, Visual Studio cannot select the correct configuration.

You can check this yourself. Open the Dependencies dialog, select the ProfSkinDLL project and make it dependent from the LibPNG and ZLib projects. Then make ProfSkinDLL active and build some release configuration, e.g. MBCS Release. You will see that Visual Studio builds the Debug configuration of LibPNG and ZLib.

So, if you see

LINK : fatal error LNK1104: cannot open file "LibPNGDLLCRT.lib"

it is clear that the LibPNG project needs to be build first.

Ooops ... just noticed I posted this in the wrong forum. Could admin move it to the tech Support" forum please.