Small Device C Compiler suite

First quick reply:

The lyx-based documentation is missing in the mingw package.

Bernhard

> The lyx-based documentation is missing in the mingw package.
... and in sdcc-2.4.0-setup.exe too.

Bernhard

> * The installer installs to Program Files\SDCC.  We used to have a
> problem with spaces in the path, but I guess this has been fixed?
I worked on this some time ago. At that point of time, SDCC and SDCPP
didn't have problems with white spaces. I hope that this wasn't broken
recently. I also did some fixes in linkers and assemblers, but I can't
guarantee that it works for all ports...

My comments for INSTALL.txt:

> Even if the default search paths look into c:\sdcc, sdcc is fully
relocatable.
This is not correct: there is no default search path on WIN32 at all.
The statement should be rephrased to: "Sdcc is fully relocatable."

I would also mention in INSTALL.txt that running sdcc-2.4.0-setup.exe is the
recommended way to install SDCC:
- the package is much smaller then the zip-ped version, even that content is
  the same
- it downloads faster (see above)
- WIN32 users are familiar to use *setup*.exe for installation
- no unzip utility needed
- it integrates into Start menu
- standard uninstall process (Add/Remove programs)
- PATH environment variable is automatically updated
- it looks nice ;-)
- I made it ;-))

Borut

> I've built sdcc 2.4.0 for the Mac, Linux, and Windows including the 
> Windows installer.
So this time you created the setup.exe package (usually I'm doing that
from time to time).
Did you follow instructions in setup.nsi? Did you have any problems?

I'm asking this because I added instructions to setup.nsi and I'm wondering
it they are OK.

Borut

On Tuesday, February 24, 2004, at 07:16 AM, Borut Razem wrote:

>> I've built sdcc 2.4.0 for the Mac, Linux, and Windows including the
>> Windows installer.
> So this time you created the setup.exe package (usually I'm doing that
> from time to time).
> Did you follow instructions in setup.nsi? Did you have any problems?
>
> I'm asking this because I added instructions to setup.nsi and I'm 
> wondering
> it they are OK.

No problems.  I must admin I suffered a big case of 'not invented here' 
syndrome when I first saw it, but I followed the instructions and it 
worked out.

I am _very_ impressed with the 7-Zip LZMA compression they've added to 
NSIS - on this type of file it's twice as efficient as plain old PKZip.

-- Michael

OK.  I added the contents of 'sdcc-doc.tar.bz2' to the unix packages 
and the contents of 'sdcc.windowze.tar.bz2' to the win32 one.  I'll re 
do the win32 build by adding the doc package and then the windows 
overlay.

Oh - and I plan to change the suffix on the files from the engineer 
speak 'i386-linux2.2-unknown' and so on to '-macosx', '-win32', and 
'i386-linux2.2'.

-- Michael

On Monday, February 23, 2004, at 10:13 PM, Bernhard Held wrote:

> First quick reply:
>
> The lyx-based documentation is missing in the mingw package.
>
> Bernhard
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> sdcc-devel mailing list
> sdcc-devel@...
> https://lists.sourceforge.net/lists/listinfo/sdcc-devel
>
>

> No problems.  I must admin I suffered a big case of 'not invented here'
> syndrome when I first saw it, but I followed the instructions and it
> worked out.
I don't understand what you mean with 'not invented here' syndrome (my
English
is too poor for phrases like this ;-)

> I am _very_ impressed with the 7-Zip LZMA compression they've added to
> NSIS - on this type of file it's twice as efficient as plain old PKZip.
I was impressed too when I saw it for the first time.

>I'll re do the win32 build by adding the doc package and then the windows
> overlay.
It would be nice to convert .txt files to DOS format (unix2dos, the same way
as for COPYING.TXT).
If you'll change sdcc.nsi, then it would be fine to have some sort of
conditional
compilation, driven from the command line:
- release build, which include the documentation
- nightly snapshot build without the documentation

Borut

> OK.  I added the contents of 'sdcc-doc.tar.bz2' to the unix packages
> and the contents of 'sdcc.windowze.tar.bz2' to the win32 one.  I'll re
> do the win32 build by adding the doc package and then the windows
> overlay.
sdcc-doc-windoze.tar.bz2 contains only the TXT files in DOS format.

Please add always sdcc-doc.tar.bz2, and then replace the TXT files for win32 
packages.

Bernhard

> - the package is much smaller then the zip-ped version, even that content
> is the same
> - it downloads faster (see above)
> - WIN32 users are familiar to use *setup*.exe for installation
> - no unzip utility needed
> - it integrates into Start menu
> - standard uninstall process (Add/Remove programs)
> - PATH environment variable is automatically updated
> - it looks nice ;-)
> - I made it ;-))
I know one drawback:
- it can't be built on the CF :-(

Bernhard

> My comments for INSTALL.txt:
> > Even if the default search paths look into c:\sdcc, sdcc is fully
>
> relocatable.
> This is not correct: there is no default search path on WIN32 at all.
> The statement should be rephrased to: "Sdcc is fully relocatable."
Fixed. I've updated my doc-packages on staging and snapshots.

Bernhard

> Fixed. I've updated my doc-packages on staging and snapshots.
Finally it's nonsense to copy the docs again and again into all packages. Why 
don't we release a separate sdcc-doc package, just like the way it's offered 
at the moment on the snapshot page?

I propose one doc package for real OSs, and one for win32? Of course the 
windows installer should contain the docs too.

Bernhard

On Tuesday, February 24, 2004, at 09:04 AM, Borut Razem wrote:

>> No problems.  I must admin I suffered a big case of 'not invented 
>> here'
>> syndrome when I first saw it, but I followed the instructions and it
>> worked out.
> I don't understand what you mean with 'not invented here' syndrome (my
> English
> is too poor for phrases like this ;-)

Hmm.  First I confuse Bernhard with 'can do kind of guy', now Borut 
with another obscure phrase.  'Not invented here' syndrome is where you 
re-do or re-write something even though a perfectly good implementation 
exists, only because you or your company didn't write it.  That's why 
there are are hundred different hash table libraries out there.

-- Michael

Updated the staging area and the web page.  Changes:

* sdcc 2.4.0 everywhere now.
* Changed suffixes to -macosx, etc.
* Added the docs to the win32 build
* Added the docs to the win32 installer and fixed the uninstaller.
* Added Vangelis to the web page.

http://sdcc.sourceforge.net/staging/
http://sdcc.sourceforge.net/scratch/mlh/

-- Michael

On Tuesday, February 24, 2004, at 09:52 AM, Bernhard Held wrote:

> I know one drawback:
> - it can't be built on the CF :-(

Apparently NSIS works quite well under WINE.  Of course, a statement 
like that is as helpful as saying 'I hear World Peace is quite 
enjoyable'.

-- Michael

>> - the package is much smaller then the zip-ped version, even that content
>> is the same
>> - it downloads faster (see above)
>> - WIN32 users are familiar to use *setup*.exe for installation
>> - no unzip utility needed
>> - it integrates into Start menu
>> - standard uninstall process (Add/Remove programs)
>> - PATH environment variable is automatically updated
>> - it looks nice ;-)
>> - I made it ;-))
>I know one drawback:
>- it can't be built on the CF :-(
... and I know a (at least theoretical ;-) solution: compile NSIS compiler
on Linux,
so we would have NSIS cross compiler, running on Linux and generating
setup.exe for
WIN32.

Borut

> Hmm.  First I confuse Bernhard with 'can do kind of guy', now Borut 
> with another obscure phrase.  'Not invented here' syndrome is where you 
> re-do or re-write something even though a perfectly good implementation 
> exists, only because you or your company didn't write it.  That's why 
> there are are hundred different hash table libraries out there.
I still don't get it: do you try to tell us that you wrote the installer
script and then saw that it already exist? I did the same mistake, but
fortunately the existing version was for old versions NSIS...

Borut

> * sdcc 2.4.0 everywhere now.
> * Changed suffixes to -macosx, etc.
> * Added the docs to the win32 build
> * Added the docs to the win32 installer and fixed the uninstaller.
> * Added Vangelis to the web page.
>
> http://sdcc.sourceforge.net/staging/
> http://sdcc.sourceforge.net/scratch/mlh/
There was a small fix in doc/INSTALL.txt, I took the liberty and copied the
new file into
sdcc-2.4.0-linux-x86.tar.* and sdcc-2.4.0-macosx.tar.*
(although linux users certainly don't care about windoze install
procedures).

 Everything looks ok to me, so let's go ...

Bernhard