Hi,

usually it works. I have myself a Windows 7 64bit installation and use VS 2008 Express SP1 which ships with 32bit compilers only.

Here are some steps you could try to figure out your problem:

1.) Install all Visual Studio Service Packs
2.) Open cmd.exe and check your environment variables for suspicious Qt stuff 3.) Try to start DGraph.exe (located in CTK-build/... ) by hand, possibly setting PATH to the Qt bin directory

That is pretty much all I can think of for now.

- Sascha

On 08/01/2011 05:52 PM, Ghazall Aghaei wrote:
Hi,

I still haven't found a solution to the above issue. Any more suggestions? Anyone else successful with VS 2008?

Regards,
Ghazall

2011/7/26 Ghazall Aghaei <[email protected] <mailto:[email protected]>>

    Yes, I've selected the non-x64 compiler option in Cmake of course.
    Weird.

    Regards,
    Ghazall

    2011/7/26 Sascha Zelzer <[email protected]
    <mailto:[email protected]>>

        On 07/26/2011 09:27 PM, Ghazall Aghaei wrote:
        Now this is an interesting idea. Thanks.
        I'm running an x64 Windows but I deliberately choose the
        tools to be 32bit, e.g. VS2008, Qt 4.7.1, Cmake 2.8.4 are all
        x86. I'm not aware of any x64 switch I could switch during
        configuring in cmake. Anything I could have missed that might
        trigger x64 code to be generated?
        Yes, on 64bit systems, if a x64 compiler is available (depends
        on your Visual Studio edition), CMake presents you with
        different choices for the "CMake Generator". The CMake-GUI
        displays the currently used generator, it should not contain a
        "64" string.

        - Sascha



        Thanks again for your help,
        Ghazall

        2011/7/26 Fritzsche, Klaus H. <[email protected]
        <mailto:[email protected]>>

            Hi Ghazall,

            DGraph-Issues might also occur if you are trying to build
            x64 using a 32bit Qt. Could this be the case for you?
            Then you should compile a 64bit Qt. The Qt installer is
            only available in 32bit so far.

            Best

            Klaus

            *Von:*Ghazall Aghaei
            [mailto:[email protected]
            <mailto:[email protected]>]
            *Gesendet:* Dienstag, 26. Juli 2011 20:29
            *An:* [email protected]
            <mailto:[email protected]>
            *Betreff:* Re: [mitk-users] Failed to obtain dependence
            path of CTKCore

            Hi,

            If you are referring to my MITK-supberuild CMake: Looks
            okay to me as it points to my local Qt 4.7.1
            installation E:/Qt/4.7.1/bin/qmake.exe

            Judging from the DGraph build instructions [1] it should
            compile fine.

            The file "CMakeCache.txt" inside CTK-build has
            the QT_QMAKE_EXECUTABLE filepath pointing to above
            location as well.

            I could not find any Qt reference in cmake_install.cmake
            in CTK-build\Utilities\DGraph - building the solution
            file in there works fine.

            Anyone else compiling the MITK superbuild with VS 2008?
            Which Qt version did you succeed with?

            Regards,

            Ghazall

            [1] http://www.commontk.org/index.php/Build_Instructions

            2011/7/26 Sascha Zelzer <[email protected]
            <mailto:[email protected]>>

            Hi,

            the CMake scripts compile a utility program called
            "DGraph.exe" which is Qt-based. Usually everything is
            done automatically, but it could be the case that your
            QT_QMAKE_EXECUTABLE CMake variable points to another Qt
            version, which was not used to build DGraph.exe.

            Can you check your QT_QMAKE_EXECUTABLE variable in CMake
            if it looks suspicious?

            Thanks,
            Sascha



            On 07/26/2011 10:10 AM, Ghazall Aghaei wrote:

            Hi there,

            i just installed visual studio 2008 and trying to compile
            july's stable superbuild received this compile error:

            1>CMake Error at
            CMake/ctkMacroValidateBuildOptions.cmake:137 (MESSAGE):
            1>  Failed to obtain dependence path of CTKCore.
            1>  Exit code 0xc0000135

            I already did a bit of research, but only some outdated
            (nov 2010) CTK mailinglist items came up which were of no
            help
            Any idea how to fix that dependence path?

            Thanks,

            Ghazall




        
------------------------------------------------------------------------------
        Magic Quadrant for Content-Aware Data Loss Prevention
        Research study explores the data loss prevention market.
        Includes in-depth
        analysis on the changes within the DLP market, and the
        criteria used to
        evaluate the strengths and weaknesses of these DLP solutions.
        http://www.accelacomm.com/jaw/sfnl/114/51385063/
        _______________________________________________
        mitk-users mailing list

        [email protected]
        <mailto:[email protected]>
        https://lists.sourceforge.net/lists/listinfo/mitk-users




------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to