Sauerbraten in a dll

by PlateWolf on 07/24/2006 01:50, 45 messages, last message: 03/24/2008 16:27, 15557 views, last view: 05/25/2024 13:07

Hi, I want to access Sauerbraten externally, did anyone managed to compile it in a dll ?
(Like SDL for example).

   Board Index   

#6: ..

by PlateWolf on 07/29/2006 01:02

Too bad, it's a great engine.
I hope it became usefull to us in the future.

Thanx for your time.

reply to this message

#7: Engine

by Drakzz on 07/30/2006 12:25

Hm, what?
Some people surely do not know what shared libraries are.
djRobbieF: On Windows you have .DLL libraries. On UNIX you have .so libraries.

I think it would be a great idea to convert Sauerbraten engine into a DLL, really.

I might attempt that.

This would be a great thing becuase there would be no need to recompile all the Sauerbraten if one bug exists somewhere.

Another thing is that game makers could easily adopt the sauer engine to their games and this would be something like RAD (Rapid application development) - create the game without the actual internals, which the engine does.

reply to this message

#8: It doesn\'t take that long.

by Todd5-0 on 07/30/2006 16:47

Compiling sauerbraten takes about 10 seconds on my computer.

reply to this message

#9: ..

by PlateWolf on 07/31/2006 01:31

You can take a look at http://www.genesis3d.com/ to see what I'm talking about.
It may not make sense to do this for C/C++ programmers, but for companies that want to use other languajes it's a very important feature when it comes to evaluate engines.
In fact, in our case, it's a must.

Drakkz, please let me know how your efforts go. I've taken a couple of hours to do it but my C/C++ skills are not the best around.

reply to this message

#10: What about Cross-Platform?

by Greywhind on 07/31/2006 01:44

If you just make a DLL, you will not be staying true to the spirit of Sauer, which is cross-platform. I would suggest making a Linux (.so) and Mac (framework) version too.

reply to this message

#11: Guys

by pushplay on 07/31/2006 06:49, refers to #10

It's the same damn code to compile to so and dll.

reply to this message

#12: ..

by djRobbieF on 07/31/2006 15:50

Personally, I like having Sauer in source... I can see how a DLL (or .so) would be nice for an end-user... but not for the development community.

reply to this message

#13: ...

by stevo32 on 08/07/2006 07:16

Ok, first, for clarification. DLLs are windowses type of shared library. They're .so on linux and i don't know what they are on OS X. The point being, is that they're all the same damn code.

djRobbieF: Obviously it'll still come as source code, this'll just make it easier for people who aren't working in C/C++.

So, when people say the want it in a DLL, they want it as a shared library. It does make things easier, it really does. I think it'd be a great idea, just maybe one that'll get integrated later in development.

Thanks!

reply to this message

#14: Re: ...

by bigsofty on 03/17/2008 16:51, refers to #13

So is it possible? I found a few threads on this but none conclusive.

reply to this message

#15: Re: ..

by shadow....school on 03/17/2008 17:02, refers to #3

Sauer is NOT GPL, it is ZLIB. Open source and GPL are not synonymous...

As for the question, I don't see why you couldn't, but that's something you'd have to do on your own.

reply to this message

#16: ..

by MovingTarget on 03/17/2008 18:59

Theoretically, it should be possible, but you'd have to go the way of definition files to export all the functions. And you probably wouldn't want to export some internal functions either.

reply to this message

#17: Re: ..

by MovingTarget on 03/17/2008 19:07, refers to #16

OK, just tried it. It seems that I got it to work, since the executable size got split in half, and it works fine.

reply to this message

#18: ..

by HashBox3 on 03/17/2008 22:03

stevo32: They\'re .dylib on OSX I think.

And I agree that it would be awesome. Quite a few engines are used this way, Raydium comes to mind.

reply to this message

#19: Re: ..

by bigsofty on 03/17/2008 22:34, refers to #17

Wow well done! Any chance we could see the result too please?

reply to this message

#20: Yeah

by fdshjkfhsdkconorhfsdjk on 03/18/2008 00:52

If we got a Sauerbraten version into a DLL, SO, and DyLib, then I am sure some people would like to use it :)

reply to this message

#21: Re: ..

by MovingTarget on 03/18/2008 02:56, refers to #19

It's really easy to do for yourself (if you use CodeBlocks+MinGW, that is).
I'm going to challenge you to find out how to do it! It's quite simple. But if I get enough pressure I may just upload it and stick something on the wiki ;)

reply to this message

#22: ..

by ezombie on 03/18/2008 04:18

How about you just post a list of the .cpp + .h files that went into the DLL - versus the EXE?

That would go a long way to help people.

reply to this message

#23: Re: ..

by fdshjkfhsdkconorhfsdjk on 03/18/2008 04:19, refers to #22

what can be done with a dll vs exe.

reply to this message

#24: ..

by ezombie on 03/18/2008 04:26

I think they want to link to it from another language - like VB, C#, D, C-, Python, Ruby, Perl, PHP, Lua - just about anything that can load and call shared libraries.

Of course it matters *what* is in the DLL versus what is in the EXE. You must put enough in the DLL to be useful to another EXE, but no so much that it restricts what you can make...

reply to this message

#25: Re: ..

by MovingTarget on 03/18/2008 13:11, refers to #22

The list would be two long. Make two duplicate projects, and in one, delete the fpsgame and rpggame folders from the headers and source in the project, and in the other, delete the engine stuff. DO NOT DELETE THE SHARED STUFF! (I wonder why it's called that :D)

reply to this message

   Board Index