# Problems with adding external module

**URL:** <https://forum.juce.com/t/problems-with-adding-external-module/33155>\
**Category:** General JUCE discussion\
**Created:** [April 30, 2019, 6:31pm UTC](https://forum.juce.com/t/problems-with-adding-external-module/33155 "2019-04-30T18:31:18Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![alassandro](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/alassandro/32/4297_2.png) [@alassandro](https://forum.juce.com/u/alassandro)\
**Post date:** [April 30, 2019, 6:46pm UTC](https://forum.juce.com/t/problems-with-adding-external-module/33155/4 "2019-04-30T18:46:42Z")

</div>

> [@Xenakios](#):
>
> I would guess it’s just not compatible with the current Juce anymore

This exactly, it looks like it still uses the old `juce_module_info` manifest too…

> [@New JUCE module format proposal!](https://forum.juce.com/t/new-juce-module-format-proposal/16926):
>
> Hi folks - I've been working recently on an update to the way that modules are defined. Apart from just wanting to simplify things a bit, I wanted to make it less dependent on the Introjucer's project generation, and to make it easier for non-introjucer-users to add juce modules to their projects by simply throwing a few files and include paths into their project. Below is my first draft of the new spec for how a module folder should look - comments welcome! The TL;DR is that the JSON manifes…

---

_[View the full topic](https://forum.juce.com/t/problems-with-adding-external-module/33155)._
