Visual C++ Compatibilty info.

Discussion in 'Effects and the DSP' started by Russ, Mar 22, 2005.

  1. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    yes i we talk about fx_demo and the demo.dsw . i used bundled fx_demo folder without changes.
    rather i wanted modify the kxm 120 (midi kbu) with possibility playing legato and polyphonic keys, triggering gate correctly.
    the idea was a simple key- counter with increment and decrement if "note on" or "note off" message arrives..
    no luck at compling it.
    so i thought: try the fx_demo to check the compiler itself before searching the error in my own code kxm120..

    i think about reinstalling vc6.
     
  2. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    must have to do with mfc. if i set "use mfc in a static library" demo.kxl is build with a lot of warnings:

    .\h\gui/kWindow.h(24) : warning C4275: non dll-interface class 'CWnd' used as base for dll-interface class 'kWindow'
    ..\h\afxwin.h(1899) : see declaration of 'CWnd'
    ..\h\gui/kTextButton.h(45) : warning C4251: 'text' : class 'CString' needs to have dll-interface to be used by clients of class 'kTextButton'
    C:\Programme\Microsoft Visual Studio\VC98\MFC\INCLUDE\afx.h(368) : see declaration of 'CString'
    ..\h\gui/kKnob.h(65) : warning C4251: 'bmpKnob' : class 'CBitmap' needs to have dll-interface to be used by clients of class 'kKnob'
    ..\h\afxwin.h(524) : see declaration of 'CBitmap'

    .. and so on and sofore

    simple.cpp
    Linking...
    Creating library Release/demo.lib and object Release/demo.exp
    LINK : warning LNK4089: all references to "ADVAPI32.dll" discarded by /OPT:REF
    LINK : warning LNK4089: all references to "SHELL32.dll" discarded by /OPT:REF
    LINK : warning LNK4089: all references to "comdlg32.dll" discarded by /OPT:REF
    rename
    1 Datei(en) kopiert.

    demo.dll - 0 error(s), 23 warning(s)
     
  3. Russ

    Russ Well-Known Member

    Joined:
    Jan 17, 2005
    Messages:
    5,722
    Likes Received:
    13
    Trophy Points:
    48
    There is no need for static linking since everyone who uses kX has the necessary MFC dll's. I would get the same warnings if I set it to link statically.

    If you want, I can send you the VC6 project files I used to compile kxm120 for 3541 (which also compiles without problems (for me) with 3545)...
     
  4. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    send me a mail (look in private message) :)

    stylus
     
  5. Russ

    Russ Well-Known Member

    Joined:
    Jan 17, 2005
    Messages:
    5,722
    Likes Received:
    13
    Trophy Points:
    48
    OK, I will send the files now. I do not know if it will help since (unless you changed some setting) it should be the same as what I sent you before, but...

    Regarding kX versions:
    Debug build should be used for kX versions prior to 3539.
    Release build should be used for kX versions 3539 and up.
    ... And of course you should use the SDK version (or a compatible version) that matches the kX version that you are compiling for.
     
  6. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    tried the workspace files you have sent, same error.
    stay on debug release/3538.

    stylus
     
  7. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    That is all too weird!
    I have 'good old' VC6 installed on some "kX machine" and can compile 3545 release builds without problems.
    I don't know if Russ actualy used VC6?
    Anyway, if you want me to give your workspace a try in vc6 just let me know?
     
  8. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
  9. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    Yep, kxm120.zip compiles just fine both in debug as well as release build.
    win xpsp3, msvc6.0+sp6, kX3545 sdk.

    Indeed, must be something wrong with your vc6 installation and/or OS.
     
  10. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    i could install sp3 on winxp. what means vc6+sp6?.
     
  11. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    Well, win xp sp2 + vc6 + 3534 should also work fine, I have just tried that on another partition.

    vc6+sp6 means vc6 + service pack 6 lol
     
  12. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    Oh btw; IIRC, the latest Visual Studio is free. Dunno if MFC is included this time or not.
    (although you can write kx plugs without mfc too)
    Check ms website.
     
  13. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    problem fixed after installing vs6/sp6. my version of vs6 was outdated.
    application update - service pack - microsoft terminology. :)

    stylus
     
  14. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    Good!:)
     
  15. Russ

    Russ Well-Known Member

    Joined:
    Jan 17, 2005
    Messages:
    5,722
    Likes Received:
    13
    Trophy Points:
    48
    Anyone know what is needed for 3548 x86 (since it appears that VC6 is no longer an option).

    Using VS .NET 2003 (SP1) I can compile the plugins OK, and they register and load into the DSP OK, but I cannot open the tweak window for the plugin (using kxgui). Debug output shows: "kX Mixer: an exception on creating plugin window...". Any ideas? I do remember this issue from before, but I thought that maybe it would not be an issue with newer versions of kX.

    Also, when trying to compile my addon, I get an an unresolved external symbol with the "int add(kString,kMenu *menu,int flag=0);" function (from kmenu.h). If I use the TCHAR version of the same function instead, it compiles OK, and the addon appears to work correctly. Any idea on why the kString version of the function causes the error? (The E-DSP addon has a couple more unresolved externels too).
     
    Last edited: Jul 30, 2009
  16. Lex Nahumury

    Lex Nahumury DH Senior Member

    Joined:
    Jan 5, 2003
    Messages:
    1,944
    Likes Received:
    6
    Trophy Points:
    0
    My plugins+win32Gui (both in vc6 as well as in vs2008) compile and run fine using 3548-x86 so it's probably some window creation bug in kxgui.
    Best to mail E about it.
     
    Russ likes this.
  17. Russ

    Russ Well-Known Member

    Joined:
    Jan 17, 2005
    Messages:
    5,722
    Likes Received:
    13
    Trophy Points:
    48
    Yeah, I get the feeling he is going to say that I have to use the WDK (or not use kxgui). I am hoping Max has some workaround...
     
  18. Russ

    Russ Well-Known Member

    Joined:
    Jan 17, 2005
    Messages:
    5,722
    Likes Received:
    13
    Trophy Points:
    48
    OK, I got it working with VC6 (with a couple warnings (C4601) about #pragma push_macro : 'new')...

    I had to add an include to the crt directory from the PSDK to get definitions for stuff like intptr_t (I already had includes for other PSDK stuff, but not that specific one).

    i.e.
    Include Files
    C:\PROGRAM FILES\MICROSOFT PLATFORM SDK\INCLUDE\CRT

    [EDIT]
    I was able to get it working with VS .NET 2003 (SP1) as well, with some includes from the WinDDK (same as I posted here, except I also had to add "C:\WINDDK\3790.1830\lib\atl\i386" to the list of libraries).
     
    Last edited: Jul 30, 2009
  19. stylus02

    stylus02 New Member

    Joined:
    Jan 11, 2008
    Messages:
    283
    Likes Received:
    2
    Trophy Points:
    0
    hi russ,

    after hd- crash i had to make a new windows installation. now it´s a windows 7 with kx version 3550. i got the same problem while compiling my plugins with vc6/sp6. in kxplugin.h this line causes an error:

    typedef intptr_t kxparam_t;

    can you explane which includes you have added?

    thx
     
    Last edited: Dec 21, 2009
  20. Max M.

    Max M. h/h member-shmember

    Joined:
    Dec 7, 2002
    Messages:
    2,690
    Likes Received:
    9
    Trophy Points:
    63
    Îòâåò: Visual C++ Compatibilty info.

    intptr_t/uintptr_t are defined in crtdefs.h
     
    Last edited: Dec 21, 2009

Share This Page

visited