Compiled DOSBox 10mb bigger \ VOGONS

Compiled DOSBox 10mb bigger

Topic actions

First post, by Jef

Posted on 2009-02-11, 12:59

Jef Offline

Rank Newbie

Rank: Newbie
Posts: 16
Joined: 2008-12-31, 18:03

When I compile DOSBox on Tiger (PowerPC), then the PowerPC-only binary with static libraries is around 13mb...
But when I compile DOSBox on Leopard (also PowerPC), then the again PowerPC-only binary with static libraries is about 3mb...

The Leopard built doesn't work on Tiger becuase it can't find the CoreFoundation.framework. But the Tiger one works on both Tiger and Leopard. (and for those who have Windows, Tiger is older than Leopard)

1) Can I link the Leopard CoreFoundation.framework to the source and will it work on Tiger (I can test this but I don't know which line I need to add for linking that framework)

2) Am I missing some flags when I compile on Tiger ? the original DOSBox executable is about 10 mb and it works on both Intel and PowerPC. The one I made is 13mb and is PowerPC only... and if I'm not mistaking, the original source is built on Tiger (maybe Panther which is older)

I both tried DOSBox 0.72 and the CVS of 30 January.

Thanks in adavance.

Reply 1 of 7, by Qbix

Posted on 2009-02-11, 13:04

Qbix Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 11234
Joined: 2002-11-27, 14:50
Location: Fryslan

maybe you forgot to strip one of the parts ?

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 7, by Jef

Posted on 2009-02-11, 13:23

Jef Offline

Rank Newbie

Rank: Newbie
Posts: 16
Joined: 2008-12-31, 18:03

Qbix wrote:
maybe you forgot to strip one of the parts ?

thanks for the quick reply 😀

what do you mean ?

Reply 3 of 7, by MiniMax

Posted on 2009-02-11, 13:28

MiniMax Offline

Rank Moderator

Rank: Moderator
Posts: 5128
Joined: 2004-01-18, 04:15
Location: Stockholm, Sweden, Europe, Earth Interests: Old games & young women

Depending on the compiler and linker flags, the object files, libraries, and the executables will sometimes contain additional debug information (which could explain the extra 10 MB you see).

The Unix-utility strip(1) is commonly used to strip/remove files from the (unnecesarry) debug information before shipping the programs to customers.

Reply 4 of 7, by Jef

Posted on 2009-02-11, 16:18

Jef Offline

Rank Newbie

Rank: Newbie
Posts: 16
Joined: 2008-12-31, 18:03

Can't seem to get it working,
I tried strip -s
But do I need to run ./configure first ? and do I need to strip it from within the main folder or the src folder ?

Reply 5 of 7, by Qbix

Posted on 2009-02-11, 16:23

Qbix Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 11234
Joined: 2002-11-27, 14:50
Location: Fryslan

1strip dosbox_executable_you_made

1man strip

Water flows down the stream
How to ask questions the smart way!

Reply 6 of 7, by Jef

Posted on 2009-02-11, 19:08

Jef Offline

Rank Newbie

Rank: Newbie
Posts: 16
Joined: 2008-12-31, 18:03

Thanks, strip executable worked... I already tried man strip but I didn't find anything that could help. the executable was 14.8 mb and now it's 2.9 mb

when I statically linked it, I left out the /debug/libdebug.a line, that's safe right ?

Reply 7 of 7, by Qbix

Posted on 2009-02-11, 19:20

Qbix Offline

Rank DOSBox Author

Rank: DOSBox Author
Posts: 11234
Joined: 2002-11-27, 14:50
Location: Fryslan

if it links without errors then it is safe 😀
but you can link it anyway. it is fairly empty in non-debug mode.

Water flows down the stream
How to ask questions the smart way!

Go to top of page Go to top of page

Back to DOSBox Development