Can't get swig to run, can someone send me the .dlls please?

Hi,

I've been unable to get swig running, I think because I only have 128mb of ram. Can someone please send me(or upload) the compiled dlls the procuded produces please?

My e-mail address is AntonyCoder@Btinternet.com

I plan on using it in Visual C# Express and have no need to modify the wrapping so all I need really are ogrenet.dll and math3d.dll

Thanks.

SWIG shouldn't care how much RAM you have... please tell us the error messages you get.

It just never runs. The sandglass loading icon appears briefly and there's some hd activity but then nothing.

have you rebooted since you set the SWIG_HOME environment variable? VS may not be able to see that depending on how you launch it.

When you right click OgreBindings.i and click compile it should output info in the Output window like "Invoking Swig" ... a lot of lines. Copy that and post here.

Just tried it, again the sandglass icon appears briefly but there's no output.

I think it maybe symptonmatic of another problem as Edonkey does the same thing when I run it now. just refuses point blank to run.

It could be a permissions thing. Are you trying to run Swig over a network share or anything?

Nah, just a regular edition of windows xp 2 home retail edition and I'm the administrator of the account.

I'll ask one once last time before sulking and calling you all names, can someone please send me the dlls

You can find them (ogre 1.0.6/.net1.1 compatible version) here. If you get compatibility problems (I think you wont) I can post a .net2 version of them.

I think it would be better to have a sticky thread to post the binaries, isn't it?

Nah, just a regular edition of windows xp 2 home retail edition and I'm the administrator of the account.

I'll ask one once last time before sulking and calling you all names, can someone please send me the dlls

The point of SWIG and the wrapper source is to have it work to create the DLLs for you. Just compiling them ourselves and putting them out there for download whenever someone has a minor hitch kinda defeats the purpose.

You came here saying "I can't get it to work, so I give up... give me the end result."

That's fine for the most part, but realize that we want to help you get it to work FOR YOU all the time... so we don't have to keep making DLL zips for people to download everytime there's an update.

Oh I know, but you must realise I'm quite literally the world's most lazy man. If it wasn't for gravity I wouldn't even bother to lay down to sleep at night.
Is there any real benefit to compiling the dlls yourself other than saving you guys time? (I don't mean that in a sarcastic way, I've just never understood why people release source instead of dlls. Makes life much easier just to have to link a dll )

Thanks for the link otherguy. Your work will not go unnoticed. In fact, here's a raise. Enjoy the high life!

Releasing sources allows for incremental changes to be made without having to keep re-zipping and maintaining an archive of DLLs for every single change. It also allows the open source method to work! If the CVS just had DLLs, what would anyone work off of?

What usually happens is DLL zips are created (which are generally larger than the source code by the way... another reason for distributing the source instead of DLLs) whenever there is a major stable release. What this means is if you get the prebuilt DLLs, you may not have the most recent version with bug fixes and such... so that's another benefit to compiling from the CVS yourself.

Of course, the opposite is true if the CVS has a change that was put in recently that introduces a bug.

Oh I know, but you must realise I'm quite literally the world's most lazy man. If it wasn't for gravity I wouldn't even bother to lay down to sleep at night.
Is there any real benefit to compiling the dlls yourself other than saving you guys time? (I don't mean that in a sarcastic way, I've just never understood why people release source instead of dlls. Makes life much easier just to have to link a dll )

Thanks for the link otherguy. Your work will not go unnoticed. In fact, here's a raise. Enjoy the high life!

In the .NET world there's no real benefit to compiling from source since you won't get any unique, processor specific optimizations, or any of the other good stuff you'll get when compiling stuff by hand in C/++.

These fellahs aren't using a build-system like CruiseControl.net that does a nighty check-out / build / upload, so their only other alternative is to zip things up by hand or make people check out CVS versions, so its no surprise they err on the side of least resistance.