really?? that was the first thing I did… made sure I could compile the vstsdk. So I did the again example and it worked fine. I skipped all the vstgui stuff cos jucey will replace that… then I kinda figured, ok… if that works… now just adapt it to main in the jucey stuff… boom.
When I say VST SDK, I meant the entire thing (inculding vstgui) lol
dev-C++ is pissing me off big time, making huge build files, always needing some obscure library, bugging out with calling conventions (why the fuck does it use pascal?!), not extending inline properly…
the borland builder X thing comes with some free compilers, but I don’t recall what they are.
There is also Watcom, but I always found it to be a bunch of arse.
static linking is always a problem with c++ though as far as I can tell.
Once you complile JUCE out as a .a file you have pretty much made it a lump that will block compiled into your code.
You could always turn JUCE into a dll and then dynamically link to it. That’d be little advantage for one app, but if a user had two or three JUCE based apps it’d be cheaper.
If you run strip over you .exe though you should be able to shrink it by around 25% or so.
Problem is mingw/gcc want static libs in win32 :-\ I looked at watcom, and there’s no bloody way that’s gonna work very well.
They seem to absolutely detest dynamic linking :-\ It’d not be hard to make JUCE a dll, but the problem is once you want to use it in an app via mingw/gcc, they want the lib to be statically linked.
from the looks of it, it comes with the borland c++ builder compiler and mingw. The personal edition is free for non comercial use from what I understand.
so maybe we can figure out a way to get this up and running…???
edit: I really hope it works with this! the environment is so much… NICER! although I can’t say much on the technical end. Gonna try to compile the jucey bits now… 8)
Are you saying that mingw doesn’t support dynamic libraries? That seems unlikely. If that is the case it would throw any hope of making the sample editor support vst plugin s. :shock:
well as far as I can tell mingw does allow you to link dynamically, but I’ll be damned if I can work out how to do it. There is a definite shortage of documentation on that front.
:?
I’m guessing there’ll be some form of loadlibrary() function available that could be used to dynamically open the library, but personally I’d rather have the library opened at runtime rather than on-demand.
Borland wont let me get BuilderX 'cos they seem to think I already have a key for it. Let me know if it seems to be working 'cos then I’ll chase up their accounts dept and see what is going on.
hmmm… well I got everything in there and started trying to build with it. The borland compiler immediately fired up all sorts of errors. I simply don’t have enough experience to decipher what the problems are… or if it’s simply something that I’ve setup wrong.
I then switched over the MinGW compiler figuring I’d at least get the borland IDE which I kinda prefer. It got thru a whole lot of it (like 50+ files), then hit an error in the way something was defined. ugh… I dunno. pretty uneventful day. Shoulda been working on some music… hpmh… :x
seems that the borland compiler doesn’t like the “forcedinline” declarations… what’s the deal with that? I’ve tried looking it up on the net, and I can’t find any info on forcedinline and borland…
[quote=“valley”]well as far as I can tell mingw does allow you to link dynamically, but I’ll be damned if I can work out how to do it. There is a definite shortage of documentation on that front.
[/quote]
Only on linux that I can see… Ive tried everything I can think of in win32 and it bugs out totally because apparently mingw likes __stdcall and windows likes __cdecl
To even come close I had do to all sorts of shit with making custom def files… even then I still had to distribute a custom lib.
the winapi has a load dll function of sorts I beleive, but that’s a major hack…