PharoV50.sources in VM?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

PharoV50.sources in VM?

HilaireFernandes
Hi,

In the Linux distributed VM, I noted the file
lib/pharo/5.xxxx/PharoV50.sources.

Can it be removed safely? What is its purpose?

Thanks

Hilaire

--
Dr. Geo
http://drgeo.eu



Reply | Threaded
Open this post in threaded view
|

Re: PharoV50.sources in VM?

Alistair Grant
Hi Hilaire,

On Fri, 1 Feb 2019 at 21:38, Hilaire <[hidden email]> wrote:
>
> Hi,
>
> In the Linux distributed VM, I noted the file
> lib/pharo/5.xxxx/PharoV50.sources.
>
> Can it be removed safely? What is its purpose?

I can't see any reason for keeping this.  The sources file is now
generated for each image, so it doesn't make sense to distribute it
with the VM.

I'll remove this in a few days if there aren't any other objections.

Cheers,
Alistair

Reply | Threaded
Open this post in threaded view
|

Re: PharoV50.sources in VM?

HilaireFernandes
Thanks for the update.

By the way, is there any reason to not remove the symbols in the Windows
and Linux VM libraries? It saves several MB. At least for DrGeo
distribution, there is no use.

Hilaire

Le 02/02/2019 à 09:01, Alistair Grant a écrit :
> I can't see any reason for keeping this.  The sources file is now
> generated for each image, so it doesn't make sense to distribute it
> with the VM.
>
> I'll remove this in a few days if there aren't any other objections.

--
Dr. Geo
http://drgeo.eu



Reply | Threaded
Open this post in threaded view
|

Re: PharoV50.sources in VM?

Alistair Grant
On Sat, 2 Feb 2019 at 09:32, Hilaire <[hidden email]> wrote:
>
> Thanks for the update.
>
> By the way, is there any reason to not remove the symbols in the Windows
> and Linux VM libraries? It saves several MB. At least for DrGeo
> distribution, there is no use.

I'm  not sure what the impact of this would be, so would prefer others
to comment.


> Hilaire
>
> Le 02/02/2019 à 09:01, Alistair Grant a écrit :
> > I can't see any reason for keeping this.  The sources file is now
> > generated for each image, so it doesn't make sense to distribute it
> > with the VM.
> >
> > I'll remove this in a few days if there aren't any other objections.

It looks like this is a linux only issue (I downloaded Win and Mac VMs
and the sources aren't present).

Issue: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/365
PR: https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/366

Cheers,
Alistair

Reply | Threaded
Open this post in threaded view
|

Re: PharoV50.sources in VM?

Pierce Ng-3
On Sat, Feb 02, 2019 at 12:54:13PM +0100, Alistair Grant wrote:
> On Sat, 2 Feb 2019 at 09:32, Hilaire <[hidden email]> wrote:
> > By the way, is there any reason to not remove the symbols in the Windows
> > and Linux VM libraries? It saves several MB. At least for DrGeo
> > distribution, there is no use.
>
> I'm  not sure what the impact of this would be, so would prefer others
> to comment.

I just built the 32-bit Windows VM from opensmalltalk-vm on Windows 7.
Here's what I got. Pharo.exe works fine.

     Volume in drive C has no label.
     Volume Serial Number is FCE0-E161
   
     Directory of C:\pkg\pharo6vm32
   
    03/02/2019  12:54 AM         2,875,628 Pharo.exe
    03/02/2019  12:54 AM         2,875,628 PharoConsole.exe
    03/02/2019  12:54 AM         9,567,149 PharoConsoleUnstripped.exe
    03/02/2019  12:54 AM         9,567,149 PharoUnstripped.exe
                   4 File(s)     24,885,554 bytes
                   0 Dir(s)  33,491,107,840 bytes free

I think the stripping comes from build.win32x86/common/Makefile starting
line 309:

    ifneq ($STRIPEXE,)
    $(STRIPEXE): $(VMEXE)
    $(STRIP) --strip-unneeded -o $(STRIPEXE) $(VMEXE)
    $(OBJCOPY) --add-gnu-debuglink=$(VMEXE) $(STRIPEXE)
   
    $(STRIPCONSOLEEXE): $(CONSOLEVMEXE)
    $(STRIP) --strip-unneeded -o $(STRIPCONSOLEEXE) $(CONSOLEVMEXE)
    $(OBJCOPY) --add-gnu-debuglink=$(CONSOLEVMEXE) $(STRIPCONSOLEEXE)
    endif

The build output is in build.win32x86/pharo.cog.spur/build/vm. I copied
the *exe and *.dll into c:\pkg\pharo6vm32 and run the VM from there.

Oh, my Linux VM (also self-built) isn't stripped.

    % file ~/pkg/pharo6vm64/pharo
    /home/pierce/pkg/pharo6vm64/pharo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=79f0524e9ecda9a3a3143fb6ba4ff45f552e05dd, with debug_info, not stripped



Reply | Threaded
Open this post in threaded view
|

Re: PharoV50.sources in VM?

HilaireFernandes
Don't forget, the dll can be stripped too !

I saved about 10MB on Dr. Geo bundle with Linux and Windows VMs
stripped. I don't know about Mac OS libraries and excutable, I don't
search for tools to remove its symboles from a Linux workstation.

Hilaire

Le 03/02/2019 à 01:34, Pierce Ng a écrit :

> I just built the 32-bit Windows VM from opensmalltalk-vm on Windows 7.
> Here's what I got. Pharo.exe works fine.
>
>      Volume in drive C has no label.
>      Volume Serial Number is FCE0-E161
>    
>      Directory of C:\pkg\pharo6vm32
>    
>     03/02/2019  12:54 AM         2,875,628 Pharo.exe
>     03/02/2019  12:54 AM         2,875,628 PharoConsole.exe
>     03/02/2019  12:54 AM         9,567,149 PharoConsoleUnstripped.exe
>     03/02/2019  12:54 AM         9,567,149 PharoUnstripped.exe
>                    4 File(s)     24,885,554 bytes
>                    0 Dir(s)  33,491,107,840 bytes free
>
> I think the stripping comes from build.win32x86/common/Makefile starting
> line 309:
>
>     ifneq ($STRIPEXE,)
>     $(STRIPEXE): $(VMEXE)
>     $(STRIP) --strip-unneeded -o $(STRIPEXE) $(VMEXE)
>     $(OBJCOPY) --add-gnu-debuglink=$(VMEXE) $(STRIPEXE)
>    
>     $(STRIPCONSOLEEXE): $(CONSOLEVMEXE)
>     $(STRIP) --strip-unneeded -o $(STRIPCONSOLEEXE) $(CONSOLEVMEXE)
>     $(OBJCOPY) --add-gnu-debuglink=$(CONSOLEVMEXE) $(STRIPCONSOLEEXE)
>     endif
>
> The build output is in build.win32x86/pharo.cog.spur/build/vm. I copied
> the *exe and *.dll into c:\pkg\pharo6vm32 and run the VM from there.
>
> Oh, my Linux VM (also self-built) isn't stripped.
>
>     % file ~/pkg/pharo6vm64/pharo
>     /home/pierce/pkg/pharo6vm64/pharo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=79f0524e9ecda9a3a3143fb6ba4ff45f552e05dd, with debug_info, not stripped
>
--
Dr. Geo
http://drgeo.eu