Sudden unexpected Libray errors

I must say that I have used lots of different development environments ove many years, starting with Zorland C (1970s), Borland, Visual Studio. They all misbehaved from time to time.
But I am mistified why an appication I coded and last compiled some four months ago, completely error free, now reports:

k:\...\libraries\USBMIDI\src\usbmidi_pluggableusb.cpp:15:26: fatal error: PluggableUSB.h: No such file or directory
 #include <PluggableUSB.h>
                          ^
compilation terminated.
Alternatives for PluggableUSB.h: []
ResolveLibrary(PluggableUSB.h)
  -> candidates: []

The library is in its registered directory. I tried re-installing it. I just wish the Arduino Ide would cope better with errors , rather than expecting em to spend a fruitless day searching for a s

Hi @kaspencer. I'm going to ask you to provide the full verbose output from a compilation.


:exclamation: This procedure is not intended to solve the problem. The purpose is to gather more information.


Please do this:

  1. Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus.
    The "Preferences" dialog will open.
  2. Check the box next to "Show verbose output during: ☐ compile" in the "Preferences" dialog.
  3. Click the "OK" button.
    The "Preferences" dialog will close.
  4. Select Sketch > Verify/Compile from the Arduino IDE menus.
  5. Wait for the compilation to fail.
  6. You will see a "Compilation error: ..." notification at the bottom right corner of the Arduino IDE window. Click the "COPY ERROR MESSAGES" button on that notification.
  7. Open a forum reply here by clicking the "Reply" button.
  8. Click the <CODE/> icon on the post composer toolbar.
    This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
    Code block icon on toolbar
  9. Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
    This will paste the compilation output into the code block.
  10. Move the cursor outside of the code block markup before you add any additional text to your reply.
  11. Click the "Reply" button to post the output.

In case the output is longer than the forum software will allow to be added to a post, you can instead save it to a .txt file and then attach that file to a reply here.

Click here for attachment instructions

  1. Open any text editor program.
  2. Paste the copied output into the text editor.
  3. Save the file in .txt format.
  4. Open a forum reply here by clicking the "Reply" button.
  5. Click the "Upload" icon (Upload icon) on the post composer toolbar:
    Upload icon on toolbar
    The "Open" dialog will open.
  6. Select the .txt file you saved from the "Open" dialog.
  7. Click the "Open" button.
    The dialog will close.
  8. Click the "Reply" button to publish the post.

Alternatively, instead of using the "Upload" icon on the post composer toolbar as described in steps (5) - (7) above, you can simply drag and drop the .txt file onto the post composer field to attach it.

@ptillisch - sorry, the post was in draught, unfinished and incomplete - I posted it in error.
KAS

1 Like

I know that you deleted the original and it sounds like you figured it out.

Can you explain what the solution was so others that experience the same issue can learn from it? I looked at your error and suspect that you compiled for the wrong board but I might be wrong.

Sorry about the delay in replying to your question.

I've been (and still am) trying to sort out another project that is also being awkward! But that issue still exists, and I'll be going back to it soon - I hope so anyway.
BUT the basic problem still exists.
My problem is that updates to the IDE and to Libraries always seem to stop my projects dead in theirs tracks - I wish I had never upgraded as I cannot get going back to work either!

All the best

Ken

We can probably help you with it, but we need more information.

The file PluggableUSB.h is not part of the USBMIDI library, it is in the boards package for whatever board you are compiling for. The library includes that file conditional on the board having USB hardware, so it should not be generating an error if you compile for a board that lacks such hardware.

Which board are you using?

Your second problem sounds like the following. TL;DR: stop the serial console during any of the updates if these appear to block.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.