Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length

 
Advanced search

1401678 Posts in 67940 Topics- by 61496 Members - Latest Member: Lankar5

July 07, 2022, 12:16:57 AM

Need hosting? Check out Digital Ocean
(more details in this thread)
TIGSource ForumsDeveloperTechnical (Moderator: ThemsAllTook)tiny development libraries
Pages: [1]
Print
Author Topic: tiny development libraries  (Read 4111 times)
Kekskiller
Guest
« on: May 12, 2008, 01:02:17 AM »

I'm looking for some librarys like TinyPTC that enables me to do input and audio stuff in a similar way. At the moment I'm using SDL for direct framebuffer access - it is nice, but has a big framework (250k lib + executable).

Are there some libs that do stuff in this way? I don't wan't to use SDL all the time, its audio and event management SUCKS.

PS: I'm using DEV-C++. I prefer pure code or devpacks, because I'm not so experienced in integrating librarys via special compiler/linker functions...
Logged
jcromartie
Level 0
***


View Profile
« Reply #1 on: May 12, 2008, 11:29:56 AM »

SDL ... it is nice, but has a big framework (250k lib + executable)

250 kB?

Two hundred and fifty kilobytes?  That's what counts as big these days!?
Logged
Kekskiller
Guest
« Reply #2 on: May 12, 2008, 11:59:31 AM »

yes, this is relative big.
Logged
Ivan
Owl Country
Level 10
*


alright, let's see what we can see


View Profile
« Reply #3 on: May 12, 2008, 12:03:53 PM »

Maybe portaudio?

http://www.portaudio.com/

It's not even a lib, it just uses whatever native sound API on the platform.

Logged

http://polycode.org/ - Free, cross-platform, open-source engine.
Kekskiller
Guest
« Reply #4 on: May 12, 2008, 12:29:04 PM »

portaudio looks interesting, will take a look at it. thanks!
Logged
increpare
Guest
« Reply #5 on: May 12, 2008, 01:06:31 PM »

Yeah; I'll quite likely have a look at that myself
Logged
jcromartie
Level 0
***


View Profile
« Reply #6 on: May 12, 2008, 01:08:09 PM »

Maybe portaudio?

http://www.portaudio.com/

It's not even a lib, it just uses whatever native sound API on the platform.

From the site:

Quote
PortAudio is a ... library.

And it's also roughly a third of the size of SDL, which handles audio in essentially the same way (writing to an output buffer in a callback function).  I'm not really clear on what the drawbacks of SDL, as presented here, are.
« Last Edit: May 12, 2008, 01:11:34 PM by jcromartie » Logged
Ivan
Owl Country
Level 10
*


alright, let's see what we can see


View Profile
« Reply #7 on: May 12, 2008, 01:17:03 PM »

Oh oops, I was under the impression it was just a wrapper for the native os sound API with no prebuilt stuff to link.
« Last Edit: May 12, 2008, 07:57:37 PM by toastie » Logged

http://polycode.org/ - Free, cross-platform, open-source engine.
Ryan
Level 1
*



View Profile
« Reply #8 on: May 12, 2008, 07:26:50 PM »

If you need input / opengl and stuff (will probably need another small library for sound), I've always really liked glfw. Super light weight. The only problem I have with it is USB gamepads don't work on OS X. I've always wanted to write a tiny wrapper for each OS [gl/input], but win32 and xlib programming makes me cry. Cry
Logged
Kekskiller
Guest
« Reply #9 on: May 13, 2008, 06:17:14 AM »

glfw is simply WOW. a 35k-55k dll + exe. nice! wonderful simple API functions. this is a must for me Kiss ... for audio stuff... hm. OpenAL looks also very small (my S.T.A.L.K.E.R. uses a 48k dll!). just look at he glfw page, there are many good links for small-sized libraries and other stuff.

thanks for the help! i really hope this will solve my problems with librarys and their usage...

edit: glfw uses TARGA files, this is a bit extraordinary but probably a step into the future Smiley (for me!)
« Last Edit: May 13, 2008, 11:52:11 AM by Kekskiller » Logged
jcromartie
Level 0
***


View Profile
« Reply #10 on: May 13, 2008, 07:14:33 AM »

edit: glfw uses TARGA files, this is a bit extraordinary but probably a step into the future Smiley

Are you sure TARGA is the future?

Quote
The TGA file format was originally defined and specified by AT&T EPICenter with feedback from Island Graphics Inc in 1984.

PNG would seem to be the future, as far as I can tell.
Logged
increpare
Guest
« Reply #11 on: May 13, 2008, 07:25:37 AM »

Gosh; I remember when I used to use P(aint)S(hop)P(ro) I was all about the tga files  Grin
Logged
ColossusEntertainment
Level 1
*

Royal Leamington Spa, UK


View Profile
« Reply #12 on: May 13, 2008, 07:58:56 AM »

I have a little graphics/game lib (also does a bit of sound and input)

http://www.colossusentertainment.com/DevelopmentStuff/PixieGameEngine.html

Not sure it's small enough to be classed as "tiny", but the aim have been to try and keep things simple, reduce dependencies and maximize compatibility. (And it's public domain Smiley)
Logged
Kekskiller
Guest
« Reply #13 on: May 13, 2008, 11:51:48 AM »

Are you sure TARGA is the future?

Oh, I'm sorry: this a personal step for me. I'm using mostly bitmap stuff, because reading is easy and it everything can read it. So TARGA is a step forward for me Smiley .  I've TARGA files with purebasic and some other programming languages, it has some nice features and I'm using targa files very often. Yes, it isn't the best format at all, but has all stuff that makes an image format important.
Logged
coderneedsfood
Level 0
**


View Profile
« Reply #14 on: May 16, 2008, 05:10:13 PM »

for raw pixel access http://www.bik5.com/tech/ easy ce is a wrapper for pocket pc and has a win32 text application also
you can rip the code from that , super easy

Logged
Pages: [1]
Print
Jump to:  

Theme orange-lt created by panic