Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

DarkBASIC Professional Discussion / DB Pro Footprint

Author
Message
BatVink
Moderator
23
Years of Service
User Offline
Joined: 4th Apr 2003
Location: Gods own County, UK
Posted: 3rd Sep 2003 20:15
Link
What's the minimum size of a DB Pro executable? I compiled a bare bones program, it came out at 5.5 meg. Is this typical, or are there ways to streamline it?

Just considering the 15 meg limit on the AlienWare comp.

StevieVee
http://facepaint.me.uk/catalog/default.php
Back to top
Profile PM Email
OSX Using Happy Dude
22
Years of Service
User Offline
Joined: 21st Aug 2003
Location: At home
Posted: 3rd Sep 2003 20:44
Link
Well :



compiles down to 237K


Avatar & Logo by Indi. Come to the UK DBPro Convention in Chichester
Back to top
Profile PM Email Website
adr
23
Years of Service
User Offline
Joined: 21st May 2003
Location: Job Centre
Posted: 3rd Sep 2003 21:35
Link
If you "compress attached media" it halves the size of the executable, but doubles compilation time.

A wise man once said: "I know that I need codes but I dont know the codes"
Back to top
Profile PM Website
CattleRustler
Retired Moderator
22
Years of Service
User Offline
Joined: 8th Aug 2003
Location: case modding at overclock.net
Posted: 3rd Sep 2003 21:56
Link
Wasn't there also some issue with dbp5.3 compiling some extra stuff into the exe? I have a test project that has no attached media, and the code is only two screens long, but when compiled it's like six megs! Something about a dbp dll getting added to the exe - I know I saw this somewhere but forgot what it said.

search the forums for EXE DLL, it got answered in a post somewhere

-RUST-
Back to top
Profile PM
spooky
23
Years of Service
User Offline
Joined: 30th Aug 2002
Location: United Kingdom
Posted: 3rd Sep 2003 23:05
Link
If you do a simple proggy like:



which forces compiler to include the some basic 3d stuff.

Normal exe = 4.7 mb
Normal exe with compressed media = 2.22 mb

so then zip up the 2.2mb file gets down to 2.15 mb
or rar it and you get 1.9 mb

The programmer formerly known as sonic
Back to top
Profile PM Website
Kentaree
23
Years of Service
User Offline
Joined: 5th Oct 2002
Location: Clonmel, Ireland
Posted: 3rd Sep 2003 23:11
Link
The commands are sorted into categories like basic3d, system etc. which each are included in their own dll. So if you'd use one command of every category your program would include every dll giving you a huge filesize.

Personally, I wonder if it isnt possible for there to be an option that only the used commands are included with your final executable and not the entire command sets. Even if this took a longer time to compile, I think most of us would prefer smaller file sizes and sacrifice some compiler speed.

Cheers,
Kentaree

I would be unstoppable if I could just get started...
Back to top
Profile PM Email Website
empty
23
Years of Service
User Offline
Joined: 26th Aug 2002
Location: 3 boats down from the candy
Posted: 3rd Sep 2003 23:41
Link
That isn't be possible with the current setup of the compiler as you can't strip single functions out of dynamic link libraries.

I awoke in a fever. The bedclothes were all soaked in sweat.
She said "You've been having a nightmare and it's not over yet"
Back to top
Profile PM
CattleRustler
Retired Moderator
22
Years of Service
User Offline
Joined: 8th Aug 2003
Location: case modding at overclock.net
Posted: 4th Sep 2003 00:25 Edited at: 4th Sep 2003 00:25
Link
Quote: "That isn't be possible with the current setup of the compiler as you can't strip single functions out of dynamic link libraries.
"


I would think that it's not possible in Windows period, for the same reason: Dynamic Link Library

-RUST-
Back to top
Profile PM
DMXtra
23
Years of Service
User Offline
Joined: 28th Aug 2002
Location: United States
Posted: 4th Sep 2003 01:42
Link
The executables have gone up in size a bit due to DirectX 9's HLSL parsers.

You can get around this by checking compression in the DBPro IDE. This way it will compress the executable down to a small size you can deal with.

Lee had said that he was going to work on it getting it back down again.

Dark Basic Pro - The Bedroom Coder's Language of choice for the 21st Century.
Back to top
Profile PM
Shadow Robert
23
Years of Service
User Offline
Joined: 22nd Sep 2002
Location: Hertfordshire, England
Posted: 4th Sep 2003 07:01
Link
smallest possible size is 230kb ...
depending on how many DLLs you use you can range from that upto 11mb for the executeable.

(this is provided you don't use any external DLLs)

you will also use around 500bytes/line of code or something close to that

though the footprint of a program is actually its memory needs, which Pro uses 16mb standard it then requires another 16mb dynamically ... and the rest is program dependant.
It'll also require a rough 8mb of Video Ram, but most programs will actually require closer to 16mb if not more especially if your using Matricies.

Back to top
Profile PM Email Website
Inkybro
23
Years of Service
User Offline
Joined: 31st Dec 2002
Location: Where I live :)
Posted: 4th Sep 2003 07:05
Link
I think it's possible.

Couldn't they, possibly in the next update, simply take the used commands, stick them into something such as commands.dll and then somehow include it with the compiled .exe, maybe attatched, maybe not.

Just wondering if that'd be possible

Don't turn your back on me, I won't be ignored! Faint - Linkin Park

One minute your on top! Next you're not, watch you drop! Linkin Park- Hit the Floor
Back to top
Profile PM Email Website
Shadow Robert
23
Years of Service
User Offline
Joined: 22nd Sep 2002
Location: Hertfordshire, England
Posted: 4th Sep 2003 08:34
Link
if Lee truely wants to get the code sizes down DarkBASIC Pro is gonna need an runtime library released to compliment DirectX which is installed on end user machines.

If it didn't need to compile the DLLs into the exec itself, then it would enable DBP to compile to some more desireable sizes ... probably closer to the lines of a 400kb being probably the more max size your likely to see not the starting point.

it would also mean that released versions of programs won't have to be recompiled each time a new update is released for bug fixxes as well ... it'd just be a case of updating the DarkBASIC Pro Runtime.
Also allowing TPC DLLs to either be compiled into the program or placed within the directory of the program would also be a nice touch i think.

i mean if you think about it the original DBPro Runtime libraries too up 7mb, and they've risen to around 10mb ... with this being the case it wouldn't be much for users to upgrade libraries for thier systems.
It might even give Lee a chance to develop some system dependancies allowing it to be far more stable on each of the Windows environments.

just an idea though - pretty sure its been suggested before

Back to top
Profile PM Email Website
Back to top

Login to post a reply

Server time is: 2026-07-23 15:49:40
Your offset time is: 2026-07-23 15:49:40