Allow/Disallow compile does not remove the faust based code....
-
So theres def. a bug in here somewhere. I try and build a scriptNode that uses faust, and for some reason fails... so I set the ScripNode in question to AllowCompilation=Dsiabled and save the node...
I run the compile process again... and I see the offending scriptNodes C++ file STILL in the list of things to be compiled...so the compile fails again.
I clean out eth Binaries folder....still no difference.
-
@Lindon it always compiles all faust files found in code_library/faust, the allowCompilation flag is just for the network itself
-
@Christoph-Hart said in Allow/Disallow compile does not remove the faust based code....:
@Lindon it always compiles all faust files found in code_library/faust, the allowCompilation flag is just for the network itself
OKay but that leaves the project in an untenable position - you cant compile any more scriptNodes, and leaves the user trying to decipher where all the cpp and .h files are that it uses and manually removing them....which is a PITA, and possibly beyond the novice user
-
@Lindon lol just delete or move the faust file.
-
@Christoph-Hart said in Allow/Disallow compile does not remove the faust based code....:
@Lindon lol just delete or move the faust file.
which the cpp? the .h? the .dsp? it crashes HISEif I remove only one of these and not ALL the others...
-
@Lindon idk, all of them?
-
@Christoph-Hart I've been doing this recently, had to remove all of them to be sure, plus any files in AdditionalSourceCode
-
Alright, I've added a tool that will cleanup the DLL files: Export -> Clean DSP Network Files.
This should perform the proper cleanup for all file types so if you want to remove Faust files, it will also delete all generated C++ files that belong to the file (and if you delete SNEX files, it will also remove the XML parameter definition file).
-
@Christoph-Hart is there any chance to consider a feature where we can do a forever-export of a Faust file to a .cpp file that we can just save and forget about it? Then we can just plug it into any future project and it loads as a node with parameters (like it does when you compile it right now)?
I created some modules that are decently simple, do what I want them to do and sound great - I would be very happy if they kept doing that forever, wherever I pull the project on, without having to worry about the correct version of Faust being installed, about recompiling the entire networks and making sure it's all well when first pulling on a new system etc.