Did something just go haywire in the Projucer? I built the latest ProJucer from develop and then I created a new project with one custom module and all the juce modules. It appears to be adding my custom module to the project 15 times and not adding any juce modules.
Seems to affect VS2017, VS2015
If I look in the JuceLibraryCode folder, there are no files for my juce modules: https://github.com/FigBug/juce_bugs/tree/master/dRowAudioTest/JuceLibraryCode
If I look in my JuceHeader, I see dRowAudio.h listed 15 times and no juce modules listed.
/*
IMPORTANT! This file is auto-generated each time you save your
project - if you alter its contents, your changes may be overwritten!
This is the header file that your files should include in order to get all the
JUCE library headers. You should avoid including the JUCE headers directly in
your own source files, because that wouldn't pick up the correct configuration
options for your app.
*/
#pragma once
#include "AppConfig.h"
#include <dRowAudio/dRowAudio.h>
#include <dRowAudio/dRowAudio.h>
#include <dRowAudio/dRowAudio.h>
#include <dRowAudio/dRowAudio.h>
show original
ed95
November 21, 2017, 2:40pm
2
Thanks for the report, it seems this is a bug that occurs when combining user and JUCE modules. I’ll push a fix to develop shortly
1 Like
