gnupic: Thread: Re: [gnupic] gputils CVS->SVN

On Sun, Nov 11, 2007 at 10:27:13AM -0500, David wrote:
> BTW, I also applied your patch for cross-compiling from Linux with
> the mingw script (r505).

Why is the dash release added? I would prefer to only have the
version in all distributions from the same source base.

Also, while this script generates a NSIS config it doesn't generate
the installer itself. Can that be automated too?

Thanks!


//Peter

Peter Stuge wrote:
> On Sun, Nov 11, 2007 at 10:27:13AM -0500, David wrote:
>   
>> BTW, I also applied your patch for cross-compiling from Linux with
>> the mingw script (r505).
>>     
>
> Why is the dash release added? I would prefer to only have the
> version in all distributions from the same source base.
>
>   

Actually it is just how the script works. I wold also bee more satisfied 
with a name without the dash release, but then I looked to the names of 
previous releases, and since they also have the dash release, I left it. 
Maybe it wold be better to modify the script for the next release...

> Also, while this script generates a NSIS config it doesn't generate
> the installer itself. Can that be automated too?
>
>   

I'm not the author of the script, so I don't know why it doesn't 
generate the installer, but it is quite simple to do it: use 
--save-temps to prevent the deletion of the dist directory and then:

    * chdir to ./dist/gputils
    * run the following command from DOS command prompt:

          "c:\Program Files\NSIS\makensis.exe" gputils.nsi 
          the Windows setup package gputils-0.13.5-1.exe will be created
          in the current directory

This can be also done from the make-mingw script, the only problem might 
be that it should work both on Linux and Windows...

Borut

On Sun, 11 Nov 2007 16:53:40 +0100
Peter Stuge ####@####.#### wrote:

> On Sun, Nov 11, 2007 at 10:27:13AM -0500, David wrote:
> > BTW, I also applied your patch for cross-compiling from Linux with
> > the mingw script (r505).
> 
> Why is the dash release added? I would prefer to only have the
> version in all distributions from the same source base.
I'm not sure why. I thought at first it was because of the version
blooper mentioned earlier, and I was going to remove it since there
actually wasn't need for another source release, but I noticed the
same situation for 0.13.4: the source tarball was
gputils-0.13.4.tar.gz, but the Windows installer released 5 minutes
later was gputils-0.13.4-1.exe.

Borut, any explanation there? I can rename if necessary.

David Barnett

David wrote:
> On Sun, 11 Nov 2007 13:27:36 +0100
> Borut Razem ####@####.#### wrote:
>
>   
>> The Windows setup is at 
>> http://sdcc.sourceforge.net/tmp/gputils-0.13.5-1.exe, created it from 
>> release sources. Please put it to gputils file releases and let me
>> know when you'll do it, so that I can remove it.
>>     
> The Windows installer is up in the file releases now. I did notice that
> this binary is a lot bigger than the previous release (1959344 vs.
> 477235)... it's probably nothing but I thought I'd mention it. You can
> take a look and make sure I set it up right and it's not corrupted, and
> then you can take down the sdcc mirror.
>
>   
I didn't pay attention on file size, thank you to notice it. The file 
was bigger due to the different compression algorithm used. I fixed it 
and removed the dash release. The new version is at 
http://sdcc.sourceforge.net/tmp/gputils-0.13.5.exe.
> BTW, I also applied your patch for cross-compiling from Linux with the
> mingw script (r505).
>
>   
I submitted an other patch which solves the compression and dash release 
problems. Please apply them.

Borut

On Sun, Nov 11, 2007 at 06:36:44PM +0100, Borut Razem wrote:
> I submitted an other patch which solves the compression and dash
> release problems.

Cool - thanks! :)


//Peter

On Nov 12, 2007 12:15 AM, Borut Razem ####@####.#### wrote:
> > Also, while this script generates a NSIS config it doesn't generate
> > the installer itself. Can that be automated too?
> >
> >
>
> I'm not the author of the script, so I don't know why it doesn't
> generate the installer, but it is quite simple to do it: use
> --save-temps to prevent the deletion of the dist directory and then:
>
>     * chdir to ./dist/gputils
>     * run the following command from DOS command prompt:
>
>           "c:\Program Files\NSIS\makensis.exe" gputils.nsi
>           the Windows setup package gputils-0.13.5-1.exe will be created
>           in the current directory
>
> This can be also done from the make-mingw script, the only problem might
> be that it should work both on Linux and Windows...
>

I do not need to use --save-temps under Windows/MinGW last time
(year 2005) I tried it. The only thing I need to change is the following.

CC=i386-mingw32msvc-gcc --> CC=mingw32-gcc

Craig said that he should probably make this configurable from the
command line, but to his knowledge, I was the first person, other than him,
to use it since ~2002.

I will try out the new scripts.

The related thread:
http://www.nabble.com/Building-of-gputils-using-MinGW-MSys-under-Windows-t574580.html
Or:
http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/1/5035

Xiaofan

Xiaofan Chen wrote:
> On Nov 12, 2007 12:15 AM, Borut Razem ####@####.#### wrote:
>   
>>> Also, while this script generates a NSIS config it doesn't generate
>>> the installer itself. Can that be automated too?
>>>
>>>
>>>       
>> I'm not the author of the script, so I don't know why it doesn't
>> generate the installer, but it is quite simple to do it: use
>> --save-temps to prevent the deletion of the dist directory and then:
>>
>>     * chdir to ./dist/gputils
>>     * run the following command from DOS command prompt:
>>
>>           "c:\Program Files\NSIS\makensis.exe" gputils.nsi
>>           the Windows setup package gputils-0.13.5-1.exe will be created
>>           in the current directory
>>
>> This can be also done from the make-mingw script, the only problem might
>> be that it should work both on Linux and Windows...
>>
>>     
>
> I do not need to use --save-temps under Windows/MinGW last time
> (year 2005) I tried it.

Yes, you have to, if you want to create the setup.exe. Script itself 
creates the zip package. If you don't specify --save-temps it deletes 
the dist directory which is needed to create setup.exe.

> The only thing I need to change is the following.
>
> CC=i386-mingw32msvc-gcc --> CC=mingw32-gcc
>
>   

Now you can do it from the command line:
CC=mingw32-gcc ./make-mingw ####@####.#### --name="Your 
Name" --source=gputils-0.xx.x.tar.gz --save-temps

> Craig said that he should probably make this configurable from the
> command line, but to his knowledge, I was the first person, other than him,
> to use it since ~2002.
>
>   

Now we are two ;-)

> I will try out the new scripts.
>
>   

Let me know if it works. I suppose you are using MinGW + MSYS?

Borut

On Nov 12, 2007 2:19 PM, Borut Razem ####@####.#### wrote:
> Xiaofan Chen wrote:
> > I do not need to use --save-temps under Windows/MinGW last time
> > (year 2005) I tried it.
>
> Yes, you have to, if you want to create the setup.exe. Script itself
> creates the zip package. If you don't specify --save-temps it deletes
> the dist directory which is needed to create setup.exe.

You are right. Normally I just unzip the file and right click
the NSIS script and choose option "compile NSIS script".

> > The only thing I need to change is the following.
> >
> > CC=i386-mingw32msvc-gcc --> CC=mingw32-gcc
>
> Now you can do it from the command line:
> CC=mingw32-gcc ./make-mingw ####@####.#### --name="Your
> Name" --source=gputils-0.xx.x.tar.gz --save-temps
>
> Let me know if it works. I suppose you are using MinGW + MSYS?
>

Yes this works. Sorry it should be CC=gcc under MinGW/MSys.


Xiaofan