First time poster, please be gentle. I wasn’t sure this topic deserved its own thread since answers here might be similar to the other thread about compiling with MinGW and Cygwin, but I went ahead and started a new thread anyway. Mods feel free to merge them if warranted.
I’m trying to compile JUCE using the CDT Plugin in Eclipse which I’ve set up to use MinGW and Msys for gcc, g++, and gdb. I’ve been successfully writing, compiling and linking C and C++ projects for my classwork in school within this Eclipse CDT Plugin environment.
This is the first time I’ve tried to import and build an outside library. I opened a new workspace, and a new managed make C++ project, then imported the JUCE_1.41 directory tree (everything except the linux and mac specific folders). As soon as I did, the builder took off on it’s own using default settings.
I’m sure there are some specific build settings I need to make but I don’t know what to change and what to leave alone. There are project/property build settings in a dialog box as well as a .cdtbuild xml file. The xml file might get automatically updated when changes are made in the properties dialog. Is anyone else using CDT and Eclipse with JUCE? Can anyone help me sort out this lib making process?
Everything seems to have compiled into .o files at least but no binaries appeared in the bin directory and there is what looks like one error chain that starts in: juce_PixelFormats.h
The two forcedinline functions tween(const Pixel&, const uint32) and set(const Pixel&) generate the error messages:
sorry, unimplemented: inlining failed in call to 'void juce::PixelARGB::tween(const Pixel&, juce:: uint32) throw () [with Pixel = juce::PixelARGB]': function body not available sorry, unimplemented: inlining failed in call to 'void juce::PixelARGB::set(const Pixel&) throw () [with Pixel = juce::PixelARGB]': function body not available
And then in the class PixelRGB
Only the forcedinline function set(const Pixel&) generates another “sorry, unimplemented…” message.
Then there are a few other places (where those inline functions are called) that also generate error messages , but I think those are just sympathetic downstream error messages.
Thanks for any help. I’m very excited about the possibilities that JUCE represents.