From: Borut R. <bor...@si...> - 2005-04-29 05:45:14
|
Hi, I finally found an optimal solution for generating the sdcc documentation: it is now generated on CF amd64-linux1 FC3 machine as a cron job. I also added a time stamp to the doc archive names, so now we have some history, similar to bin and src snapshot archives. But I'm still not satisfied with the result: as Frieder noted, the type-writer letters are garbled. The funny thing is that I'm able to generate proper fonts, but links are not working then ;-). If I generate the pdf file on Windows (LyX Win32 + MiKTeX), then both links and fonts are OK. If I won't find a solution until the release date, we can put pdfs generated on Windows into doc archives. Erik, let me now, when is the deadline! I'm still trying to find a solution. I'm not a lyx/tex/pdf expert, so if you know the solution or have any ideas, please let me know. P.S.: I didn't try the texhash yet. I hope it will help... Borut -----Original Message----- From: Erik Petrich [mailto:epe...@iv...] Sent: 28. april 2005 19:32 To: Frieder Ferlemann Cc: Borut Razem Subject: Re: SDCC, running texhash once? pdfopt On Thu, 28 Apr 2005, Frieder Ferlemann wrote: > Hello Erik, > > the links within the pdf file are functional again:) > > The type-writer fonts seem to be garbled though. > If we are very lucky then running texhash once fixes that. > > http://www.mpim-bonn.mpg.de/in-lan/mansys/texhash.html > > Greetings, > Frieder > > > > (running pdfopt might make sense too, but this clearly has a very low > priority) Actually, I think Borut is likely to be the one deserving the credit for getting the documentation working on the compiler farm again. Erik |
From: Erik P. <epe...@iv...> - 2005-04-29 06:10:56
|
On Fri, 29 Apr 2005, Borut Razem wrote: > I finally found an optimal solution for generating the sdcc documentation: > it is now generated on CF amd64-linux1 FC3 machine as a cron job. I also > added a time stamp to the doc archive names, so now we have some history, > similar to bin and src snapshot archives. > > But I'm still not satisfied with the result: as Frieder noted, the > type-writer letters are garbled. The funny thing is that I'm able to > generate proper fonts, but links are not working then ;-). If I generate the > pdf file on Windows (LyX Win32 + MiKTeX), then both links and fonts are OK. > If I won't find a solution until the release date, we can put pdfs generated > on Windows into doc archives. Erik, let me now, when is the deadline! Unless some problems arise, I am looking at 7 May. > I'm still trying to find a solution. I'm not a lyx/tex/pdf expert, so if you > know the solution or have any ideas, please let me know. > > P.S.: I didn't try the texhash yet. I hope it will help... Erik |
From: Borut R. <bor...@si...> - 2005-05-06 15:20:38
|
I created SDCC 2.5.0 documentation packages and put them to the SDCC snapshot WEB page http://sdcc.sourceforge.net/snap.php - chapter (docs_2.5.0). The difference with the snapshot version is that sdccman.pdf fonts are OK. I couldn't do it on Linux, so I took the sdccman.dvi generated on Linux and processed it on Windows, and the result seems to be OK ;-) Borut |
From: Frieder F. <fri...@we...> - 2005-05-06 16:19:17
|
Borut Razem wrote: > I created SDCC 2.5.0 documentation packages and put them to the SDCC > snapshot WEB page http://sdcc.sourceforge.net/snap.php - chapter > (docs_2.5.0). > > The difference with the snapshot version is that sdccman.pdf fonts are OK. I > couldn't do it on Linux, so I took the sdccman.dvi generated on Linux and > processed it on Windows, and the result seems to be OK ;-) Hello Borut, could you update the version which is available at http://sdcc.sourceforge.net/doc/sdccman.pdf as well? Preferably with "pdfopt" having been run on it. (With pdfopt users with a slow internet connection should be able to use it more conveniently.) It might make sense to populate the "doc" section http://sourceforge.net/docman/?group_id=599 with a version for 2.5.0 and a version for the old 2.4.0 release. I'll mail bomb you with pdfopt'ed versions for both per PM:^) Greetings, Frieder |
From: Borut R. <bor...@si...> - 2005-05-06 16:39:34
|
> could you update the version which is available at > http://sdcc.sourceforge.net/doc/sdccman.pdf > as well? I can do it, but it doesn't make sense, because it will last only for one day: http://sdcc.sourceforge.net/doc is automatically updated each time the doc snapshot is generated, which happens once per day :-( I still hope to find the solution which will generate correct fonts on Linux. > Preferably with "pdfopt" having been run on it. > (With pdfopt users with a slow internet connection > should be able to use it more conveniently.) OK, I can add the pdfopt step to Makefile.doc. > It might make sense to populate the "doc" section > http://sourceforge.net/docman/?group_id=599 > with a version for 2.5.0 and a version for the > old 2.4.0 release. > I'll mail bomb you with pdfopt'ed versions > for both per PM:^) I'm waiting... Borut |
From: Borut R. <bor...@si...> - 2005-05-06 20:59:00
|
> OK, I can add the pdfopt step to Makefile.doc. Done. > It might make sense to populate the "doc" section > http://sourceforge.net/docman/?group_id=599 > with a version for 2.5.0 and a version for the > old 2.4.0 release. Docman section is only for text and HTML files. I added sdcc-doc package to SDCC File Release System and released sdcc-doc-2.5.0.*. Borut |
From: Borut R. <bor...@si...> - 2005-05-08 19:45:48
|
I finally fixed generation of pdf documents in documentation nightly snapshots. Many thanks to Frieder Ferlemann who actually found the solution. NOTE: pdf documents are now built in pdf version 1.4. I hope that this is not a problem. If somebody disagrees, please let me know. Borut |
From: Erik P. <epe...@iv...> - 2005-05-09 03:31:15
|
I have successfully built release packages (but not submitted them to the release system yet) for source, Intel Linux, and Windows (both .zip and Setup versions). However, I ran into problems with the Power-PC Mac version; the prototypes for some socket functions seem to be missed when compiling sdcc-extra/emu/rrgb/csock.c. The compiler itself compiled without error, so we could probably start the regression tests manually to verify the packagae. However, my semester final exams start in 10 hours, so I won't be able to do this myself until Tuesday or Wednesday. Erik |
From: Frieder F. <fri...@we...> - 2005-05-09 17:00:40
|
Erik Petrich wrote: > verify the packagae. However, my semester final exams start in 10 hours, > so I won't be able to do this myself until Tuesday or Wednesday. Pressing the thumbs here - the sdcc community would certainly let you pass with excellence! Frieder |
From: Erik P. <epe...@iv...> - 2005-05-12 20:51:32
|
SDCC 2.5.0 is officially released. The currently available packages are: 1) source, 2) x86 linux binaries, and 3) 32-bit Windows binaries (both .zip and setup). I've given up on the Power PC Mac package for the moment; the ucsim simulator needed to run the regression tests won't link. For some reason, the linker is not using (or not finding) the ucsim libraries. I'll look at this some more later, but I didn't want to hold up the rest of the release. Erik |
From: Maarten B. (sourceforge) <sou...@ds...> - 2005-05-13 08:31:56
|
Thanks a bunch Erik, Too bad the Mac package cannot be tested, but it's good to have the other= s released. I hope this didn't interfere with your exams too much and that they went well. B.t.w. Is this the same reason the nightly snapshots don'= t build for Mac OSX for almost a year now? And do we actually have Mac users? Now here's what I think still needs to done: * Fix the Mac regression testing ;-) * Submit a News item about the release * Update the Homepage * Update the Canned Responses * Get the word out on the streets (forums?) But once again, many thanks, Maarten > SDCC 2.5.0 is officially released. The currently available packages > are: 1) source, 2) x86 linux binaries, and 3) 32-bit Windows binaries > (both .zip and setup). > > I've given up on the Power PC Mac package for the moment; the ucsim > simulator needed to run the regression tests won't link. For some reaso= n, > the linker is not using (or not finding) the ucsim libraries. I'll look= at > this some more later, but I didn't want to hold up the rest of the > release. > > Erik |
From: Borut R. <bor...@si...> - 2005-05-13 19:44:33
|
> * Update the Homepage Done. Borut |
From: Borut R. <bor...@si...> - 2005-05-13 19:56:03
|
Congratulations and special thanks to Erik. Erik, is there a special reason why the nightly snapshot builds are disabled? Borut |
From: Erik P. <epe...@iv...> - 2005-05-13 21:23:59
|
On Fri, 13 May 2005, Borut Razem wrote: > Erik, is there a special reason why the nightly snapshot builds are > disabled? I had turned them off when generating and testing the release builds to avoid conflicts and had forgotten to turn them on again when I was done. I'll do that next. Erik |
From: Borut R. <bor...@si...> - 2005-05-13 19:53:34
|
> I finally fixed generation of pdf documents in documentation nightly > snapshots. > > Many thanks to Frieder Ferlemann who actually found the solution. > > NOTE: pdf documents are now built in pdf version 1.4. I hope that this is > not a problem. If somebody disagrees, please let me know. Frieder explained me that pdf version 1.4 is problematic, so the pdf documentation is now built in pdf version 1.3. Borut |