[newbie] Using JUCE with existing code

[TheVinn]

I did what TheVinn suggested and put in the select .cpp files and .h files, but I got a lot of compile errors when those .cpp files were compiling. I guess I have some work to do on that, nothing I can't handle.

Is your copy of AppConfig.h visible from your project's include paths?

Which .cpp did you add to your project? juce_core.cpp?

[Bruce Wheaton]

Dealing with link errors isn't child's play sometimes. Static libraries and cpp's that are walking into an app always are going to have this problem, only .dylibs/dll's with .h files can avoid those type of errors.

OK, so - I didn't suggest that you rebuild your library project, just that you use baby steps, AKA basic troubleshooting.

And yes, link errors can be a bear. Especially if you don't have a good grasp of what's going on. You should probably steer clear of explaining to everyone else what will and won't always be problems until you have a bit more understanding.

Right click on the orange slice icon that represents your project file in the IntroJucer. Not sure why it didn't make targets for you. Did you do 'New..' to make a new project?

Bruce

[dave96]

The Introjucer is obviously undergoing pretty rapid development at the moment and small things are being fixed all the time. Therefore I always recommend building the Introjucer from the sources yourself, just open the project under juce/extras/Introjucer/Builds/... for your platform, it only takes a second. There was a day or two where it didn't automatically create an export target for you and if this happens to be the pre-built one currently uploaded you will see this problem.

Also if you're not up to date with the latest its difficult for us to point you in the right direction as I think most people here are pretty close to the bleeding edge tip due to all the great stuff that comes with it.