DSP compiling error on WIN, works fine on MAC

[ustk]

@Morphoice said in DSP compiling error on WIN, works fine on MAC:

but how am I supposed to compile my third party nodes on another OS if I clear them out of the thirdparty folder?

I should have said the files created by Hise in there, not the actual 3rd party files you manually added in

[Morphoice]

@ustk ah ok I see. But the problem here is in the C++ code, something the windows compiler takes more strict than the mac, so deleting random stuff wouldnt solve it, I need someone to fix the C++ above

[Lindon]

@Morphoice so are you trying to compile your fx/HISE when its on a virtual machine external drive?

I have found that Faust based nodes WONT build on anything other than a real real real drive inside the machine - external drives are a no no.

[Morphoice]

@Lindon again, it's a problem with the c++ code I posted above. I am compiling on either a virtual machine, external drive and a dedicated machine with an internal drive which has the exact same problem whereas all other plugins that don't use that third party node compile fine on either of the systems. so it's for sure not a problem with an external drive and sorry to say so but if we live in a world where men can be women, people can travel to space and doctors can cure aids, an external properly mounted drive sure as hell should not break a compiler. y'all conjuring up some spiritual paranormal esoteric reasons why stuff doesn't work instead of having a look at the real problem.

MSVC (Microsoft Visual C++) which is the compiler on Windows/PC handles things more strict than CLANG (the C++ compiler on MAC). Whoever made that C++ did not account for that and probably worked on mac or linux. I posted the error codes, I don't know a lot of C++ though so if just someone who is pro at C++ could have a look and point me to a solution, I'm sure it's an easy one. Please no more suggestions to arrange my computers according to the teachings of Feng Shui, y'all driving me nuts ;) No offence, though, I love you all. It's just not the solution to the problem, so can we please get the point of that and stop trying random stuff ;)

[Lindon]

@Morphoice well... let me get the hell out of your way then.

[d.healey]

@Morphoice Usually compilers have flags you can set to control strictness. Maybe ask Chat GPT if such flags are available on Windows

[Morphoice]

@Lindon Please no hard feelings man, you know I appreciate your help. An external drive is just not the problem here, I've already tracked it down as good as I can

[orange]

Yes, looks like it's related to Airwindows.h.

Maybe @oskarsh has an idea about this?

[Lindon]

@Morphoice well I have a project that uses a single AirWindows scriptNode (its Air2) and it compiles fine on windows.

so the Additional Source code folder looks like this:

the nodes folder looks like this:

the Air2.h file in here looks like this:

// This just references the real file

#include "../../DspNetworks/ThirdParty/Air2.h"

The DspNetworks/ThirdParty folder looks like this:

Where the Air2.h file looks like this:

#pragma once

#include <JuceHeader.h>

#include "../../AdditionalSourceCode/AirWindows.h"

namespace airwindows::air2_ns {
JUCE_BEGIN_IGNORE_WARNINGS_GCC_LIKE("-Wmultichar")
#include "../../External/airwindows/plugins/LinuxVST/src/Air2/Air2.h"

#include "../../External/airwindows/plugins/LinuxVST/src/Air2/Air2.cpp"
#include "../../External/airwindows/plugins/LinuxVST/src/Air2/Air2Proc.cpp"
JUCE_END_IGNORE_WARNINGS_GCC_LIKE
}  // namespace airwindows::air2_ns

namespace project {

using namespace juce;
using namespace hise;
using namespace scriptnode;

DECLARE_AIRWINDOWS_NODE(Air2, air2_ns);

}  // namespace project

There is an External folder at the root of my project with these included files in there...

Im using VS2022 - I have not changed any flags in there...

[oskarsh]

@orange yes some nodes seem to only work on windows and some only on macOS. The source code of my project can be compiled on windows and MacOS the same. Make sure to clear the binaries folder of the dsp networks. Do not delete any other folders.

When compiling make sure you first set all networks to not compile - then compile the dsp networks - open Hise and set your networks with Airwindows nodes to compile.