Sender: root AT delorie DOT com
Message-ID: <396F149A.B93179D7@inti.gov.ar>
Date: Fri, 14 Jul 2000 10:24:42 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.0.38 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: How to reduce .EXE file size using RHIDE?
References: <Bzlb5.62592$_b3 DOT 1827596 AT newsread1 DOT prod DOT itd DOT earthlink DOT net> <m366q9rk7m DOT fsf AT midpec DOT com> <livsmsslgpt6nc72jmavsi4emue70f5fph AT 4ax DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Damian Yerrick wrote:

> But the OP wanted an option to create a "release" project (in addition
> to a "debug" project) that would automatically run UPX on the result
> of stubify.

It can be done. The user should read RHIDE's documentation. You can override the
linking rules and you can add UPX after ld, but I don't see it as a good idea.
The excecutable should be compressed *only* during the creation of the package.
I do it with Perl scripts, they create a lot of extra files (like version and
manifest), compresses the executable with UPX, makes a copy of the executable
with full debug info (so I can run symify with tracebacks from my users) and
creates a .zip.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013