Visual C++ Compatibilty info.

Lex Nahumury · Jun 14, 2009, 09:10 PM

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

Lex Nahumury · Jun 14, 2009, 10:58 PM

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.

stylus02 · Jun 15, 2009, 08:08 AM

problem fixed after installing vs6/sp6. my version of vs6 was outdated.
application update - service pack - microsoft terminology.

stylus

Lex Nahumury · Jun 15, 2009, 09:36 AM

Quote:

Originally Posted by stylus02

problem fixed after installing vs6/sp6. my version of vs6 was outdated.
application update - service pack - microsoft terminology.

stylus

Good!

Russ · Jul 29, 2009, 07:07 PM

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).

Lex Nahumury · Jul 29, 2009, 08:00 PM

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 · Jul 29, 2009, 08:10 PM

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...

Russ · Jul 29, 2009, 09:10 PM

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).

Jun 14, 2009, 09:10 PM	#31
Lex Nahumury DH Senior Member Join Date: Jan 2003 Location: The Netherlands Posts: 1,883 Rep Power: 48	Re: Visual C++ Compatibilty info. 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

Jun 14, 2009, 10:58 PM	#32
Lex Nahumury DH Senior Member Join Date: Jan 2003 Location: The Netherlands Posts: 1,883 Rep Power: 48	Re: Visual C++ Compatibilty info. 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.

Jun 15, 2009, 08:08 AM	#33
stylus02 DriverHeaven Lover Join Date: Jan 2008 Location: germany, sb0090 Posts: 158 Rep Power: 0	Re: Visual C++ Compatibilty info. problem fixed after installing vs6/sp6. my version of vs6 was outdated. application update - service pack - microsoft terminology. stylus __________________ http://freenet-homepage.de/stylish-s...xas/index.html

Jul 29, 2009, 07:07 PM	#35
Russ DriverHeaven Extreme Member Join Date: Jan 2005 Posts: 4,836 Rep Power: 41	Re: Visual C++ Compatibilty info. 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 by Russ; Jul 29, 2009 at 08:30 PM.*

Jul 29, 2009, 08:00 PM	#36
Lex Nahumury DH Senior Member Join Date: Jan 2003 Location: The Netherlands Posts: 1,883 Rep Power: 48	Re: Visual C++ Compatibilty info. 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.

Jul 29, 2009, 08:10 PM	#37
Russ DriverHeaven Extreme Member Join Date: Jan 2005 Posts: 4,836 Rep Power: 41	Re: Visual C++ Compatibilty info. 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...

Jul 29, 2009, 09:10 PM	#38
Russ DriverHeaven Extreme Member Join Date: Jan 2005 Posts: 4,836 Rep Power: 41	Re: Visual C++ Compatibilty info. 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 by Russ; Jul 30, 2009 at 12:19 AM.