how to set up a visual c++ express thing for compiling ChucK

Dr. Spankenstein · Posted: Sun Sep 30, 2007 2:57 am Post subject:

Linking...

Creating library Debug/chuck.lib and object Debug/chuck.exp

rtaudio.obj : error LNK2019: unresolved external symbol __imp__CoInitialize@4 referenced in function "public: __thiscall RtApiDs::RtApiDs(void)" (??0RtApiDs@@QAE@XZ)

rtaudio.obj : error LNK2019: unresolved external symbol __imp__CoUninitialize@0 referenced in function "public: virtual __thiscall RtApiDs::~RtApiDs(void)" (??1RtApiDs@@UAE@XZ)

rtaudio.obj : error LNK2019: unresolved external symbol __imp__GetForegroundWindow@0 referenced in function "private: virtual bool __thiscall RtApiDs::probeDeviceOpen(int,enum RtApi::StreamMode,int,int,unsigned long,int *,int)" (?probeDeviceOpen@RtApiDs@@EAE_NHW4StreamMode@RtApi@@HHKPAHH@Z)

LIBCMTD.lib(wincrt0.obj) : error LNK2019: unresolved external symbol _WinMain@16 referenced in function ___tmainCRTStartup

I've changed settings in the project properties -> linker -> subsystem to both CONSOLE and WIN32 but neither work.

All the libraries are linked correctly in the VC++ directories too.

I havent a clue where I'm going wrong here as I've followed the instructions carefully.

Rhys

PS. Thanks for clearing that up kassen

blue hell · Posted: Sun Sep 30, 2007 8:18 am Post subject:

For me these errors were solved by setting the additional dependencies for the project to the list that's on the previous page of this thread. I'll sum it up again, in the hope it will turn out to be useful Very Happy

In the solution explorer right click on the chuck_win32 project, select properties go to configuration properties/linker/input/additional dependencies and check that the list looks like :

dinput.lib
odbc32.lib
odbccp32.lib
dsound.lib
dxguid.lib
wsock32.lib
winmm.lib
User32.lib
gdi32.lib
Advapi32.lib
ole32.lib
kernel32.lib
oleaut32.lib

There may be a few too many, as I don't know what I'm doing exactly.

Dr. Spankenstein · Posted: Sun Sep 30, 2007 12:29 pm Post subject:

Thanks, I was being stupid and not explicitly adding them to the linker by typing them in.

Unfortunately with the code I compile, I constantly get debug assertion failures when trying to run the code....I'm not certain why and I feel I'm somewhat out my depth here!

Kassen · Posted: Sun Sep 30, 2007 1:14 pm Post subject:

Well, Dr.; if it turns out it it's this hard then that's a interesting result in and of itself, especially considering that a senior hacker like BlueHell has trouble with it too. I'd say this is ground for petitioning for more and better docs on building for Windows.

I'm also happy to report I got a mail from Ge who described his first week at Stanford as "Insanity" but who will look at it in the near future.

I think we booked some nice results here already, even if it doesn't quite run on Windows yet and if I'm 99% sure I'm still missing something because there is a whole variable that's all through the Envelope code that I don't see any purpose to yet (oops!).

blue hell · Posted: Sun Sep 30, 2007 1:18 pm Post subject:

Kassen · Posted: Sun Sep 30, 2007 1:38 pm Post subject:

blue hell · Posted: Sun Sep 30, 2007 2:08 pm Post subject:

When I run it I get :

blue hell · Posted: Sun Sep 30, 2007 3:09 pm Post subject:

Back to the ASIO setup

Kassen · Posted: Sun Sep 30, 2007 3:32 pm Post subject:

Well, I'm happy, in contrast getting

blue hell · Posted: Sun Sep 30, 2007 3:40 pm Post subject:

Kassen · Posted: Sun Sep 30, 2007 3:49 pm Post subject:

Yes, all of that is bound to come from one little oops somewhere, I don't think you are expected to intuitively grasp what a "EAEXPAURtApiDevice" is or what it's having a problem with without a context beyond knowing we are talking about something related to a hook to a soundcard.....

blue hell · Posted: Sun Sep 30, 2007 3:57 pm Post subject:

All the more respect for Phillipe though, too bad he's busy busy. I'm giving it a rest now for a couple of days. I'll probably still browse the code in the meanwhile, maybe I get a bright idea or something, we'll see.

Kassen · Posted: Sun Sep 30, 2007 4:11 pm Post subject:

Yeah, me too. We lost the momentum, I'd rather throw some more hours at interesting problems then at roadblocks we know are solvable and will likely be gone in a few days.

lamarcph · Posted: Mon Oct 01, 2007 4:48 am Post subject:

What is better than homework to make you look at stuff you should not look at?

Seriously, "soon", I will post a step by step tutorial on how to compile with express 2005. It's is strait forward, once you know how to do it.

However, Blue Hell, I never had anything like you are having now. Do you have all the DirectX and Windows SDK installed?

This is what I have as a preprocessor command line:

__PLATFORM_WIN32__;WIN32;_CONSOLE; __WINDOWS_ASIO__; __WINDOWS_DS__; _SCL_SECURE_NO_WARNINGS;

As I understand it, __WINDOWS_DS__ must still be there otherwise midi will not work.

I hope this works,
Philippe.

blue hell · Posted: Mon Oct 01, 2007 5:11 am Post subject:

lamarcph · Posted: Mon Oct 01, 2007 5:37 am Post subject:

An other thing I forgot:

Depending on what winSDK you are using, be sure to add

#define _HAS_ITERATOR_DEBUGGING 0
#define _SECURE_SCL 0

at the top of chuck_oo.cpp, before #include "chuck_oo.h" .

Otherwise, it will compile fine, but it will crash as soon as you do a chuck array.

Dr. Spankenstein · Posted: Mon Oct 01, 2007 9:33 am Post subject:

Well I finally got the .exe to compile and run in windows OK BUT......

This is what I get from the new env code when running kijaz's experiment...

Kassen · Posted: Mon Oct 01, 2007 11:17 am Post subject:

Ah! I suspect that was a typo by Kijjaz. Replace e.last() by e.value().

E.last() reports the last sample calculated and with a 0 input that's 0. e.value() reports the value used as if e is used as a modulation envelope.

Also look at the original topic about the bug because I did some updates since you started; I had missed some important stuff. I believe we now have the core issues with Envelope documented but I can't guarantee my last version is production-quality, in the end I hacked some of it up quite badly (see the explanation there).

Kassen · Posted: Mon Oct 01, 2007 11:19 am Post subject:

blue hell · Posted: Mon Oct 01, 2007 11:36 am Post subject:

moudi · Joined: Oct 07, 2006 Posts: 63 Location: Bern Switzerland

moudi · Joined: Oct 07, 2006 Posts: 63 Location: Bern Switzerland

hi all

i tried to compile a chuck asio version, but i get still some errors.
i will try to explain what i already did.

1) i was able to compile a chuck DS version successfuly. i took this as the base for my asio chuck.

2) changed the preprocessor settings as mentioned by philippe.

3) corrected the typos (EM_poplog() and the cerr block).

4) added the #define to chuck_oo.cpp as mentioned by philippe.

5) copied the asio directory of the rtaudio to the chuck sources (since chuck refers to a /asio/asiosys.h)

6) hit the compile button and got some nasty errors like this one:

Kassen · Posted: Fri Nov 02, 2007 2:55 pm Post subject:

Isn't there a kind soul who could share a ASIO build ,exe of 1.2.1.1? I don't have one either ATM.

Unless you, Moudi, have custom tweaks you need with yours?

blue hell · Posted: Fri Nov 02, 2007 4:30 pm Post subject:

I have an untested version of 1.2.1.0 only.